Oracle International Corporation

Gregg Alan Wilson

Gary P Cole

Girish Nagaraja

Vadim Lander

Venkateswara Reddy Medam

Nikhil Yograj Vaishnavi

Damien Carru

Ajay Sondhi

Sudhir Kumar Srinivasan

Arsalan Ahmad

Martinus Petrus Lambertus Van Den Dungen

Lokesh Gupta

Ashutosh Pitre

Ajeet Bansal

Xiaoxiao Xu

Pradyumna Reddy Vajja

Venkata Rama Prasad Tammana

Shruthi Chikkanna

Ashwin Kumar Vajantri

Prashant Srinivasan

Tomas Knappek

Girish Yashawant Mande

Manoj N Kumar

Mohamad Raja Gani Mohamad Abdul

Arun Theebaprakasam

Kuang-Yu Shih

Venkata S Evani

Vasukiammaiyar Asokkumar

Ayman Mohammed Aly Hassan Elmenshawy

Balakumar Balu

Yang Li

Ghazanfar Ahmed

Ashish Bhargava

Sudarsan Sridhar

Sheila Wilson

Isabella Hio-Wai Lao

Taoran Li

Robert Lee Tesch, Ii

Swarupa Ramakrishnan

Bhumikaben Rashmikant Patel

Vanja Oljaca

Rohit Jalan

Raghavendra Saravanamurthy

Venkateswara R Medam

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.

Failover of domains

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.

Multi-region login

Techniques are provided for granting an application of a first type of identity system, which uses a first type of identity token, access to a second type of identity system, which uses a second type of identity token. An application can make a request to a token exchange system. The request can include a bearer token and a public key of the application. The token exchange system can exchange the bearer token for a Proof-of-Possession token after performing verification steps. A token exchange system can exchange the first token (e.g., bearer token) for the first identity system for the second token (e.g., Proof-of-Possession token) for the second identity system without requiring entry of credentials to access the second identity system.

Applications as resource principals or service principals

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. Responsive to receiving the request to register the application, the IMAS causes the template application instance on the user device to transition to an application instance of the application with full functionality, generates an application instance-specific credential for the application instance, associates the generated application instance-specific credential with the application instance, and stores the application instance-specific credential in association with (1) an application identifier identifying the application instance, (2) a user identifier identifying the user, and (3) a user device identifier identifying the user device.

Techniques for dynamically assigning client credentials to an application

A framework for migrating a customer tenancy from a first identity and access management (TAM) system to a second IAM system. A first snapshot of the customer tenancy is obtained from a first data storage. The first snapshot is processed and migrated to the second IAM system. A second snapshot of the customer tenancy is obtained from a second data storage and migrated to the second IAM system. A state of a lock associated with the second data storage is modified, where after a third snapshot of the customer tenancy is obtained from the second data storage and migrated to the second IAM system. Responsive to the third snapshot being migrated, directing a request regarding the customer tenancy to the second IAM system.

Migration and cutover based on events in a replication stream

The present embodiments relate to a CI replication service that can replicate domain data from IDCS control plane to data plane and to all subscribed regions of a domain. For instance, the CI replication service can provide replication of required resources of a domain for AuthN and AuthZ from an IDCS local region to other regions for high availability (e.g., to improve latency). The CI replication service can replicate the resources from a domain's home region to all subscribed regions for local availability of data for workloads running in those regions. Further, when a new region is subscribed for a domain, then the service can bootstrap that domain's data from home region before enabling that region for the domain.

Domain replication across regions

Embodiments are directed to a multi-tenant cloud system. Embodiments receive a request for an authentication action for a user and create an authenticate target action. Embodiments register a cache listener to listen for a target action response that is responsive to the authenticate target action and initiate the authentication action for the user at an on-premise active directory ('AD') via a bridge. Embodiments wait for a cache callback and, at the cache callback, receive a target action response comprising a result of the authentication action.

Multi-tenant identity cloud service with on-premise authentication integration

Embodiments include a multi-tenant cloud system that receives a request for an authenticate action for a user. Embodiments create an authenticate target action and register a cache listener for a cache that includes a filter to listen for a target action response that is responsive to the authenticate target action, the filter listing a plurality of bridges assigned to an on-premise active directory. Embodiments randomly select one of the plurality of bridges and sends the authenticate target action to the active directory via the selected bridge. Embodiments wait for a cache callback and, at the cache callback, receive a target action response that includes a result of the authenticate action.

Multi-tenant identity cloud service with on-premise authentication integration and bridge high availability

Embodiments include a multi-tenant cloud-based identity management system for a plurality of tenants. Embodiments include a global database providing a first set of resources to the plurality of tenants and a plurality of tenant databases, each tenant database providing a second set of resources to one of the plurality of tenants. Embodiments further include a plurality of resources accessible by the tenants and an automated upgrade framework for upgrading the global database and the tenant databases in response to an upgrade of a first release of the system to a second release of the system. For the automated upgrade framework, embodiments determine resource changes between the first release and the second release, generate an upgrade patch based on the resource changes and apply the upgrade patch to the global database.

Automated database upgrade for a multi-tenant identity cloud service

A system stores and uses object relationships in a multi-tenant cloud-based identity and access management (IAM) system by: defining a schema for storing related objects, where the schema includes reference attributes indicative of relationships between the related objects in a database, and the schema defines a relationship type and a persistence scope for each reference attribute; constructing an in-memory representation of the related objects and their relationships based on the schema, where the in-memory representation indicates the relationship type and the persistence scope for each reference attribute; and using the in-memory representation of the related objects to perform an IAM service for a client of the multi-tenant cloud-based IAM system.

Reference attributes for related stored objects in a multi-tenant cloud service

One embodiment provides declarative policy management in a multi-tenant cloud-based identity and access management ('IAM') system. The embodiment receives at least one Application Programming Interface ('API') request by a policy engine of the multi-tenant cloud-based IAM system from a tenant of the multi-tenant cloud-based IAM system. The embodiment configures a declarative policy for the tenant of the multi-tenant cloud-based IAM system based on the at least one API request. The embodiment then enforces the declarative policy in an IAM service performed for the tenant of the multi-tenant cloud-based IAM system.

Rest-based declarative policy management

Embodiments provide cloud based identity management by receiving a request from an application for a resource that includes an operation on a resource type out of a plurality of resource types and the request specifies a tenant out of a plurality of tenants, the resource type including a schema, and the schema includes a plurality of schema attributes and metadata for each of the schema attributes, the resource type including one of a user or a second application. Embodiments store multiple versions of the resource type, at least a first version of the resource indicating a deprecated attribute with respect to a first previous version of the resource type, and at least a second version of the resource type indicating an added attribute with respect to a second previous version of resource type, where the request indicates one of the multiple versions of the resource type.

Data management 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.

Generating derived credentials for a multi-tenant identity cloud service

Embodiments perform write operations in a multi-tenant cloud system that includes a first data center adapted to authenticate a first plurality of registered clients and located in a first geographic area, and a second data center adapted to authenticate a second plurality of registered clients and located in a second geographic area that is different from the first geographic area. Embodiments receive a request from a first client to perform a first write for a resource at the second data center. Embodiments generate a call to the first data center including a second write for the resource at the first data center. Embodiments retrieve data corresponding to the first write and send the retrieved data to the first data center. Embodiments write on the data based on the first write, the writing on the data including changing the data to generate changed data.

Local write for a multi-tenant identity cloud service

Growing community of inventors

Austin, TX, United States of America

Gregg Alan Wilson