Generating derived credentials for a multi-tenant identity cloud service
A multi-tenant system that provides cloud-based identity management receives a request to execute a job, where the job has a scheduled start time, or a timeframe to complete, that exceeds the validity time of a request access token. The system generates the request access token corresponding to the job, where the request access token has access privileges. The system schedules the job and persists the request access token. The system triggers the job at the scheduled start time and generates a derived access token based on the request access token, where the derived access token includes the access privileges. The system then injects the derived access token during runtime of the job and calls a service using the derived access token to execute the job.
1. A non-transitory computer readable medium having instructions stored thereon that, when executed by one or more processors, cause the processors to provide cloud based identity management, the providing comprising:
providing, by a cloud based identity management system, a request access token to a user, the request access token required to invoke a scheduling of an identity management job executed by the cloud based identity management system, the request access token comprising a first validity time and comprising a set of access privileges;
receiving from the user a request to invoke the scheduling of the job, the request comprising the request access token, wherein the job has a timeframe to complete that exceeds the first validity time of the request access token;
validating the request access token;
scheduling the job;
persisting the request access token;
triggering the job at a scheduled start time;
generating a derived access token based on the request access token, wherein the derived access token comprises a same set of access privileges as the request access token and comprises a second validity time that is greater than the timeframe to complete and the derived access token is not sent to the user;
injecting the derived access token; and
calling a service using the derived access token to execute the job.
2. The non-transitory computer readable medium of claim 1 , wherein the service comprises a microservice and the request access token is persisted in an operational data store and cannot be accessed by other users.
3. The non-transitory computer readable medium of claim 1 , further comprising signing the derived access token using current signing keys, wherein the derived access token is not received from the user.
4. The non-transitory computer readable medium of claim 1 , wherein the calling the service comprises invoking an application programming interface that corresponds to the service.
5. The non-transitory computer readable medium of claim 1 , wherein the request access token is persisted with metadata corresponding to the job.
6. The non-transitory computer readable medium of claim 5 , wherein the request access token is retrieved from the metadata and decoded.
7. The non-transitory computer readable medium of claim 1 , wherein the request comprises an identity of a tenant of a plurality of tenants that comprises a resource needed to execute the job.
8. A method to provide cloud based identity management, the method comprising:
providing, by a cloud based identity management system, a request access token to a user, the request access token required to invoke a scheduling of an identity management job executed by the cloud based identity management system, the request access token comprising a first validity time and comprising a set of access privileges;
receiving from the user a request to invoke the scheduling of the job, the request comprising the request access token, wherein the job has a timeframe to complete that exceeds the first validity time of the request access token;
validating the request access token;
scheduling the job;
persisting the request access token;
triggering the job at a scheduled start time;
generating a derived access token based on the request access token, wherein the derived access token comprises a same set of access privileges as the request access token and comprises a second validity time that is greater than the timeframe to complete and the derived access token is not sent to the user;
injecting the derived access token; and
calling a service using the derived access token to execute the job.
9. The method of claim 8 , wherein the service comprises a microservice and the request access token is persisted in an operational data store and cannot be accessed by other users.
10. The method of claim 8 , further comprising signing the derived access token using current signing keys, wherein the derived access token is not received from the user.
11. The method of claim 8 , wherein the calling the service comprises invoking an application programming interface that corresponds to the service.
12. The method of claim 8 , wherein the request access token is persisted with metadata corresponding to the job.
13. The method of claim 12 , wherein the request access token is retrieved from the metadata and decoded.
14. The method of claim 8 , wherein the request comprises an identity of a tenant of a plurality of tenants that comprises a resource needed to execute the job.
15. A system for providing cloud-based identity and access management, comprising:
a plurality of tenants;
a plurality of services; and
one or more processors that:
providing, by the cloud based identity management system, a request access token to a user, the request access token required to invoke a scheduling of an identity management job executed by the cloud based identity management system, the request access token comprising a first validity time and comprising a set of access privileges;
receive from the user a request to invoke the scheduling of the job, the request comprising the request access token, wherein the job has a timeframe to complete that exceeds the first validity time of the request access token;
validate the request access token;
schedule the job;
persist the request access token;
trigger the job at a scheduled start time;
generate a derived access token based on the request access token,
wherein the derived access token comprises a same set of access privileges as the request access token and comprises a second validity time that is greater than the timeframe to complete and the derived access token is not sent to the user;
inject the derived access token; and
call a service using the derived access token to execute the job.
16. The system of claim 15 , wherein each of the services comprises a microservice and the request access token is persisted in an operational data store and cannot be accessed by other users.
17. The system of claim 15 , further comprising signing the derived access token using current signing keys, wherein the derived access token is not received from the user.
18. The system of claim 15 , wherein the call the service using the derived access token comprises invoking an application programming interface that corresponds to the service.
19. The system of claim 15 , wherein the request access token is persisted with metadata corresponding to the job.
20. The system of claim 19 , wherein the request access token is retrieved from the metadata and decoded.