Oracle International Corporation

Gary P Cole

Gregg Alan Wilson

Vadim Lander

Damien Carru

Ajay Sondhi

Girish Nagaraja

Venkata S Evani

Martinus Petrus Lambertus Van Den Dungen

Ayman Mohammed Aly Hassan Elmenshawy

Ashutosh Pitre

Amol Dharmadhikari

Vikrant Jain

Venkata Rama Prasad Tammana

Ashish Bhargava

Ashish Kumar Gupta

Sudarsan Sridhar

Tomas Knappek

Isabella Hio-Wai Lao

Zheang Li

Ashish Gupta

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

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

A system manages tenant application updates in a multi-tenant cloud-based identity and access management (IAM) system by defining one or more application templates; creating one or more applications for one or more tenants of the multi-tenant cloud-based IAM system using the one or more application templates; applying a change to at least one of the one or more application templates; determining whether the one or more applications need to be updated in an automatic mode, a semi-automatic mode, or a manual mode, to incorporate the change; and updating at least one of the one or more applications in an applicable one of the automatic mode, the semi-automatic mode, or the manual mode, based on the outcome of the determining.

Application templates and upgrade framework for a multi-tenant identity cloud service

Embodiments provide cloud-based identity management by receiving a request to perform an identity management service that includes real-time tasks and near-real-time tasks. Embodiments synchronously execute the real-time tasks by accessing at least one microservice using a corresponding application programming interface ('API'). Embodiments asynchronously execute the near-real-time tasks by offloading the near-real-time tasks to one or more message queues.

Task segregation in a multi-tenant identity and data security management cloud service

A system provides cloud-based identity and access management. The system provides a user interface ('UI') to a tenant of an identity-management service. The system enables diagnostics functionality for the tenant based on a user input received via the UI, where the diagnostics functionality allows for a user in the tenant to configure and receive diagnostics reports related to the identity-management service. The system then receives a request for the identity-management service, accesses a microservice based on the request, performs the identity-management service by the microservice, collects and records diagnostics information during the performing of the identity-management service, and displays the diagnostics information to the user via the UI.

Tenant self-service troubleshooting for a multi-tenant identity and data security management cloud service

Embodiments provide application management functionality in a multi-tenant identity cloud service. Embodiments define a plurality of facets for the application, each facet describing a behavior of the application. Embodiments define an application template for the application that includes metadata to generate default values for the application. Embodiments generate a user interface ('UI') that includes functionality to configure all of the defined facets.

Application management for a multi-tenant identity cloud service

A system provides cloud-based identity and access management. The system receives a request for performing an identity management service, where the request includes a call to an application programming interface ('API') that identifies the identity management service and a microservice configured to perform the identity management service. The system authenticates the request, accesses the microservice, and performs the identity management service by the microservice.

Microservices based multi-tenant identity and data security management cloud service

A system provides cloud-based identity and access management. The system receives a request to perform an identity management service, and accesses a microservice based on the identity management service. The system determines one or more real-time tasks and one or more near-real-time tasks that are required to be executed to complete the identity management task. The system synchronously executes the one or more real-time tasks by the microservice, and sends the one or more near-real-time tasks to a queue to be asynchronously executed.

Growing community of inventors

Austin, TX, United States of America

Gary P Cole