Oracle International Corporation

Venkata S Evani

Ajay Sondhi

Ching-Wen Chu

Girish Nagaraja

Uppili Srinivasan

Daniel Music Vogel

Beomsuk Kim

Martinus Petrus Lambertus Van Den Dungen

Gregg Alan Wilson

Shivaram Bhat

Nagaraj Pattar

Gary P Cole

Matthew Rushton

Ghazanfar Ahmed

Ashok Kumar Subbaiyan

Shobhank Sharma

Kranthi Kiran Pandiri

Norka Beatriz Lucena Mogollon

Kirils Zaicenko

Vladimir Nikolayevich Krayushkin

Atul Goyal

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.

Single sign-on between 2 independent states

Techniques are described for providing a multi-cloud control plane (MCCP) in a first cloud infrastructure (included in a first cloud environment provided by a first cloud services provider) that enables services and/or resources provided in the first cloud infrastructure to be utilized by users of a second cloud environment. The first cloud infrastructure receives a request from a user associated with an account in the second cloud infrastructure. The request corresponding to using a service provided by the first cloud infrastructure. A tenancy is created for the user in the first cloud infrastructure to enable the user to utilize the service, and a link-resource object is created that includes information linking the tenancy of the user in the first cloud infrastructure to the account of the user in the second cloud infrastructure, the link-resource object enabling the user to utilize the service provided by the first cloud infrastructure.

Propagating identities across different cloud services providers

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

Cloud-link adaptor of a multi-cloud infrastructure

A framework, which conforms to the OAuth standard, involves a generic OAuth authorization server that can be used by multiple resource servers in order to ensure that access to resources stored on those resource servers is limited to access to which the resource owner consents. Each resource server registers, with the OAuth authorization server, metadata for that resource server, indicating scopes that are recognized by the resource server. The OAuth authorization server refers to this metadata when requesting consent from a resource owner on behalf of a client application, so that the consent will be of an appropriate scope. The OAuth authorization server refers to this metadata when constructing an access token to provide to the client application for use in accessing the resources on the resource server. The OAuth authorization server uses this metadata to map issued access tokens to the scopes to which those access tokens grant access.

Bundled authorization requests

Service profile-specific token attributes and resource server token attribute overriding

Pluggable authorization policies

Multiple resource servers interacting with single OAuth server

Growing community of inventors

Fremont, CA, United States of America

Venkata S Evani