You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of deleting expired temporary users from backend, maintain active|inactive state of the temporary users. Alternatively, we can support delete on expiry toggle letting admin configure expiration behaviour.
What problem does this solve?
Various Teleport integration services support SCIM client/server (Okta, Sailpoint, Identity Center integration) , permission assignment (Identity Center integration) and each integration needs to handle a special case for temporary users. It adds complexity to integration system and affects user experience. For example, any time temporary user account is created/removed, they need to be provisioned/de-provisioned in upstream SCIM server. Given provisioning are not always instant and subject to API throttling, user may need to wait for few more minutes before they can access the upstream service.
If a workaround exists, please include it.
The current system works too but it demands special case for each new user identity related integration we support.
The text was updated successfully, but these errors were encountered:
What would you like Teleport to do?
Instead of deleting expired temporary users from backend, maintain
active|inactive
state of the temporary users. Alternatively, we can supportdelete on expiry
toggle letting admin configure expiration behaviour.What problem does this solve?
Various Teleport integration services support SCIM client/server (Okta, Sailpoint, Identity Center integration) , permission assignment (Identity Center integration) and each integration needs to handle a special case for temporary users. It adds complexity to integration system and affects user experience. For example, any time temporary user account is created/removed, they need to be provisioned/de-provisioned in upstream SCIM server. Given provisioning are not always instant and subject to API throttling, user may need to wait for few more minutes before they can access the upstream service.
If a workaround exists, please include it.
The current system works too but it demands special case for each new user identity related integration we support.
The text was updated successfully, but these errors were encountered: