Abstract: Approaches of reassigning a home region from a first data center to a second data center as requested by a customer are described herein. The home region is able to implement write operations to a domain, whereas other data centers cannot implement write operations to the domain. The customer can request the home region being reassigned to another data center such that the customer can utilize the other data center to implement write operations to the domain.

Abstract: Approaches of reassigning a home region from a first data center to a second data center as requested by a customer are described herein. The home region is able to implement write operations to a domain, whereas other data centers cannot implement write operations to the domain. The customer can request the home region being reassigned to another data center such that the customer can utilize the other data center to implement write operations to the domain.

Abstract: A system for providing login to a network of a cloud service provider via more than one region is described herein. For example, the system and approaches may store authentication information in multiple regions allowing for authentication in the multiple regions.

Abstract: An approach of performing data center failover using an address that indicates a backup data center. The address includes common names indicating a data center with a domain and a backup datacenter with a replica of the domain. A cloud service provider can receive the address, establish a connection with an available data center, and failover to the backup data center if the data center with the connection becomes unavailable.

Abstract: An identity management and authorization system (IMAS) receives a request to download an application to a user device associated with a user. The IMAS downloads, to the user device, a template application instance corresponding to the requested application, the template application instance having a reduced functionality than the requested application. The IMAS receives, from the user device, a request to register to the downloaded template.

Abstract: Approaches of reassigning a home region from a first data center to a second data center as requested by a customer are described herein. The home region is able to implement write operations to a domain, whereas other data centers cannot implement write operations to the domain. The customer can request the home region being reassigned to another data center such that the customer can utilize the other data center to implement write operations to the domain.

Abstract: Described herein is a framework for generating an integrated identity and access management (IAM) system from a first IAM system and a second IAM system that is different than the first IAM system. The integrated IAM system is generated by: (i) creating a domain in a customer tenancy associated with the first IAM system, and (ii) embedding an identity provider of the second IAM system within the domain. The integrated IAM system receives a request from a user to perform an operation with respect to resource associated with the second IAM system. Upon the user being successfully authenticated by the integrated IAM system, the request is executed.

Abstract: Systems and methods for single sign-on between two independent systems are disclosed herein. The method can include receiving a request to access a first application of a first system having a first login protocol. The method can include receiving user login credentials and authenticating the user login credentials. The method can include logging the user in to the first system and a second system based on the received login credentials. The second system can have a second login protocol independent of the first login protocol.

Abstract: Techniques are disclosed for unifying a first identity management service with a second identity management service within a distributed computing system. The first identity management service can receive a request to perform an entity operation. The request may be formatted for an interface of the first identity service. The first identity service can determine that the account is in a second domain associated with the second identity service and transform the request to a format corresponding to an interface of the second identity service. The transformed request may be transmitted to the second identity service using an external proxy and based in part on the second domain corresponding to the second identity service.

Abstract: Systems and methods for a single logout between two independent systems are described herein. The system includes a first access control system having a first login protocol. The first access control system includes at least one first processor, and a memory comprising a plurality of instructions executable by the at least one first processor. The system includes a second access control system. The second access control system has a second login protocol independent of the first login protocol. The first access control system can receive a logout request from a user at the first access control system, logging the user out of the first access control system, and utilizing a trust mechanism to log the user out of the second access control system.

Abstract: Techniques for making eventual consistency cache updates deterministic. One technique includes receiving, at a control plane, a request to execute an operation on data, executing the operation on the data, creating a replication event for the operation and a replication identifier associated with the replication event, sending a response that includes a custom header having the replication identifier, receiving, at a data plane, a subsequent request to execute an operation involving the data, the subsequent request includes the replication identifier, retrieving a replication identifier for a latest replication event executed on the data plane, comparing the replication identifier from the subsequent request and the replication identifier for the latest replication event, determining the replication event associated with the replication identifier from the subsequent request has not been executed on the data plane based on the comparison, and sending a deterministic error message to the client device.