Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
712:api-tokens [2025/09/15 15:26] – [How to create an API token for SCIM] Weinlein, Thomas | 712:api-tokens [2025/09/15 15:37] (current) – [API token administration] Weinlein, Thomas | ||
---|---|---|---|
Line 25: | Line 25: | ||
Each token is identified by a label that is defined upon generation. The resulting token values will not be stored at the server but the server is able to identify a valid token by its value. Tokens become invalid after explicitly being revoked by the Stages administrator or after their expiry date has been reached. | Each token is identified by a label that is defined upon generation. The resulting token values will not be stored at the server but the server is able to identify a valid token by its value. Tokens become invalid after explicitly being revoked by the Stages administrator or after their expiry date has been reached. | ||
- | {{:712:issue_apitoken.png}} | + | {{ :712:issue-token.jpg }} |
Directly after creating the API Token, the token value can be copied from the Stages popup dialog and saved in a secure location. Once the dialog has been closed, it can not be retrieved anymore. | Directly after creating the API Token, the token value can be copied from the Stages popup dialog and saved in a secure location. Once the dialog has been closed, it can not be retrieved anymore. | ||
Line 48: | Line 48: | ||
All API tokens no matter if of type SCIM or CollectorData, | All API tokens no matter if of type SCIM or CollectorData, | ||
+ | |||
+ | {{ 712: | ||
So the administrator has always an overview which API tokens exist for the Stages server and is also able to disable or revoke them. | So the administrator has always an overview which API tokens exist for the Stages server and is also able to disable or revoke them. | ||