We've updated our file storage system, so some links may no longer work. If you need a file, just email us at support@secomea.com—we’re happy to help!

Manage SCIM access tokens in Okta

Prev

Manage SCIM access tokens in Okta

Security and Governance Controls

Token Validity:

Each SCIM token has a one-year lifetime. Generating a new token does not in itself revoke previous issued tokens. This is to ensure synchronization continuity. Only when a new token is added to Okta and a successful test sync has been run will the previous token be rendered inactive.

Token Rotation:

Rotate before the one-year expiry. To rotate, generate a new token in Prime (see Set up SCIM with Okta), then repeat the Integration steps in section 2.1 with the new value, ending with Test API Credentials and Save. The previous token remains active until that test sync succeeds, so synchronisation is not interrupted and a failed attempt can be retried.

Revocation Rights:

The Secomea Team has the capability to fully revoke the SCIM integration, in exceptional or security-related scenarios, or in connection with customer offboarding.

Audit and Traceability:

All token creation, revocation, and usage events are logged and auditable through Prime’s backend services.

References

Official SCIM 2.0 Documents as listed below:

https://datatracker.ietf.org/doc/html/rfc7643

https://datatracker.ietf.org/doc/html/rfc7644

https://datatracker.ietf.org/doc/html/rfc7642