Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Informatica Intelligent Cloud Services REST API
  3. Platform REST API version 2 resources
  4. Platform REST API version 3 resources
  5. Data Integration REST API
  6. File Ingestion and Replication REST API
  7. Streaming Ingestion and Replication REST API
  8. RunAJob utility
  9. ParamSetCli utility
  10. REST API codes
  11. REST API resource quick references

REST API Reference

REST API Reference

Revoking a token

Revoking a token

If you have Kubernetes DevOps engineers privileges, you can revoke a token.

DELETE request

To revoke a token, use the following URI:
/public/core/v3/containerImageToken/revoke/<tokenId>
Include the following parameter:
Parameter
Type
Description
tokenId
String
ID of the token to be revoked.
The following table lists the potential error codes for a request:
HTTP status code
Description
400
Token with id:{tokenId} already revoked.
400
User:{0} is not authorized to revoke this token.
401
Unauthenticated or unauthorized.
403
Privilege get.k8s.repository.token is required for accessing this API.

DELETE response

If successful, the token is revoked.

DELETE response examples

To revoke a token, use the following request:
DELETE <baseApiUrl>/public/core/v3/containerImageToken/revoke/<tokenId> Content-type: application/json Accept: application/json INFA-SESSION-ID: <SessionId>
If successful, you receive a "200 OK" response.
If you have insufficient privileges, you might receive a "403 Forbidden" response like the following example:
{ "error": { "code": "AIS_007", "message": "Privilege - view.k8s.agent.config required for accessing this API.", "debugMessage": "Privilege - view.k8s.agent.config required for accessing this API.", "requestId": "l2EpwkFoqkEjrEJURclPw2", "details": null } } }
If the token has already been revoked, you might receive a "400 Bad Request" response like the following example:
{ "error": { "code": "AIS_014", "message": "Token with id:<token ID> already revoked.", "debugMessage": "Token with id:<token ID> already revoked.", "requestId": "iVdlwEoaFiZd3vb0LvLVmp", "details": null } } }
If you are not authorized to revoke the token, you might receive a "400 Bad Request" response like the following example:
{ "error": { "code": "AIS_013", "message": "User:k8s is not authorized to revoke this token :<token ID>.", "debugMessage": "User:k8s is not authorized to revoke this token :<token ID>.", "requestId": "iLhZ6l6EF6Ddb3jICTGxoj", "details": null } }

0 COMMENTS

We’d like to hear from you!