Assured lazy rollback for a multi-tenant identity cloud service
Embodiments operate a multi-tenant cloud system for a plurality of user accounts. Embodiments receive a create request from a client system to provision a new account for a user. Embodiments determine that the create request has failed and initiates a rollback of the create request. Embodiments determine that the rollback has failed and initiates a new rollback in response to a status request from the client system.
1. A method of operating a multi-tenant cloud system for a plurality of user accounts, the method comprising:
receiving a create request from a client system to provision a new account for a user;
determining that the create request has failed;
initiating a rollback of the create request;
determining that the rollback has failed; and
initiating a new rollback in response to a status request from the client system.
2. The method of claim 1 , wherein when the rollback has failed, the new rollback is not initiated unless the status request from the client system is received.
3. The method of claim 2 , wherein the rollback has failed when the rollback is in-progress greater than a second predetermined time period.
4. The method of claim 1 , wherein the create request has failed when the create request is in-progress greater than a first predetermined time period.
5. The method of claim 1 , further comprising:
submitting a task for deletion in a thread pool; and
deleting tenant entries from a schema.
6. The method of claim 5 , further comprising:
in response to the status request, while the rollback has completed, responding that the create request has failed.
7. The method of claim 1 , the create request and the status request both comprising using a REpresentational State Transfer (REST) application programming interface (API).
8. A non-transitory computer-readable medium storing instructions which, when executed by at least one of a plurality of processors, cause the processor to operate a multi-tenant cloud system for a plurality of user accounts, the operating comprising:
receiving a create request from a client system to provision a new account for a user;
determining that the create request has failed;
initiating a rollback of the create request;
determining that the rollback has failed; and
initiating a new rollback in response to a status request from the client system.
9. The computer-readable medium of claim 8 , wherein when the rollback has failed, the new rollback is not initiated unless the status request from the client system is received.
10. The computer-readable medium of claim 9 , wherein the rollback has failed when the rollback is in-progress greater than a second predetermined time period.
11. The computer-readable medium of claim 8 , wherein the create request has failed when the create request is in-progress greater than a first predetermined time period.
12. The computer-readable medium of claim 8 , the operating further comprising:
submitting a task for deletion in a thread pool; and
deleting tenant entries from a schema.
13. The computer-readable medium of claim 12 , the operating further comprising:
in response to the status request, while the rollback has completed, responding that the create request has failed.
14. The computer-readable medium of claim 8 , the create request and the status request both comprising using a REpresentational State Transfer (REST) application programming interface (API).
15. A multi-tenant cloud system for a plurality of user accounts, the system comprising:
one or more processors in communication with a client system that receives a new user account request from a user, the processors:
receiving a create request from the client system to provision a new account for the user in response to the new user account request from the user;
determining that the create request has failed;
initiating a rollback of the create request;
determining that the rollback has failed; and
initiating a new rollback in response to a status request from the client system.
16. The system of claim 15 , wherein when the rollback has failed, the new rollback is not initiated unless the status request from the client system is received.
17. The system of claim 16 , wherein the rollback has failed when the rollback is in-progress greater than a second predetermined time period.
18. The system of claim 15 , wherein the create request has failed when the create request is in-progress greater than a first predetermined time period.
19. The system of claim 15 , further comprising:
in response to the status request, while the rollback is in-progress, responding that the create request is in-progress.
20. The system of claim 19 , further comprising:
submitting a task for deletion in a thread pool; and
deleting tenant entries from a schema.