Abstract: Embodiments are directed to a multi-tenant cloud system that provisions new customer accounts. Embodiments include a dedicated database schema and a shared database schemas. Embodiments provision a new customer account by determining whether the new customer account is a first type of account or a second type of account. When the new customer account is the first type of account, embodiments allocate the new customer account to the one of the shared database schemas. When the new customer account is the second type of account, embodiments allocate the new customer account to a dedicated schema.

Abstract: Techniques are provided for creating a unified data model for entities in components of an access management system. A method can include identifying an entity of a component, identifying a first attribute metadata for the entity, creating a data type for the first attribute metadata of the entity, defining the entity in accordance with the created data type, and storing the defined entity in a unified storage.

Abstract: 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.

Abstract: Embodiments are directed to rewiring a key management system (“KMS”) service instance (“SI”) with associated keys. Embodiments, in response to a request, delete a first SI that is mapped to one or more keys. To restore the keys, embodiments create a second SI and map the second SI to the one or more keys.

Abstract: A cloud-based identity and access management system that implements single sign-on (“SSO”) receives a first request for an identity management service configured to allow for accessing an application. Embodiments send the first request to a first microservice which performs the identity management service by generating a token. The first microservice generates the token at least in part by sending a second request to a SSO microservice that is configured to provide SSO functionality across different microservices that are based on different protocols. Embodiments then receive the token from the first microservice and provide the token to the application, where the token allows for accessing the application.

Abstract: Embodiments are directed to rewiring a key management system (“KMS”) service instance (“SI”) with associated keys. Embodiments, in response to a request, delete a first SI that is mapped to one or more keys. To restore the keys, embodiments create a second SI and map the second SI to the one or more keys.

Abstract: 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.

Abstract: Embodiments are directed to a multi-tenant cloud system that provisions new customer accounts. Embodiments include a dedicated database schema and a shared database schemas. Embodiments provision a new customer account by determining whether the new customer account is a first type of account or a second type of account. When the new customer account is the first type of account, embodiments allocate the new customer account to the one of the shared database schemas. When the new customer account is the second type of account, embodiments allocate the new customer account to a dedicated schema.

Abstract: Tenant and service management for an Identity Cloud Service (IDCS) is provided. A request is received, from a Tenant Automation System (TAS) over a network, to create an IDCS service instance for a tenant. The IDCS service instance is created using a task execution framework that includes a task orchestrator and a plurality of synchronous tasks, the task orchestrator instantiating the tasks, controlling the tasks and generating a response to the request. A response, indicating that the IDCS service instance for the tenant has been created, is sent to the TAS over the network.

Abstract: Tenant and service management for an Identity Cloud Service (IDCS) is provided. A request is received, from a Tenant Automation System (TAS) over a network, to create an IDCS service instance for a tenant. The IDCS service instance is created using a task execution framework that includes a task orchestrator and a plurality of synchronous tasks, the task orchestrator instantiating the tasks, controlling the tasks and generating a response to the request. A response, indicating that the IDCS service instance for the tenant has been created, is sent to the TAS over the network.

Abstract: A cloud-based identity and access management system that implements single sign-on (“SSO”) receives a first request for an identity management service configured to allow for accessing an application. Embodiments send the first request to a first microservice which performs the identity management service by generating a token. The first microservice generates the token at least in part by sending a second request to a SSO microservice that is configured to provide SSO functionality across different microservices that are based on different protocols. Embodiments then receive the token from the first microservice and provide the token to the application, where the token allows for accessing the application.

Abstract: Techniques are provided for creating a unified data model for entities in components of an access management system. A method can include identifying an entity of a component, identifying a first attribute metadata for the entity, creating a data type for the first attribute metadata of the entity, defining the entity in accordance with the created data type, and storing the defined entity in a unified storage.