Distributed high availability agent architecture

A high availability (HA) Identity Bridge (IDBridge) between an on-premises Active Directory (AD) and a cloud-based Identity Cloud Service (IDCS) is provided. A connection to an AD, coupled to a first network, is established. A connection to an IDCS, coupled to a second network, is established, the IDCS including a System for Cross-domain Identity Management (SCIM) directory. A plurality of selectable AD OUs are displayed in a GUI, and a selection of one or more OUs is then received. Each member group of the selected OUs is displayed in the GUI, and a selection of one or more member groups of the selected OUs is then received. The users of the selected OUs and the selected member groups of the selected OUs are monitored to identify users and groups that have been added, modified or deleted. The identified users and groups are then synchronized to the SCIM directory.

FIELD

One embodiment is directed generally to identity management, and in particular, to identity management in a cloud-based system.

BACKGROUND INFORMATION

Generally, the use of cloud based applications (e.g., enterprise public cloud applications, third party cloud applications, etc.) is soaring, with access coming from a variety of devices (e.g., desktop and mobile devices) and a variety of users (e.g., employees, partners, customers, etc.). The abundant diversity and accessibility of cloud based applications has led access security to become a central concern. Typical security concerns in a cloud environment are unauthorized access, account hijacking, malicious insiders, etc. Accordingly, there is a need for secure access to cloud based applications, or applications located anywhere, regardless of from what device type or by what user type the applications are accessed.

SUMMARY

Embodiments provide a system and methods that implement a number of microservices in a stateless middle tier to provide cloud based multi-tenant identity and access management services.

In certain embodiments, an Identity Bridge (IDBridge) between an on-premises Active Directory (AD) and a cloud-based Identity Cloud Service (IDCS) is provided. A connection to an AD, coupled to a first network, is established, the AD including a plurality of organizational units (OUs), a plurality of groups and a plurality of users, each group being a member of an OU, and each user being a member of an OU and a group. A connection to an IDCS, coupled to a second network, is established, the IDCS including a System for Cross-domain Identity Management (SCIM) directory having a plurality of user resource entries and a plurality of group resource entries. The plurality of OUs are displayed in a graphical user interface (GUI), each OU being selectable by a user. A selection of one or more OUs is then received. Each member group of the selected OUs is displayed in the GUI, and each group is selectable by the user. A selection of one or more member groups of the selected OUs is then received. The users of the selected OUs are monitored to identify users that have been added, modified or deleted, and the selected member groups of the selected OUs are monitored to identify groups that have been added, modified or deleted. The identified users and groups are then synchronized to the SCIM directory.

DETAILED DESCRIPTION

Embodiments of the present invention provide an identity cloud service that implements a microservices based architecture and provides multi-tenant identity and data security management and secure access to cloud based applications. Embodiments support secure access for hybrid cloud deployments (i.e., cloud deployments which include a combination of a public cloud and a private cloud). Embodiments protect applications and data both in the cloud and on-premise. Embodiments support multi-channel access via web, mobile, and application programming interfaces (“APIs”). Embodiments manage access for different users, such as customers, partners, and employees. Embodiments manage, control, and audit access across the cloud as well as on-premise. Embodiments integrate with new and existing applications and identities. Embodiments are horizontally scalable.

Embodiments of the present invention provide a system and methods that implement a number of microservices in a stateless middle tier environment to provide cloud based multi-tenant identity and access management services. In certain embodiments, each requested identity management service is broken into real-time and near real-time tasks. The real-time tasks are handled by a microservice in the middle tier, while the near real-time tasks are offloaded to a message queue. Embodiments of the present invention implement access tokens that are consumed by a routing tier and a middle tier to enforce a security model for accessing the microservices. Accordingly, embodiments provide a cloud-scale Identity and Access Management (“IAM”) platform based on a multi-tenant, microservices architecture.

In certain hybrid cloud deployments, identities are first migrated from an on-premises LDAP server to an IDCS SCIM server. Legacy on-premises LDAP-based applications then access these identities in the IDCS SCIM server through an intermediary or proxy service. In certain embodiments, an LDAP to SCIM proxy service allows legacy LDAP-based applications to interact seamlessly with the IDCS SCIM server. Newly-deployed on-premises SCIM-based applications may access the IDCS SCIM server directly, as well as those legacy on-premises LDAP-based applications that have been re-written to support SCIM. In a hybrid cloud deployment, the LDAP to SCIM proxy service advantageously provides a single source of truth for identities, and avoids the complexities, disadvantages and limitations of identity federation and/or synchronization configurations.

In certain embodiments, an Identity Bridge (IDBridge) between an on-premises Active Directory (AD) and a cloud-based Identity Cloud Service (IDCS) is provided. A connection to an AD, coupled to a first network, is established, the AD including a plurality of organizational units (OUs), a plurality of groups and a plurality of users, each group being a member of an OU, and each user being a member of an OU and a group. A connection to an IDCS, coupled to a second network, is established, the IDCS including a System for Cross-domain Identity Management (SCIM) directory having a plurality of user resource entries and a plurality of group resource entries. The plurality of OUs are displayed in a graphical user interface (GUI), each OU being selectable by a user. A selection of one or more OUs is then received. Each member group of the selected OUs is displayed in the GUI, and each group is selectable by the user. A selection of one or more member groups of the selected OUs is then received. The users of the selected OUs are monitored to identify users that have been added, modified or deleted, and the selected member groups of the selected OUs are monitored to identify groups that have been added, modified or deleted. The identified users and groups are then synchronized to the SCIM directory.

Unified Security of Access

One embodiment protects applications and data in a cloud environment as well as in an on-premise environment. The embodiment secures access to any application from any device by anyone. The embodiment provides protection across both environments since inconsistencies in security between the two environments may result in higher risks. For example, such inconsistencies may cause a sales person to continue having access to their Customer Relationship Management (“CRM”) account even after they have defected to the competition. Accordingly, embodiments extend the security controls provisioned in the on-premise environment into the cloud environment. For example, if a person leaves a company, embodiments ensure that their accounts are disabled both on-premise and in the cloud.

Generally, users may access applications and/or data through many different channels such as web browsers, desktops, mobile phones, tablets, smart watches, other wearables, etc. Accordingly, one embodiment provides secured access across all these channels. For example, a user may use their mobile phone to complete a transaction they started on their desktop.

One embodiment further manages access for various users such as customers, partners, employees, etc. Generally, applications and/or data may be accessed not just by employees but by customers or third parties. Although many known systems take security measures when onboarding employees, they generally do not take the same level of security measures when giving access to customers, third parties, partners, etc., resulting in the possibility of security breaches by parties that are not properly managed. However, embodiments ensure that sufficient security measures are provided for access of each type of user and not just employees.

Identity Cloud Service

Embodiments provide an Identity Cloud Service (“IDCS”) that is a multi-tenant, cloud-scale, IAM platform. IDCS provides authentication, authorization, auditing, and federation. IDCS manages access to custom applications and services running on the public cloud, and on-premise systems. In an alternative or additional embodiment, IDCS may also manage access to public cloud services. For example, IDCS can be used to provide Single Sign On (“SSO”) functionality across such variety of services/applications/systems.

Embodiments are based on a multi-tenant, microservices architecture for designing, building, and delivering cloud-scale software services. Multi-tenancy refers to having one physical implementation of a service securely supporting multiple customers buying that service. A service is a software functionality or a set of software functionalities (such as the retrieval of specified information or the execution of a set of operations) that can be reused by different clients for different purposes, together with the policies that control its usage (e.g., based on the identity of the client requesting the service). In one embodiment, a service is a mechanism to enable access to one or more capabilities, where the access is provided using a prescribed interface and is exercised consistent with constraints and policies as specified by the service description.

In one embodiment, a microservice is an independently deployable service. In one embodiment, the term microservice contemplates a software architecture design pattern in which complex applications are composed of small, independent processes communicating with each other using language-agnostic APIs. In one embodiment, microservices are small, highly decoupled services and each may focus on doing a small task. In one embodiment, the microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms (e.g., an HTTP resource API). In one embodiment, microservices are easier to replace relative to a monolithic service that performs all or many of the same functions. Moreover, each of the microservices may be updated without adversely affecting the other microservices. In contrast, updates to one portion of a monolithic service may undesirably or unintentionally negatively affect the other portions of the monolithic service. In one embodiment, microservices may be beneficially organized around their capabilities. In one embodiment, the startup time for each of a collection of microservices is much less than the startup time for a single application that collectively performs all the services of those microservices. In some embodiments, the startup time for each of such microservices is about one second or less, while the startup time of such single application may be about a minute, several minutes, or longer.

In one embodiment, microservices architecture refers to a specialization (i.e., separation of tasks within a system) and implementation approach for service oriented architectures (“SOAs”) to build flexible, independently deployable software systems. Services in a microservices architecture are processes that communicate with each other over a network in order to fulfill a goal. In one embodiment, these services use technology-agnostic protocols. In one embodiment, the services have a small granularity and use lightweight protocols. In one embodiment, the services are independently deployable. By distributing functionalities of a system into different small services, the cohesion of the system is enhanced and the coupling of the system is decreased. This makes it easier to change the system and add functions and qualities to the system at any time. It also allows the architecture of an individual service to emerge through continuous refactoring, and hence reduces the need for a big up-front design and allows for releasing software early and continuously.

In one embodiment, in the microservices architecture, an application is developed as a collection of services, and each service runs a respective process and uses a lightweight protocol to communicate (e.g., a unique API for each microservice). In the microservices architecture, decomposition of a software into individual services/capabilities can be performed at different levels of granularity depending on the service to be provided. A service is a runtime component/process. Each microservice is a self-contained module that can talk to other modules/microservices. Each microservice has an unnamed universal port that can be contacted by others. In one embodiment, the unnamed universal port of a microservice is a standard communication channel that the microservice exposes by convention (e.g., as a conventional Hypertext Transfer Protocol (“HTTP”) port) and that allows any other module/microservice within the same service to talk to it. A microservice or any other self-contained functional module can be generically referred to as a “service”.

Embodiments provide multi-tenant identity management services. Embodiments are based on open standards to ensure ease of integration with various applications, delivering IAM capabilities through standards-based services.

Embodiments manage the lifecycle of user identities which entails the determination and enforcement of what an identity can access, who can be given such access, who can manage such access, etc. Embodiments run the identity management workload in the cloud and support security functionality for applications that are not necessarily in the cloud. The identity management services provided by the embodiments may be purchased from the cloud. For example, an enterprise may purchase such services from the cloud to manage their employees' access to their applications.

Embodiments provide system security, massive scalability, end user usability, and application interoperability. Embodiments address the growth of the cloud and the use of identity services by customers. The microservices based foundation addresses horizontal scalability requirements, while careful orchestration of the services addresses the functional requirements. Achieving both goals requires decomposition (wherever possible) of the business logic to achieve statelessness with eventual consistency, while much of the operational logic not subject to real-time processing is shifted to near-real-time by offloading to a highly scalable asynchronous event management system with guaranteed delivery and processing. Embodiments are fully multi-tenant from the web tier to the data tier in order to realize cost efficiencies and ease of system administration.

Embodiments are based on industry standards (e.g., OpenID Connect, OAuth2, Security Assertion Markup Language 2 (“SAML2”), System for Cross-domain Identity Management (“SCIM”), Representational State Transfer (“REST”), etc.) for ease of integration with various applications. One embodiment provides a cloud-scale API platform and implements horizontally scalable microservices for elastic scalability. The embodiment leverages cloud principles and provides a multi-tenant architecture with per-tenant data separation. The embodiment further provides per-tenant customization via tenant self-service. The embodiment is available via APIs for on-demand integration with other identity services, and provides continuous feature release.

One embodiment provides interoperability and leverages investments in identity management (“IDM”) functionality in the cloud and on-premise. The embodiment provides automated identity synchronization from on-premise Lightweight Directory Access Protocol (“LDAP”) data to cloud data and vice versa. The embodiment provides a SCIM identity bus between the cloud and the enterprise, and allows for different options for hybrid cloud deployments (e.g., identity federation and/or synchronization, SSO agents, user provisioning connectors, etc.).

Accordingly, one embodiment is a system that implements a number of microservices in a stateless middle tier to provide cloud-based multi-tenant identity and access management services. In one embodiment, each requested identity management service is broken into real-time and near-real-time tasks. The real-time tasks are handled by a microservice in the middle tier, while the near-real-time tasks are offloaded to a message queue. Embodiments implement tokens that are consumed by a routing tier to enforce a security model for accessing the microservices. Accordingly, embodiments provide a cloud-scale IAM platform based on a multi-tenant, microservices architecture.

Generally, known systems provide siloed access to applications provided by different environments, e.g., enterprise cloud applications, partner cloud applications, third-party cloud applications, and customer applications. Such siloed access may require multiple passwords, different password policies, different account provisioning and de-provisioning schemes, disparate audit, etc. However, one embodiment implements IDCS to provide unified IAM functionality over such applications.FIG. 1is a block diagram100of an example embodiment with IDCS118, providing a unified identity platform126for onboarding users and applications. The embodiment provides seamless user experience across various applications such as enterprise cloud applications102, partner cloud applications104, third-party cloud applications110, and customer applications112. Applications102,104,110,112may be accessed through different channels, for example, by a mobile phone user108via a mobile phone106, by a desktop computer user116via a browser114, etc. A web browser (commonly referred to as a browser) is a software application for retrieving, presenting, and traversing information resources on the World Wide Web. Examples of web browsers are Mozilla Firefox®, Google Chrome®, Microsoft Internet Explorer®, and Apple Safari®.

IDCS118provides a unified view124of a user's applications, a unified secure credential across devices and applications (via identity platform126), and a unified way of administration (via an admin console122). IDCS services may be obtained by calling IDCS APIs142. Such services may include, for example, login/SSO services128(e.g., OpenID Connect), federation services130(e.g., SAML), token services132(e.g., OAuth), directory services134(e.g., SCIM), provisioning services136(e.g., SCIM or Any Transport over Multiprotocol (“AToM”)), event services138(e.g., REST), and role-based access control (“RBAC”) services140(e.g., SCIM). IDCS118may further provide reports and dashboards120related to the offered services.

Integration Tools

Generally, it is common for large corporations to have an IAM system in place to secure access to their on-premise applications. Business practices are usually matured and standardized around an in-house IAM system such as “Oracle IAM Suite” from Oracle Corp. Even small to medium organizations usually have their business processes designed around managing user access through a simple directory solution such as Microsoft Active Directory (“AD”). To enable on-premise integration, embodiments provide tools that allow customers to integrate their applications with IDCS.

FIG. 2is a block diagram200of an example embodiment with IDCS202in a cloud environment208, providing integration with an AD204that is on-premise206. The embodiment provides seamless user experience across all applications including on-premise and third-party applications, for example, on-premise applications218and various applications/services in cloud208such as cloud services210, cloud applications212, partner applications214, and customer applications216. Cloud applications212may include, for example, Human Capital Management (“HCM”), CRM, talent acquisition (e.g., Oracle Taleo cloud service from Oracle Corp.), Configure Price and Quote (“CPQ”), etc. Cloud services210may include, for example, Platform as a Service (“PaaS”), Java, database, business intelligence (“BI”), documents, etc.

Applications210,212,214,216,218, may be accessed through different channels, for example, by a mobile phone user220via a mobile phone222, by a desktop computer user224via a browser226, etc. The embodiment provides automated identity synchronization from on-premise AD data to cloud data via a SCIM identity bus234between cloud208and the enterprise206. The embodiment further provides a SAML bus228for federating authentication from cloud208to on-premise AD204(e.g., using passwords232).

Generally, an identity bus is a service bus for identity related services. A service bus provides a platform for communicating messages from one system to another system. It is a controlled mechanism for exchanging information between trusted systems, for example, in a service oriented architecture (“SOA”). An identity bus is a logical bus built according to standard HTTP based mechanisms such as web service, web server proxies, etc. The communication in an identity bus may be performed according to a respective protocol (e.g., SCIM, SAML, OpenID Connect, etc.). For example, a SAML bus is an HTTP based connection between two systems for communicating messages for SAML services. Similarly, a SCIM bus is used to communicate SCIM messages according to the SCIM protocol.

The embodiment ofFIG. 2implements an identity (“ID”) bridge230that is a small binary (e.g., 1 MB in size) that can be downloaded and installed on-premise206alongside a customer's AD204. ID Bridge230listens to users and groups (e.g., groups of users) from the organizational units (“OUs”) chosen by the customer and synchronizes those users to cloud208. In one embodiment, users' passwords232are not synchronized to cloud208. Customers can manage application access for users by mapping IDCS users' groups to cloud applications managed in IDCS208. Whenever the users' group membership is changed on-premise206, their corresponding cloud application access changes automatically.

For example, an employee moving from engineering to sales can get near instantaneous access to the sales cloud and lose access to the developer cloud. When this change is reflected in on-premise AD204, cloud application access change is accomplished in near-real-time. Similarly, access to cloud applications managed in IDCS208is revoked for users leaving the company. For full automation, customers may set up SSO between on-premise AD204and IDCS208through, e.g., AD federation service (“AD/FS”, or some other mechanism that implements SAML federation) so that end users can get access to cloud applications210,212,214,216, and on-premise applications218with a single corporate password332.

FIG. 3is a block diagram300of an example embodiment that includes the same components202,206,208,210,212,214,216,218,220,222,224,226,228,234as inFIG. 2. However, in the embodiment ofFIG. 3, IDCS202provides integration with an on-premise IDM304such as Oracle IDM. Oracle IDM304is a software suite from Oracle Corp. for providing IAM functionality. The embodiment provides seamless user experience across all applications including on-premise and third-party applications. The embodiment provisions user identities from on-premise IDM304to IDCS208via SCIM identity bus234between cloud202and enterprise206. The embodiment further provides SAML bus228(or an OpenID Connect bus) for federating authentication from cloud208to on-premise206.

In the embodiment ofFIG. 3, an Oracle Identity Manager (“OIM”) Connector302from Oracle Corp., and an Oracle Access Manager (“OAM”) federation module306from Oracle Corp., are implemented as extension modules of Oracle IDM304. A connector is a module that has physical awareness about how to talk to a system. OIM is an application configured to manage user identities (e.g., manage user accounts in different systems based on what a user should and should not have access to). OAM is a security application that provides access management functionality such as web SSO; identity context, authentication and authorization; policy administration; testing; logging; auditing; etc. OAM has built-in support for SAML. If a user has an account in IDCS202, OIM connector302and OAM federation306can be used with Oracle IDM304to create/delete that account and manage access from that account.

FIG. 4is a block diagram400of an example embodiment that includes the same components202,206,208,210,212,214,216,218,220,222,224,226,234as inFIGS. 2 and 3. However, in the embodiment ofFIG. 4, IDCS202provides functionality to extend cloud identities to on-premise applications218. The embodiment provides seamless view of the identity across all applications including on-premise and third-party applications. In the embodiment ofFIG. 4, SCIM identity bus234is used to synchronize data in IDCS202with on-premise LDAP data called “Cloud Cache”402. Cloud Cache402is disclosed in more detail below.

Generally, an application that is configured to communicate based on LDAP needs an LDAP connection. An LDAP connection may not be established by such application through a URL (unlike, e.g., “www.google.com” that makes a connection to Google) since the LDAP needs to be on a local network. In the embodiment ofFIG. 4, an LDAP-based application218makes a connection to Cloud Cache402, and Cloud Cache402establishes a connection to IDCS202and then pulls data from IDCS202as it is being requested. The communication between IDCS202and Cloud Cache402may be implemented according to the SCIM protocol. For example, Cloud Cache402may use SCIM bus234to send a SCIM request to IDCS202and receive corresponding data in return.

Generally, fully implementing an application includes building a consumer portal, running marketing campaigns on the external user population, supporting web and mobile channels, and dealing with user authentication, sessions, user profiles, user groups, application roles, password policies, self-service/registration, social integration, identity federation, etc. Generally, application developers are not identity/security experts. Therefore, on-demand identity management services are desired.

FIG. 5is a block diagram500of an example embodiment that includes the same components202,220,222,224,226,234,402, as inFIGS. 2-4. However, in the embodiment ofFIG. 5, IDCS202provides secure identity management on demand. The embodiment provides on demand integration with identity services of IDCS202(e.g., based on standards such as OpenID Connect, OAuth2, SAML2, or SCIM). Applications505(which may be on-premise, in a public cloud, or in a private cloud) may call identity service APIs504in IDCS202. The services provided by IDCS202may include, for example, self-service registration506, password management508, user profile management510, user authentication512, token management514, social integration516, etc.

In this embodiment, SCIM identity bus234is used to synchronize data in IDCS202with data in on-premise LDAP Cloud Cache402. Further, a “Cloud Gate”502running on a web server/proxy (e.g., NGINX, Apache, etc.) may be used by applications505to obtain user web SSO and REST API security from IDCS202. Cloud Gate502is a component that secures access to multi-tenant IDCS microservices by ensuring that client applications provide valid access tokens, and/or users successfully authenticate in order to establish SSO sessions. Cloud Gate502is further disclosed below. Cloud Gate502(enforcement point similar to webgate/webagent) enables applications running behind supported web servers to participate in SSO.

One embodiment provides SSO and cloud SSO functionality. A general point of entry for both on-premise IAM and IDCS in many organizations is SSO. Cloud SSO enables users to access multiple cloud resources with a single user sign-in. Often, organizations will want to federate their on-premise identities. Accordingly, embodiments utilize open standards to allow for integration with existing SSO to preserve and extend investment (e.g., until a complete, eventual transition to an identity cloud service approach is made).

One embodiment may provide the following functionalities:maintain an identity store to track user accounts, ownership, access, and permissions that have been authorized,integrate with workflow to facilitate various approvals (e.g., management, IT, human resources, legal, and compliance) needed for applications access,provision SaaS user accounts for selective devices (e.g., mobile and personal computer (“PC”)) with access to user portal containing many private and public cloud resources, andfacilitate periodic management attestation review for compliance with regulations and current job responsibilities.

In addition to these functions, embodiments may further provide:

cloud account provisioning to manage account life cycle in cloud applications,

extensive mobile security capabilities, and

dynamic authentication options.

One embodiment provides adaptive authentication and MFA. Generally, passwords and challenge questions have been seen as inadequate and susceptible to common attacks such as phishing. Most business entities today are looking at some form of MFA to reduce risk. To be successfully deployed, however, solutions need to be easily provisioned, maintained, and understood by the end user, as end users usually resist anything that interferes with their digital experience. Companies are looking for ways to securely incorporate bring your own device (“BYOD”), social identities, remote users, customers, and contractors, while making MFA an almost transparent component of a seamless user access experience. Within an MFA deployment, industry standards such as OAuth and OpenID Connect are essential to ensure integration of existing multifactor solutions and the incorporation of newer, adaptive authentication technology. Accordingly, embodiments define dynamic (or adaptive) authentication as the evaluation of available information (i.e., IP address, location, time of day, and biometrics) to prove an identity after a user session has been initiated. With the appropriate standards (e.g., open authentication (“OATH”) and fast identity online (“FIDO”)) integration and extensible identity management framework, embodiments provide MFA solutions that can be adopted, upgraded, and integrated easily within an IT organization as part of an end-to-end secure IAM deployment. When considering MFA and adaptive policies, organizations must implement consistent policies across on-premise and cloud resources, which in a hybrid IDCS and on-premise IAM environment requires integration between systems.

One embodiment provides user provisioning and certification. Generally, the fundamental function of an IAM solution is to enable and support the entire user provisioning life cycle. This includes providing users with the application access appropriate for their identity and role within the organization, certifying that they have the correct ongoing access permissions (e.g., as their role or the tasks or applications used within their role change over time), and promptly de-provisioning them as their departure from the organization may require. This is important not only for meeting various compliance requirements but also because inappropriate insider access is a major source of security breaches and attacks. An automated user provisioning capability within an identity cloud solution can be important not only in its own right but also as part of a hybrid IAM solution whereby IDCS provisioning may provide greater flexibility than an on-premise solution for transitions as a company downsizes, upsizes, merges, or looks to integrate existing systems with IaaS/PaaS/SaaS environments. An IDCS approach can save time and effort in one-off upgrades and ensure appropriate integration among necessary departments, divisions, and systems. The need to scale this technology often sneaks up on corporations, and the ability to deliver a scalable IDCS capability immediately across the enterprise can provide benefits in flexibility, cost, and control.

Generally, an employee is granted additional privileges (i.e., “privilege creep”) over the years as her/his job changes. Companies that are lightly regulated generally lack an “attestation” process that requires managers to regularly audit their employees' privileges (e.g., access to networks, servers, applications, and data) to halt or slow the privilege creep that results in over-privileged accounts. Accordingly, one embodiment may provide a regularly conducted (at least once a year) attestation process. Further, with mergers and acquisitions, the need for these tools and services increases exponentially as users are on SaaS systems, on-premise, span different departments, and/or are being de-provisioned or re-allocated. The move to cloud can further confuse this situation, and things can quickly escalate beyond existing, often manually managed, certification methods. Accordingly, one embodiment automates these functions and applies sophisticated analytics to user profiles, access history, provisioning/de-provisioning, and fine-grained entitlements.

One embodiment provides identity analytics. Generally, the ability to integrate identity analytics with the IAM engine for comprehensive certification and attestation can be critical to securing an organization's risk profile. Properly deployed identity analytics can demand total internal policy enforcement. Identity analytics that provide a unified single management view across cloud and on-premise are much needed in a proactive governance, risk, and compliance (“GRC”) enterprise environment, and can aid in providing a closed-loop process for reducing risk and meeting compliance regulations. Accordingly, one embodiment provides identity analytics that are easily customizable by the client to accommodate specific industry demands and government regulations for reports and analysis required by managers, executives, and auditors.

One embodiment provides self-service and access request functionality to improve the experience and efficiency of the end user and to reduce costs from help desk calls. Generally, while a number of companies deploy on-premise self-service access request for their employees, many have not extended these systems adequately outside the formal corporate walls. Beyond employee use, a positive digital customer experience increases business credibility and ultimately contributes to revenue increase, and companies not only save on customer help desk calls and costs but also improve customer satisfaction. Accordingly, one embodiment provides an identity cloud service environment that is based on open standards and seamlessly integrates with existing access control software and MFA mechanisms when necessary. The SaaS delivery model saves time and effort formerly devoted to systems upgrades and maintenance, freeing professional IT staff to focus on more core business applications.

One embodiment provides privileged account management (“PAM”). Generally, every organization, whether using SaaS, PaaS, IaaS, or on-premise applications, is vulnerable to unauthorized privileged account abuse by insiders with super-user access credentials such as system administrators, executives, HR officers, contractors, systems integrators, etc. Moreover, outside threats typically first breach a low-level user account to eventually reach and exploit privileged user access controls within the enterprise system. Accordingly, one embodiment provides PAM to prevent such unauthorized insider account use. The main component of a PAM solution is a password vault which may be delivered in various ways, e.g., as software to be installed on an enterprise server, as a virtual appliance also on an enterprise server, as a packaged hardware/software appliance, or as part of a cloud service. PAM functionality is similar to a physical safe used to store passwords kept in an envelope and changed periodically, with a manifest for signing them in and out. One embodiment allows for a password checkout as well as setting time limits, forcing periodic changes, automatically tracking checkout, and reporting on all activities. One embodiment provides a way to connect directly through to a requested resource without the user ever knowing the password. This capability also paves the way for session management and additional functionality.

Generally, most cloud services utilize APIs and administrative interfaces, which provide opportunities for infiltrators to circumvent security. Accordingly, one embodiment accounts for these holes in PAM practices as the move to the cloud presents new challenges for PAM. Many small to medium sized businesses now administer their own SaaS systems (e.g., Office 365), while larger companies increasingly have individual business units spinning up their own SaaS and IaaS services. These customers find themselves with PAM capabilities within the identity cloud service solutions or from their IaaS/PaaS provider but with little experience in handling this responsibility. Moreover, in some cases, many different geographically dispersed business units are trying to segregate administrative responsibilities for the same SaaS applications. Accordingly, one embodiment allows customers in these situations to link existing PAM into the overall identity framework of the identity cloud service and move toward greater security and compliance with the assurance of scaling to cloud load requirements as business needs dictate.

API Platform

Embodiments provide an API platform that exposes a collection of capabilities as services. The APIs are aggregated into microservices and each microservice exposes one or more of the APIs. That is, each microservice may expose different types of APIs. In one embodiment, each microservice communicates only through its APIs. In one embodiment, each API may be a microservice. In one embodiment, multiple APIs are aggregated into a service based on a target capability to be provided by that service (e.g., OAuth, SAML, Admin, etc.). As a result, similar APIs are not exposed as separate runtime processes. The APIs are what is made available to a service consumer to use the services provided by IDCS.

Generally, in the web environment of IDCS, a URL includes three parts: a host, a microservice, and a resource (e.g., host/microservice/resource). In one embodiment, the microservice is characterized by having a specific URL prefix, e.g., “host/oauth/v1” where the actual microservice is “oauth/v1”, and under “oauth/v1” there are multiple APIs, e.g., an API to request tokens: “host/oauth/v1/token”, an API to authenticate a user: “host/oauth/v1/authorize”, etc. That is, the URL implements a microservice, and the resource portion of the URL implements an API. Accordingly, multiple APIs are aggregated under the same microservice. In one embodiment, the host portion of the URL identifies a tenant (e.g., https://tenant3.identity.oraclecloud.com:/oauth/v1/token”).

Configuring applications that integrate with external services with the necessary endpoints and keeping that configuration up to date is typically a challenge. To meet this challenge, embodiments expose a public discovery API at a well-known location from where applications can discover the information about IDCS they need in order to consume IDCS APIs. In one embodiment, two discovery documents are supported: IDCS Configuration (which includes IDCS, SAML, SCIM, OAuth, and OpenID Connect configuration, at e.g., <IDCS-URL>/.well-known/idcs-configuration), and Industry-standard OpenID Connect Configuration (at, e.g., <IDCS-URL>/.well-known/openid-configuration). Applications can retrieve discovery documents by being configured with a single IDCS URL.

FIG. 6is a block diagram providing a system view600of IDCS in one embodiment. InFIG. 6, any one of a variety of applications/services602may make HTTP calls to IDCS APIs to use IDCS services. Examples of such applications/services602are web applications, native applications (e.g., applications that are built to run on a specific operating system, such as Windows applications, iOS applications, Android applications, etc.), web services, customer applications, partner applications, or any services provided by a public cloud, such as Software as a Service (“SaaS”), PaaS, and Infrastructure as a Service (“IaaS”).

In one embodiment, the HTTP requests of applications/services602that require IDCS services go through an Oracle Public Cloud BIG-IP appliance604and an IDCS BIG-IP appliance606(or similar technologies such as a Load Balancer, or a component called a Cloud Load Balancer as a Service (“LBaaS”) that implements appropriate security rules to protect the traffic). However, the requests can be received in any manner. At IDCS BIG-IP appliance606(or, as applicable, a similar technology such as a Load Balancer or a Cloud LBaaS), a cloud provisioning engine608performs tenant and service orchestration. In one embodiment, cloud provisioning engine608manages internal security artifacts associated with a new tenant being on-boarded into the cloud or a new service instance purchased by a customer.

The HTTP requests are then received by an IDCS web routing tier610that implements a security gate (i.e., Cloud Gate) and provides service routing and microservices registration and discovery612. Depending on the service requested, the HTTP request is forwarded to an IDCS microservice in the IDCS middle tier614. IDCS microservices process external and internal HTTP requests. IDCS microservices implement platform services and infrastructure services. IDCS platform services are separately deployed Java-based runtime services implementing the business of IDCS. IDCS infrastructure services are separately deployed runtime services providing infrastructure support for IDCS. IDCS further includes infrastructure libraries that are common code packaged as shared libraries used by IDCS services and shared libraries. Infrastructure services and libraries provide supporting capabilities as required by platform services for implementing their functionality.

Platform Services

In one embodiment, IDCS supports standard authentication protocols, hence IDCS microservices include platform services such as OpenID Connect, OAuth, SAML2, System for Cross-domain Identity Management++ (“SCIM++”), etc.

The OpenID Connect platform service implements standard OpenID Connect Login/Logout flows. Interactive web-based and native applications leverage standard browser-based OpenID Connect flow to request user authentication, receiving standard identity tokens that are JavaScript Object Notation (“JSON”) Web Tokens (“JWTs”) conveying the user's authenticated identity. Internally, the runtime authentication model is stateless, maintaining the user's authentication/session state in the form of a host HTTP cookie (including the JWT identity token). The authentication interaction initiated via the OpenID Connect protocol is delegated to a trusted SSO service that implements the user login/logout ceremonies for local and federated logins. Further details of this functionality are disclosed below with reference toFIGS. 10 and 11. In one embodiment, OpenID Connect functionality is implemented according to, for example, OpenID Foundation standards.

The OAuth2 platform service provides token authorization services. It provides a rich API infrastructure for creating and validating access tokens conveying user rights to make API calls. It supports a range of useful token grant types, enabling customers to securely connect clients to their services. It implements standard 2-legged and 3-legged OAuth2 token grant types. Support for OpenID Connect (“OIDC”) enables compliant applications (OIDC relaying parties (“RP”s)) to integrate with IDCS as the identity provider (OIDC OpenID provider (“OP”)). Similarly, the integration of IDCS as OIDC RP with social OIDC OP (e.g., Facebook, Google, etc.) enables customers to allow social identities policy-based access to applications. In one embodiment, OAuth functionality is implemented according to, for example, Internet Engineering Task Force (“IETF”), Request for Comments (“RFC”) 6749.

The SAML2 platform service provides identity federation services. It enables customers to set up federation agreements with their partners based on SAML identity provider (“IDP”) and SAML service provider (“SP”) relationship models. In one embodiment, the SAML2 platform service implements standard SAML2 Browser POST Login and Logout Profiles. In one embodiment, SAML functionality is implemented according to, for example, IETF, RFC 7522.

SCIM is an open standard for automating the exchange of user identity information between identity domains or information technology (“IT”) systems, as provided by, e.g., IETF, RFCs 7642, 7643, 7644. The SCIM++ platform service provides identity administration services and enables customers to access IDP features of IDCS. The administration services expose a set of stateless REST interfaces (i.e., APIs) that cover identity lifecycle, password management, group management, etc., exposing such artifacts as web-accessible resources.

All IDCS configuration artifacts are resources, and the APIs of the administration services allow for managing IDCS resources (e.g., users, roles, password policies, applications, SAML/OIDC identity providers, SAML service providers, keys, certifications, notification templates, etc.). Administration services leverage and extend the SCIM standard to implement schema-based REST APIs for Create, Read, Update, Delete, and Query (“CRUDQ”) operations on all IDCS resources. Additionally, all internal resources of IDCS used for administration and configuration of IDCS itself are exposed as SCIM-based REST APIs. Access to the identity store618is isolated to the SCIM++ API.

In one embodiment, for example, the SCIM standard is implemented to manage the users and groups resources as defined by the SCIM specifications, while SCIM++ is configured to support additional IDCS internal resources (e.g., password policies, roles, settings, etc.) using the language defined by the SCIM standard.

The Administration service supports the SCIM 2.0 standard endpoints with the standard SCIM 2.0 core schemas and schema extensions where needed. In addition, the Administration service supports several SCIM 2.0 compliant endpoint extensions to manage other IDCS resources, for example, Users, Groups, Applications, Settings, etc. The Administration service also supports a set of remote procedure call-style (“RPC-style”) REST interfaces that do not perform CRUDQ operations but instead provide a functional service, for example, “UserPasswordGenerator,” “UserPasswordValidator,” etc.

IDCS Administration APIs use the OAuth2 protocol for authentication and authorization. IDCS supports common OAuth2 scenarios such as scenarios for web server, mobile, and JavaScript applications. Access to IDCS APIs is protected by access tokens. To access IDCS Administration APIs, an application needs to be registered as an OAuth2 client or an IDCS Application (in which case the OAuth2 client is created automatically) through the IDCS Administration console and be granted desired IDCS Administration Roles. When making IDCS Administration API calls, the application first requests an access token from the IDCS OAuth2 Service. After acquiring the token, the application sends the access token to the IDCS API by including it in the HTTP authorization header. Applications can use IDCS Administration REST APIs directly, or use an IDCS Java Client API Library.

Infrastructure Services

The IDCS infrastructure services support the functionality of IDCS platform services. These runtime services include an event processing service (for asynchronously processing user notifications, application subscriptions, and auditing to database); a job scheduler service (for scheduling and executing jobs, e.g., executing immediately or at a configured time long-running tasks that do not require user intervention); a cache management service; a storage management service (for integrating with a public cloud storage service); a reports service (for generating reports and dashboards); an SSO service (for managing internal user authentication and SSO); a user interface (“UI”) service (for hosting different types of UI clients); and a service manager service. Service manager is an internal interface between the Oracle Public Cloud and IDCS. Service manager manages commands issued by the Oracle Public Cloud, where the commands need to be implemented by IDCS. For example, when a customer signs up for an account in a cloud store before they can buy something, the cloud sends a request to IDCS asking to create a tenant. In this case, service manager implements the cloud specific operations that the cloud expects IDCS to support.

An IDCS microservice may call another IDCS microservice through a network interface (i.e., an HTTP request).

In one embodiment, IDCS may also provide a schema service (or a persistence service) that allows for using a database schema. A schema service allows for delegating the responsibility of managing database schemas to IDCS. Accordingly, a user of IDCS does not need to manage a database since there is an IDCS service that provides that functionality. For example, the user may use the database to persist schemas on a per tenant basis, and when there is no more space in the database, the schema service will manage the functionality of obtaining another database and growing the space so that the users do not have to manage the database themselves.

IDCS further includes data stores which are data repositories required/generated by IDCS, including an identity store618(storing users, groups, etc.), a global database620(storing configuration data used by IDCS to configure itself), an operational schema622(providing per tenant schema separation and storing customer data on a per customer basis), an audit schema624(storing audit data), a caching cluster626(storing cached objects to speed up performance), etc. All internal and external IDCS consumers integrate with the identity services over standards-based protocols. This enables use of a domain name system (“DNS”) to resolve where to route requests, and decouples consuming applications from understanding the internal implementation of identity services.

Real-Time and Near Real-Time Tasks

IDCS separates the tasks of a requested service into synchronous real-time and asynchronous near-real-time tasks, where real-time tasks include only the operations that are needed for the user to proceed. In one embodiment, a real-time task is a task that is performed with minimal delay, and a near-real-time task is a task that is performed in the background without the user having to wait for it. In one embodiment, a real-time task is a task that is performed with substantially no delay or with negligible delay, and appears to a user as being performed almost instantaneously.

The real-time tasks perform the main business functionality of a specific identity service. For example, when requesting a login service, an application sends a message to authenticate a user's credentials and get a session cookie in return. What the user experiences is logging into the system. However, several other tasks may be performed in connection with the user's logging in, such as validating who the user is, auditing, sending notifications, etc. Accordingly, validating the credentials is a task that is performed in real-time so that the user is given an HTTP cookie to start a session, but the tasks related to notifications (e.g., sending an email to notify the creation of an account), audits (e.g., tracking/recording), etc., are near-real-time tasks that can be performed asynchronously so that the user can proceed with least delay.

When an HTTP request for a microservice is received, the corresponding real-time tasks are performed by the microservice in the middle tier, and the remaining near-real-time tasks such as operational logic/events that are not necessarily subject to real-time processing are offloaded to message queues628that support a highly scalable asynchronous event management system630with guaranteed delivery and processing. Accordingly, certain behaviors are pushed from the front end to the backend to enable IDCS to provide high level service to the customers by reducing latencies in response times. For example, a login process may include validation of credentials, submission of a log report, updating of the last login time, etc., but these tasks can be offloaded to a message queue and performed in near-real-time as opposed to real-time.

In one example, a system may need to register or create a new user. The system calls an IDCS SCIM API to create a user. The end result is that when the user is created in identity store618, the user gets a notification email including a link to reset their password. When IDCS receives a request to register or create a new user, the corresponding microservice looks at configuration data in the operational database (located in global database620inFIG. 6) and determines that the “create user” operation is marked with a “create user” event which is identified in the configuration data as an asynchronous operation. The microservice returns to the client and indicates that the creation of the user is done successfully, but the actual sending of the notification email is postponed and pushed to the backend. In order to do so, the microservice uses a messaging API616to queue the message in queue628which is a store.

In order to dequeue queue628, a messaging microservice, which is an infrastructure microservice, continually runs in the background and scans queue628looking for events in queue628. The events in queue628are processed by event subscribers630such as audit, user notification, application subscriptions, data analytics, etc. Depending on the task indicated by an event, event subscribers630may communicate with, for example, audit schema624, a user notification service634, an identity event subscriber632, etc. For example, when the messaging microservice finds the “create user” event in queue628, it executes the corresponding notification logic and sends the corresponding email to the user.

In one embodiment, queue628queues operational events published by microservices614as well as resource events published by APIs616that manage IDCS resources.

IDCS uses a real-time caching structure to enhance system performance and user experience. The cache itself may also be provided as a microservice. IDCS implements an elastic cache cluster626that grows as the number of customers supported by IDCS scales. Cache cluster626may be implemented with a distributed data grid which is disclosed in more detail below. In one embodiment, write-only resources bypass cache.

In one embodiment, IDCS runtime components publish health and operational metrics to a public cloud monitoring module636that collects such metrics of a public cloud such as Oracle Public Cloud from Oracle Corp.

In one embodiment, IDCS may be used to create a user. For example, a client application602may issue a REST API call to create a user. Admin service (a platform service in614) delegates the call to a user manager (an infrastructure library/service in614), which in turn creates the user in the tenant-specific ID store stripe in ID store618. On “User Create Success”, the user manager audits the operation to the audit table in audit schema624, and publishes an “identity.user.create.success” event to message queue628. Identity subscriber632picks up the event and sends a “Welcome” email to the newly created user, including newly created login details.

In one embodiment, IDCS may be used to grant a role to a user, resulting in a user provisioning action. For example, a client application602may issue a REST API call to grant a user a role. Admin service (a platform service in614) delegates the call to a role manager (an infrastructure library/service in614), who grants the user a role in the tenant-specific ID store stripe in ID store618. On “Role Grant Success”, the role manager audits the operations to the audit table in audit schema624, and publishes an “identity.user.role.grant.success” event to message queue628. Identity subscriber632picks up the event and evaluates the provisioning grant policy. If there is an active application grant on the role being granted, a provisioning subscriber performs some validation, initiates account creation, calls out the target system, creates an account on the target system, and marks the account creation as successful. Each of these functionalities may result in publishing of corresponding events, such as “prov.account.create.initiate”, “prov.target.create.initiate”, “prov.target.create.success”, or “prov.account.create.success”. These events may have their own business metrics aggregating number of accounts created in the target system over the last N days.

In one embodiment, IDCS may be used for a user to log in. For example, a client application602may use one of the supported authentication flows to request a login for a user. IDCS authenticates the user, and upon success, audits the operation to the audit table in audit schema624. Upon failure, IDCS audits the failure in audit schema624, and publishes “login.user.login.failure” event in message queue628. A login subscriber picks up the event, updates its metrics for the user, and determines if additional analytics on the user's access history need to be performed.

Accordingly, by implementing “inversion of control” functionality (e.g., changing the flow of execution to schedule the execution of an operation at a later time so that the operation is under the control of another system), embodiments enable additional event queues and subscribers to be added dynamically to test new features on a small user sample before deploying to broader user base, or to process specific events for specific internal or external customers.

Stateless Functionality

IDCS microservices are stateless, meaning the microservices themselves do not maintain state. “State” refers to the data that an application uses in order to perform its capabilities. IDCS provides multi-tenant functionality by persisting all state into tenant specific repositories in the IDCS data tier. The middle tier (i.e., the code that processes the requests) does not have data stored in the same location as the application code. Accordingly, IDCS is highly scalable, both horizontally and vertically.

To scale vertically (or scale up/down) means to add resources to (or remove resources from) a single node in a system, typically involving the addition of CPUs or memory to a single computer. Vertical scalability allows an application to scale up to the limits of its hardware. To scale horizontally (or scale out/in) means to add more nodes to (or remove nodes from) a system, such as adding a new computer to a distributed software application. Horizontal scalability allows an application to scale almost infinitely, bound only by the amount of bandwidth provided by the network.

Stateless-ness of the middle tier of IDCS makes it horizontally scalable just by adding more CPUs, and the IDCS components that perform the work of the application do not need to have a designated physical infrastructure where a particular application is running. Stateless-ness of the IDCS middle tier makes IDCS highly available, even when providing identity services to a very large number of customers/tenants. Each pass through an IDCS application/service is focused on CPU usage only to perform the application transaction itself but not use hardware to store data. Scaling is accomplished by adding more slices when the application is running, while data for the transaction is stored at a persistence layer where more copies can be added when needed.

The IDCS web tier, middle tier, and data tier can each scale independently and separately. The web tier can be scaled to handle more HTTP requests. The middle tier can be scaled to support more service functionality. The data tier can be scaled to support more tenants.

IDCS Functional View

FIG. 6Ais an example block diagram600bof a functional view of IDCS in one embodiment. In block diagram600b, the IDCS functional stack includes services, shared libraries, and data stores. The services include IDCS platform services640b, IDCS premium services650b, and IDCS infrastructure services662b. In one embodiment, IDCS platform services640band IDCS premium services650bare separately deployed Java-based runtime services implementing the business of IDCS, and IDCS infrastructure services662bare separately deployed runtime services providing infrastructure support for IDCS. The shared libraries include IDCS infrastructure libraries680bwhich are common code packaged as shared libraries used by IDCS services and shared libraries. The data stores are data repositories required/generated by IDCS, including identity store698b, global configuration700b, message store702b, global tenant704b, personalization settings706b, resources708b, user transient data710b, system transient data712b, per-tenant schemas (managed ExaData)714b, operational store (not shown), caching store (not shown), etc.

In one embodiment, IDCS provides various UIs602bfor a consumer of IDCS services, such as customer end user UI604b, customer admin UI606b, DevOps admin UI608b, and login UI610b. In one embodiment, IDCS allows for integration612bof applications (e.g., customer apps614b, partner apps616b, and cloud apps618b) and firmware integration620b. In one embodiment, various environments may integrate with IDCS to support their access control needs. Such integration may be provided by, for example, identity bridge622b(providing AD integration, WNA, and SCIM connector), Apache agent624b, or MSFT agent626b.

In one embodiment, internal and external IDCS consumers integrate with the identity services of IDCS over standards-based protocols628b, such as OpenID Connect630b, OAuth2632b, SAML2634b, SCIM636b, and REST/HTTP638b. This enables use of a domain name system (“DNS”) to resolve where to route requests, and decouples the consuming applications from understanding internal implementation of the identity services.

The IDCS functional view inFIG. 6Afurther includes public cloud infrastructure services that provide common functionality that IDCS depends on for user notifications (cloud notification service718b), file storage (cloud storage service716b), and metrics/alerting for DevOps (cloud monitoring service (EM)722band cloud metrics service (Graphite)720b).

Cloud Gate

In one embodiment, IDCS implements a “Cloud Gate” in the web tier. Cloud Gate is a web server plugin that enables web applications to externalize user SSO to an identity management system (e.g., IDCS), similar to WebGate or WebAgent technologies that work with enterprise IDM stacks. Cloud Gate acts as a security gatekeeper that secures access to IDCS APIs. In one embodiment, Cloud Gate is implemented by a web/proxy server plugin that provides a web Policy Enforcement Point (“PEP”) for protecting HTTP resources based on OAuth.

FIG. 7is a block diagram700of an embodiment that implements a Cloud Gate702running in a web server712and acting as a Policy Enforcement Point (“PEP”) configured to integrate with IDCS Policy Decision Point (“PDP”) using open standards (e.g., OAuth2, OpenID Connect, etc.) while securing access to web browser and REST API resources714of an application. In some embodiments, the PDP is implemented at OAuth and/or OpenID Connect microservices704. For example, when a user browser706sends a request to IDCS for a login of a user710, a corresponding IDCS PDP validates the credentials and then decides whether the credentials are sufficient (e.g., whether to request for further credentials such as a second password). In the embodiment ofFIG. 7, Cloud Gate702may act both as the PEP and as the PDP since it has a local policy.

As part of one-time deployment, Cloud Gate702is registered with IDCS as an OAuth2 client, enabling it to request OIDC and OAuth2 operations against IDCS. Thereafter, it maintains configuration information about an application's protected and unprotected resources, subject to request matching rules (how to match URLs, e.g., with wild cards, regular expressions, etc.). Cloud Gate702can be deployed to protect different applications having different security policies, and the protected applications can be multi-tenant.

During web browser-based user access, Cloud Gate702acts as an OIDC RP718initiating a user authentication flow. If user710has no valid local user session, Cloud Gate702re-directs the user to the SSO microservice and participates in the OIDC “Authorization Code” flow with the SSO microservice. The flow concludes with the delivery of a JWT as an identity token. Cloud Gate708validates the JWT (e.g., looks at signature, expiration, destination/audience, etc.) and issues a local session cookie for user710. It acts as a session manager716securing web browser access to protected resources and issuing, updating, and validating the local session cookie. It also provides a logout URL for removal of its local session cookie.

Cloud Gate702also acts as an HTTP Basic Auth authenticator, validating HTTP Basic Auth credentials against IDCS. This behavior is supported in both session-less and session-based (local session cookie) modes. No server-side IDCS session is created in this case.

During programmatic access by REST API clients708, Cloud Gate702may act as an OAuth2 resource server/filter720for an application's protected REST APIs714. It checks for the presence of a request with an authorization header and an access token. When client708(e.g., mobile, web apps, JavaScript, etc.) presents an access token (issued by IDCS) to use with a protected REST API714, Cloud Gate702validates the access token before allowing access to the API (e.g., signature, expiration, audience, etc.). The original access token is passed along unmodified.

Generally, OAuth is used to generate either a client identity propagation token (e.g., indicating who the client is) or a user identity propagation token (e.g., indicating who the user is). In the embodiments, the implementation of OAuth in Cloud Gate is based on a JWT which defines a format for web tokens, as provided by, e.g., IETF, RFC 7519.

When a user logs in, a JWT is issued. The JWT is signed by IDCS and supports multi-tenant functionality in IDCS. Cloud Gate validates the JWT issued by IDCS to allow for multi-tenant functionality in IDCS. Accordingly, IDCS provides multi-tenancy in the physical structure as well as in the logical business process that underpins the security model.

Tenancy Types

IDCS specifies three types of tenancies: customer tenancy, client tenancy, and user tenancy. Customer or resource tenancy specifies who the customer of IDCS is (i.e., for whom is the work being performed). Client tenancy specifies which client application is trying to access data (i.e., what application is doing the work). User tenancy specifies which user is using the application to access data (i.e., by whom is the work being performed). For example, when a professional services company provides system integration functionality for a warehouse club and uses IDCS for providing identity management for the warehouse club systems, user tenancy corresponds to the professional services company, client tenancy is the application that is used to provide system integration functionality, and customer tenancy is the warehouse club.

Separation and identification of these three tenancies enables multi-tenant functionality in a cloud-based service. Generally, for on-premise software that is installed on a physical machine on-premise, there is no need to specify three different tenancies since a user needs to be physically on the machine to log in. However, in a cloud-based service structure, embodiments use tokens to determine who is using what application to access which resources. The three tenancies are codified by tokens, enforced by Cloud Gate, and used by the business services in the middle tier. In one embodiment, an OAuth server generates the tokens. In various embodiments, the tokens may be used in conjunction with any security protocol other than OAuth.

Decoupling user, client, and resource tenancies provides substantial business advantages for the users of the services provided by IDCS. For example, it allows a service provider that understands the needs of a business (e.g., a healthcare business) and their identity management problems to buy services provided by IDCS, develop their own backend application that consumes the services of IDCS, and provide the backend applications to the target businesses. Accordingly, the service provider may extend the services of IDCS to provide their desired capabilities and offer those to certain target businesses. The service provider does not have to build and run software to provide identity services but can instead extend and customize the services of IDCS to suit the needs of the target businesses.

Some known systems only account for a single tenancy which is customer tenancy. However, such systems are inadequate when dealing with access by a combination of users such as customer users, customer's partners, customer's clients, clients themselves, or clients that customer has delegated access to. Defining and enforcing multiple tenancies in the embodiments facilitates the identity management functionality over such variety of users.

In one embodiment, one entity of IDCS does not belong to multiple tenants at the same time; it belongs to only one tenant, and a “tenancy” is where artifacts live. Generally, there are multiple components that implement certain functions, and these components can belong to tenants or they can belong to infrastructure. When infrastructure needs to act on behalf of tenants, it interacts with an entity service on behalf of the tenant. In that case, infrastructure itself has its own tenancy and customer has its own tenancy. When a request is submitted, there can be multiple tenancies involved in the request.

For example, a client that belongs to “tenant 1” may execute a request to get a token for “tenant 2” specifying a user in “tenant 3.” As another example, a user living in “tenant 1” may need to perform an action in an application owned by “tenant 2”. Thus, the user needs to go to the resource namespace of “tenant 2” and request a token for themselves. Accordingly, delegation of authority is accomplished by identifying “who” can do “what” to “whom.” As yet another example, a first user working for a first organization (“tenant 1”) may allow a second user working for a second organization (“tenant 2”) to have access to a document hosted by a third organization (“tenant 3”).

In one example, a client in “tenant 1” may request an access token for a user in “tenant 2” to access an application in “tenant 3”. The client may do so by invoking an OAuth request for the token by going to “http://tenant3/oauth/token”. The client identifies itself as a client that lives in “tenant 1” by including a “client assertion” in the request. The client assertion includes a client ID (e.g., “client 1”) and the client tenancy “tenant 1”. As “client 1” in “tenant 1”, the client has the right to invoke a request for a token on “tenant 3”, and the client wants the token for a user in “tenant 2”. Accordingly, a “user assertion” is also passed as part of the same HTTP request. The access token that is generated will be issued in the context of the target tenancy which is the application tenancy (“tenant 3”) and will include the user tenancy (“tenant 2”).

In one embodiment, in the data tier, each tenant is implemented as a separate stripe. From a data management perspective, artifacts live in a tenant. From a service perspective, a service knows how to work with different tenants, and the multiple tenancies are different dimensions in the business function of a service.FIG. 8illustrates an example system800implementing multiple tenancies in an embodiment. System800includes a client802that requests a service provided by a microservice804that understands how to work with data in a database806. The database includes multiple tenants808and each tenant includes the artifacts of the corresponding tenancy. In one embodiment, microservice804is an OAuth microservice requested through https://tenant3/oauth/token for getting a token. The function of the OAuth microservice is performed in microservice804using data from database806to verify that the request of client802is legitimate, and if it is legitimate, use the data from different tenancies808to construct the token. Accordingly, system800is multi-tenant in that it can work in a cross-tenant environment by not only supporting services coming into each tenancy, but also supporting services that can act on behalf of different tenants.

System800is advantageous since microservice804is physically decoupled from the data in database806, and by replicating the data across locations that are closer to the client, microservice804can be provided as a local service to the clients and system800can manage the availability of the service and provide it globally.

In one embodiment, microservice804is stateless, meaning that the machine that runs microservice804does not maintain any markers pointing the service to any specific tenants. Instead, a tenancy may be marked, for example, on the host portion of a URL of a request that comes in. That tenancy points to one of tenants808in database806. When supporting a large number of tenants (e.g., millions of tenants), microservice804cannot have the same number of connections to database806, but instead uses a connection pool810which provides the actual physical connections to database806in the context of a database user.

Generally, connections are built by supplying an underlying driver or provider with a connection string, which is used to address a specific database or server and to provide instance and user authentication credentials (e.g., “Server=sql_box;Database=Common;User ID=uid;Pwd=password;”). Once a connection has been built, it can be opened and closed, and properties (e.g., the command time-out length, or transaction, if one exists) can be set. The connection string includes a set of key-value pairs, dictated by the data access interface of the data provider. A connection pool is a cache of database connections maintained so that the connections can be reused when future requests to a database are required. In connection pooling, after a connection is created, it is placed in the pool and it is used again so that a new connection does not have to be established. For example, when there needs to be ten connections between microservice804and database808, there will be ten open connections in connection pool810, all in the context of a database user (e.g., in association with a specific database user, e.g., who is the owner of that connection, whose credentials are being validated, is it a database user, is it a system credential, etc.).

The connections in connection pool810are created for a system user that can access anything. Therefore, in order to correctly handle auditing and privileges by microservice804processing requests on behalf of a tenant, the database operation is performed in the context of a “proxy user”812associated with the schema owner assigned to the specific tenant. This schema owner can access only the tenancy that the schema was created for, and the value of the tenancy is the value of the schema owner. When a request is made for data in database806, microservice804uses the connections in connection pool810to provide that data. Accordingly, multi-tenancy is achieved by having stateless, elastic middle tier services process incoming requests in the context of (e.g., in association with) the tenant-specific data store binding established on a per request basis on top of the data connection created in the context of (e.g., in association with) the data store proxy user associated with the resource tenancy, and the database can scale independently of the services.

The following provides an example functionality for implementing proxy user812:

dbOperation=<prepare DB command to execute>

In this functionality, microservice804sets the “Proxy User” setting on the connection pulled from connection pool810to the “Tenant,” and performs the database operation in the context of the tenant while using the database connection in connection pool810.

When striping every table to configure different columns in a same database for different tenants, one table may include all tenants' data mixed together. In contrast, one embodiment provides a tenant-driven data tier. The embodiment does not stripe the same database for different tenants, but instead provides a different physical database per tenant. For example, multi-tenancy may be implemented by using a pluggable database (e.g., Oracle Database 12c from Oracle Corp.) where each tenant is allocated a separate partition. At the data tier, a resource manager processes the request and then asks for the data source for the request (separate from metadata). The embodiment performs runtime switch to a respective data source/store per request. By isolating each tenant's data from the other tenants, the embodiment provides improved data security.

In one embodiment, various tokens codify different tenancies. A URL token may identify the tenancy of the application that requests a service. An identity token may codify the identity of a user that is to be authenticated. An access token may identify multiple tenancies. For example, an access token may codify the tenancy that is the target of such access (e.g., an application tenancy) as well as the user tenancy of the user that is given access. A client assertion token may identify a client ID and the client tenancy. A user-assertion token may identify the user and the user tenancy.

In one embodiment, an identity token includes at least a claim indicating the user tenant name (i.e., where the user lives).

In one embodiment, an access token includes at least a claim indicating the resource tenant name at the time the request for the access token was made (e.g., the customer), a claim indicating the user tenant name, a claim indicating the name of the OAuth client making the request, and a claim indicating the client tenant name. In one embodiment, an access token may be implemented according to the following JSON functionality:

In one embodiment, a client assertion token includes at least a claim indicating the client tenant name, and a claim indicating the name of the OAuth client making the request.

The tokens and/or multiple tenancies described herein may be implemented in any multi-tenant cloud-based service other than IDCS. For example, the tokens and/or multiple tenancies described herein may be implemented in SaaS or Enterprise Resource Planning (“ERP”) services.

FIG. 9is a block diagram of a network view900of IDCS in one embodiment.FIG. 9illustrates network interactions that are performed in one embodiment between application “zones”904. Applications are broken into zones based on the required level of protection and the implementation of connections to various other systems (e.g., SSL zone, no SSL zone, etc.). Some application zones provide services that require access from the inside of IDCS, while some application zones provide services that require access from the outside of IDCS, and some are open access. Accordingly, a respective level of protection is enforced for each zone.

In the embodiment ofFIG. 9, service to service communication is performed using HTTP requests. In one embodiment, IDCS uses the access tokens described herein not only to provide services but also to secure access to and within IDCS itself. In one embodiment, IDCS microservices are exposed through RESTful interfaces and secured by the tokens described herein.

In the embodiment ofFIG. 9, any one of a variety of applications/services902may make HTTP calls to IDCS APIs to use IDCS services. In one embodiment, the HTTP requests of applications/services902go through an Oracle Public Cloud Load Balancing External Virtual IP address (“VIP”)906(or other similar technologies), a public cloud web routing tier908, and an IDCS Load Balancing Internal VIP appliance910(or other similar technologies), to be received by IDCS web routing tier912. IDCS web routing tier912receives the requests coming in from the outside or from the inside of IDCS and routes them across either an IDCS platform services tier914or an IDCS infrastructure services tier916. IDCS platform services tier914includes IDCS microservices that are invoked from the outside of IDCS, such as OpenID Connect, OAuth, SAML, SCIM, etc. IDCS infrastructure services tier916includes supporting microservices that are invoked from the inside of IDCS to support the functionality of other IDCS microservices. Examples of IDCS infrastructure microservices are UI, SSO, reports, cache, job scheduler, service manager, functionality for making keys, etc. An IDCS cache tier926supports caching functionality for IDCS platform services tier914and IDCS infrastructure services tier916.

By enforcing security both for outside access to IDCS and within IDCS, customers of IDCS can be provided with outstanding security compliance for the applications they run.

In the embodiment ofFIG. 9, other than the data tier918which communicates based on Structured Query Language (“SQL”) and the ID store tier920that communicates based on LDAP, OAuth protocol is used to protect the communication among IDCS components (e.g., microservices) within IDCS, and the same tokens that are used for securing access from the outside of IDCS are also used for security within IDCS. That is, web routing tier912uses the same tokens and protocols for processing the requests it receives regardless of whether a request is received from the outside of IDCS or from the inside of IDCS. Accordingly, IDCS provides a single consistent security model for protecting the entire system, thereby allowing for outstanding security compliance since the fewer security models implemented in a system, the more secure the system is.

In the IDCS cloud environment, applications communicate by making network calls. The network call may be based on an applicable network protocol such as HTTP, Transmission Control Protocol (“TCP”), User Datagram Protocol (“UDP”), etc. For example, an application “X” may communicate with an application “Y” based on HTTP by exposing application “Y” as an HTTP Uniform Resource Locator (“URL”). In one embodiment, “Y” is an IDCS microservice that exposes a number of resources each corresponding to a capability. When “X” (e.g., another IDCS microservice) needs to call “Y”, it constructs a URL that includes “Y” and the resource/capability that needs to be invoked (e.g., https:/host/Y/resource), and makes a corresponding REST call which goes through web routing tier912and gets directed to “Y”.

In one embodiment, a caller outside the IDCS may not need to know where “Y” is, but web routing tier912needs to know where application “Y” is running. In one embodiment, IDCS implements discovery functionality (implemented by an API of OAuth service) to determine where each application is running so that there is no need for the availability of static routing information.

In one embodiment, an enterprise manager (“EM”)922provides a “single pane of glass” that extends on-premise and cloud-based management to IDCS. In one embodiment, a “Chef” server924which is a configuration management tool from Chef Software, Inc., provides configuration management functionality for various IDCS tiers. In one embodiment, a service deployment infrastructure and/or a persistent stored module928may send OAuth2 HTTP messages to IDCS web routing tier912for tenant lifecycle management operations, public cloud lifecycle management operations, or other operations. In one embodiment, IDCS infrastructure services tier916may send ID/password HTTP messages to a public cloud notification service930or a public cloud storage service932.

Cloud Access Control—SSO

One embodiment supports lightweight cloud standards for implementing a cloud scale SSO service. Examples of lightweight cloud standards are HTTP, REST, and any standard that provides access through a browser (since a web browser is lightweight). On the contrary, SOAP is an example of a heavy cloud standard which requires more management, configuration, and tooling to build a client with. The embodiment uses OpenID Connect semantics for applications to request user authentication against IDCS. The embodiment uses lightweight HTTP cookie-based user session tracking to track user's active sessions at IDCS without statefull server-side session support. The embodiment uses JWT-based identity tokens for applications to use in mapping an authenticated identity back to their own local session. The embodiment supports integration with federated identity management systems, and exposes SAML IDP support for enterprise deployments to request user authentication against IDCS.

FIG. 10is a block diagram1000of a system architecture view of SSO functionality in IDCS in one embodiment. The embodiment enables client applications to leverage standards-based web protocols to initiate user authentication flows. Applications requiring SSO integration with a cloud system may be located in enterprise data centers, in remote partner data centers, or even operated by a customer on-premise. In one embodiment, different IDCS platform services implement the business of SSO, such as OpenID Connect for processing login/logout requests from connected native applications (i.e., applications utilizing OpenID Connect to integrate with IDCS); SAML IDP service for processing browser-based login/logout requests from connected applications; SAML SP service for orchestrating user authentication against an external SAML IDP; and an internal IDCS SSO service for orchestrating end user login ceremony including local or federated login flows, and for managing IDCS host session cookie. Generally, HTTP works either with a form or without a form. When it works with a form, the form is seen within a browser. When it works without a form, it functions as a client to server communication. Both OpenID Connect and SAML require the ability to render a form, which may be accomplished by presence of a browser or virtually performed by an application that acts as if there is a browser. In one embodiment, an application client implementing user authentication/SSO through IDCS needs to be registered in IDCS as an OAuth2 client and needs to obtain client identifier and credentials (e.g., ID/password, ID/certificate, etc.).

The example embodiment ofFIG. 10includes three components/microservices that collectively provide login capabilities, including two platform microservices: OAuth21004and SAML21006, and one infrastructure microservice: SSO1008. In the embodiment ofFIG. 10, IDCS provides an “Identity Metasystem” in which SSO services1008are provided over different types of applications, such as browser based web or native applications1010requiring 3-legged OAuth flow and acting as an OpenID Connect relaying party (“RP,” an application that outsources its user authentication function to an IDP), native applications1011requiring 2-legged OAuth flow and acting as an OpenID Connect RP, and web applications1012acting as a SAML SP.

Generally, an Identity Metasystem is an interoperable architecture for digital identity, allowing for employing a collection of digital identities based on multiple underlying technologies, implementations, and providers. LDAP, SAML, and OAuth are examples of different security standards that provide identity capability and can be the basis for building applications, and an Identity Metasystem may be configured to provide a unified security system over such applications. The LDAP security model specifies a specific mechanism for handling identity, and all passes through the system are to be strictly protected. SAML was developed to allow one set of applications securely exchange information with another set of applications that belong to a different organization in a different security domain. Since there is no trust between the two applications, SAML was developed to allow for one application to authenticate another application that does not belong to the same organization. OAuth provides OpenID Connect that is a lightweight protocol for performing web based authentication.

In the embodiment ofFIG. 10, when an OpenID application1010connects to an OpenID server in IDCS, its “channels” request SSO service. Similarly, when a SAML application1012connects to a SAML server in IDCS, its “channels” also request SSO service. In IDCS, a respective microservice (e.g., an OpenID microservice1004and a SAML microservice1006) will handle each of the applications, and these microservices request SSO capability from SSO microservice1008. This architecture can be expanded to support any number of other security protocols by adding a microservice for each protocol and then using SSO microservice1008for SSO capability. SSO microservice1008issues the sessions (i.e., an SSO cookie1014is provided) and is the only system in the architecture that has the authority to issue a session. An IDCS session is realized through the use of SSO cookie1014by browser1002. Browser1002also uses a local session cookie1016to manage its local session.

In one embodiment, for example, within a browser, a user may use a first application based on SAML and get logged in, and later use a second application built with a different protocol such as OAuth. The user is provided with SSO on the second application within the same browser. Accordingly, the browser is the state or user agent and maintains the cookies.

In one embodiment, SSO microservice1008provides login ceremony1018, ID/password recovery1020, first time login flow1022, an authentication manager1024, an HTTP cookie manager1026, and an event manager1028. Login ceremony1018implements SSO functionality based on customer settings and/or application context, and may be configured according to a local form (i.e., basic Auth), an external SAML IDP, an external OIDC IDP, etc. ID/password recovery1020is used to recover a user's ID and/or password. First time login flow1022is implemented when a user logs in for the first time (i.e., an SSO session does not yet exist). Authentication manager1024issues authentication tokens upon successful authentication. HTTP cookie manager1026saves the authentication token in an SSO cookie. Event manager1028publishes events related to SSO functionality.

In one embodiment, interactions between OAuth microservice1004and SSO microservice1008are based on browser redirects so that SSO microservice1008challenges the user using an HTML form, validates credentials, and issues a session cookie.

In one embodiment, for example, OAuth microservice1004may receive an authorization request from browser1002to authenticate a user of an application according to 3-legged OAuth flow. OAuth microservice1004then acts as an OIDC provider1030, redirects browser1002to SSO microservice1008, and passes along application context. Depending on whether the user has a valid SSO session or not, SSO microservice1008either validates the existing session or performs a login ceremony. Upon successful authentication or validation, SSO microservice1008returns authentication context to OAuth microservice1004. OAuth microservice1004then redirects browser1002to a callback URL with an authorization (“AZ”) code. Browser1002sends the AZ code to OAuth microservice1004to request the required tokens1032. Browser1002also includes its client credentials (obtained when registering in IDCS as an OAuth2 client) in the HTTP authorization header. OAuth microservice1004in return provides the required tokens1032to browser1002. In one embodiment, tokens1032provided to browser1002include JW identity and access tokens signed by the IDCS OAuth2 server. Further details of this functionality are disclosed below with reference toFIG. 11.

In one embodiment, for example, OAuth microservice1004may receive an authorization request from a native application1011to authenticate a user according to a 2-legged OAuth flow. In this case, an authentication manager1034in OAuth microservice1004performs the corresponding authentication (e.g., based on ID/password received from a client1011) and a token manager1036issues a corresponding access token upon successful authentication.

In one embodiment, for example, SAML microservice1006may receive an SSO POST request from a browser to authenticate a user of a web application1012that acts as a SAML SP. SAML microservice1006then acts as a SAML IDP1038, redirects browser1002to SSO microservice1008, and passes along application context. Depending on whether the user has a valid SSO session or not, SSO microservice1008either validates the existing session or performs a login ceremony. Upon successful authentication or validation, SSO microservice1008returns authentication context to SAML microservice1006. SAML microservice then redirects to the SP with required tokens.

In one embodiment, for example, SAML microservice1006may act as a SAML SP1040and go to a remote SAML IDP1042(e.g., an active directory federation service (“ADFS”)). One embodiment implements the standard SAML/AD flows. In one embodiment, interactions between SAML microservice1006and SSO microservice1008are based on browser redirects so that SSO microservice1008challenges the user using an HTML form, validates credentials, and issues a session cookie.

In one embodiment, the interactions between a component within IDCS (e.g.,1004,1006,1008) and a component outside IDCS (e.g.,1002,1011,1042) are performed through firewalls1044.

FIG. 11is a message sequence flow1100of SSO functionality provided by IDCS in one embodiment. When a user uses a browser1102to access a client1106(e.g., a browser-based application or a mobile/native application), Cloud Gate1104acts as an application enforcement point and enforces a policy defined in a local policy text file. If Cloud Gate1104detects that the user has no local application session, it requires the user to be authenticated. In order to do so, Cloud Gate1104redirects browser1102to OAuth2 microservice1110to initiate OpenID Connect login flow against the OAuth2 microservice1110(3-legged AZ Grant flow with scopes=“openid profile”).

The request of browser1102traverses IDCS routing tier web service1108and Cloud Gate1104and reaches OAuth2 microservice1110. OAuth2 microservice1110constructs the application context (i.e., metadata that describes the application, e.g., identity of the connecting application, client ID, configuration, what the application can do, etc.), and redirects browser1102to SSO microservice1112to log in.

If the user has a valid SSO session, SSO microservice1112validates the existing session without starting a login ceremony. If the user does not have a valid SSO session (i.e., no session cookie exists), the SSO microservice1112initiates the user login ceremony in accordance with customer's login preferences (e.g., displaying a branded login page). In order to do so, the SSO microservice1112redirects browser1102to a login application service1114implemented in JavaScript. Login application service1114provides a login page in browser1102. Browser1102sends a REST POST to the SSO microservice1112including login credentials. The SSO microservice1112generates an access token and sends it to Cloud Gate1104in a REST POST. Cloud Gate1104sends the authentication information to Admin SCIM microservice1116to validate the user's password. Admin SCIM microservice1116determines successful authentication and sends a corresponding message to SSO microservice1112.

In one embodiment, during the login ceremony, the login page does not display a consent page, as “login” operation requires no further consent. Instead, a privacy policy is stated on the login page, informing the user about certain profile attributes being exposed to applications. During the login ceremony, the SSO microservice1112respects customer's IDP preferences, and if configured, redirects to the IDP for authentication against the configured IDP.

Upon successful authentication or validation, SSO microservice1112redirects browser1102back to OAuth2 microservice1110with the newly created/updated SSO host HTTP cookie (e.g., the cookie that is created in the context of the host indicated by “HOSTURL”) containing the user's authentication token. OAuth2 microservice1110returns AZ Code (e.g., an OAuth concept) back to browser1102and redirects to Cloud Gate1104. Browser1102sends AZ Code to Cloud Gate1104, and Cloud Gate1104sends a REST POST to OAuth2 microservice1110to request the access token and the identity token. Both tokens are scoped to OAuth microservice1110(indicated by the audience token claim). Cloud Gate1104receives the tokens from OAuth2 microservice1110.

Cloud Gate1104uses the identity token to map the user's authenticated identity to its internal account representation, and it may save this mapping in its own HTTP cookie. Cloud Gate1104then redirects browser1102to client1106. Browser1102then reaches client1106and receives a corresponding response from client1106. From this point on, browser1102can access the application (i.e., client1106) seamlessly for as long as the application's local cookie is valid. Once the local cookie becomes invalid, the authentication process is repeated.

Cloud Gate1104further uses the access token received in a request to obtain “userinfo” from OAuth2 microservice1110or the SCIM microservice. The access token is sufficient to access the “userinfo” resource for the attributes allowed by the “profile” scope. It is also sufficient to access “/me” resources via the SCIM microservice. In one embodiment, by default, the received access token is only good for user profile attributes that are allowed under the “profile” scope. Access to other profile attributes is authorized based on additional (optional) scopes submitted in the AZ grant login request issued by Cloud Gate1104.

When the user accesses another OAuth2 integrated connecting application, the same process repeats.

In one embodiment, the SSO integration architecture uses a similar OpenID Connect user authentication flow for browser-based user logouts. In one embodiment, a user with an existing application session accesses Cloud Gate1104to initiate a logout. Alternatively, the user may have initiated the logout on the IDCS side. Cloud Gate1104terminates the application-specific user session, and initiates OAuth2 OpenID Provider (“OP”) logout request against OAuth2 microservice1110. OAuth2 microservice1110redirects to SSO microservice1112that kills the user's host SSO cookie. SSO microservice1112initiates a set of redirects (OAuth2 OP and SAML IDP) against known logout endpoints as tracked in user's SSO cookie.

In one embodiment, if Cloud Gate1104uses SAML protocol to request user authentication (e.g., login), a similar process starts between the SAML microservice and SSO microservice1112.

Cloud Cache

One embodiment provides a service/capability referred to as Cloud Cache. Cloud Cache is provided in IDCS to support communication with applications that are LDAP based (e.g., email servers, calendar servers, some business applications, etc.) since IDCS does not communicate according to LDAP while such applications are configured to communicate only based on LDAP. Typically, cloud directories are exposed via REST APIs and do not communicate according to the LDAP protocol. Generally, managing LDAP connections across corporate firewalls requires special configurations that are difficult to set up and manage.

To support LDAP based applications, Cloud Cache translates LDAP communications to a protocol suitable for communication with a cloud system. Generally, an LDAP based application uses a database via LDAP. An application may be alternatively configured to use a database via a different protocol such as SQL. However, LDAP provides a hierarchical representation of resources in tree structures, while SQL represents data as tables and fields. Accordingly, LDAP may be more desirable for searching functionality, while SQL may be more desirable for transactional functionality.

In one embodiment, services provided by IDCS may be used in an LDAP based application to, for example, authenticate a user of the applications (i.e., an identity service) or enforce a security policy for the application (i.e., a security service). In one embodiment, the interface with IDCS is through a firewall and based on HTTP (e.g., REST). Typically, corporate firewalls do not allow access to internal LDAP communication even if the communication implements Secure Sockets Layer (“SSL”), and do not allow a TCP port to be exposed through the firewall. However, Cloud Cache translates between LDAP and HTTP to allow LDAP based applications reach services provided by IDCS, and the firewall will be open for HTTP.

Generally, an LDAP directory may be used in a line of business such as marketing and development, and defines users, groups, works, etc. In one example, a marketing and development business may have different targeted customers, and for each customer, may have their own applications, users, groups, works, etc. Another example of a line of business that may run an LDAP cache directory is a wireless service provider. In this case, each call made by a user of the wireless service provider authenticates the user's device against the LDAP directory, and some of the corresponding information in the LDAP directory may be synchronized with a billing system. In these examples, LDAP provides functionality to physically segregate content that is being searched at runtime.

In one example, a wireless service provider may handle its own identity management services for their core business (e.g., regular calls), while using services provided by IDCS in support of a short term marketing campaign. In this case, Cloud Cache “flattens” LDAP when it has a single set of users and a single set of groups that it runs against the cloud. In one embodiment, any number of Cloud Caches may be implemented in IDCS.

Distributed Data Grid

In one embodiment, the cache cluster in IDCS is implemented based on a distributed data grid, as disclosed, for example, in U.S. Pat. Pub. No. 2016/0092540, the disclosure of which is hereby incorporated by reference. A distributed data grid is a system in which a collection of computer servers work together in one or more clusters to manage information and related operations, such as computations, within a distributed or clustered environment. A distributed data grid can be used to manage application objects and data that are shared across the servers. A distributed data grid provides low response time, high throughput, predictable scalability, continuous availability, and information reliability. In particular examples, distributed data grids, such as, e.g., the Oracle Coherence data grid from Oracle Corp., store information in-memory to achieve higher performance, and employ redundancy in keeping copies of that information synchronized across multiple servers, thus ensuring resiliency of the system and continued availability of the data in the event of failure of a server.

In one embodiment, IDCS implements a distributed data grid such as Coherence so that every microservice can request access to shared cache objects without getting blocked. Coherence is a proprietary Java-based in-memory data grid, designed to have better reliability, scalability, and performance than traditional relational database management systems. Coherence provides a peer to peer (i.e., with no central manager), in-memory, distributed cache.

FIG. 12illustrates an example of a distributed data grid1200which stores data and provides data access to clients1250and implements embodiments of the invention. A “data grid cluster”, or “distributed data grid”, is a system comprising a plurality of computer servers (e.g.,1220a,1220b,1220c, and1220d) which work together in one or more clusters (e.g.,1200a,1200b,1200c) to store and manage information and related operations, such as computations, within a distributed or clustered environment. While distributed data grid1200is illustrated as comprising four servers1220a,1220b,1220c,1220d, with five data nodes1230a,1230b,1230c,1230d, and1230ein a cluster1200a, the distributed data grid1200may comprise any number of clusters and any number of servers and/or nodes in each cluster. In an embodiment, distributed data grid1200implements the present invention.

As illustrated inFIG. 12, a distributed data grid provides data storage and management capabilities by distributing data over a number of servers (e.g.,1220a,1220b,1220c, and1220d) working together. Each server of the data grid cluster may be a conventional computer system such as, for example, a “commodity x86” server hardware platform with one to two processor sockets and two to four CPU cores per processor socket. Each server (e.g.,1220a,1220b,1220c, and1220d) is configured with one or more CPUs, Network Interface Cards (“NIC”), and memory including, for example, a minimum of 4 GB of RAM up to 64 GB of RAM or more. Server1220ais illustrated as having CPU1222a, Memory1224a, and NIC1226a(these elements are also present but not shown in the other Servers1220b,1220c,1220d). Optionally, each server may also be provided with flash memory (e.g., SSD1228a) to provide spillover storage capacity. When provided, the SSD capacity is preferably ten times the size of the RAM. The servers (e.g.,1220a,1220b,1220c,1220d) in a data grid cluster1200aare connected using high bandwidth NICs (e.g., PCI-X or PCIe) to a high-performance network switch1220(for example, gigabit Ethernet or better).

A cluster1200apreferably contains a minimum of four physical servers to avoid the possibility of data loss during a failure, but a typical installation has many more servers. Failover and failback are more efficient the more servers that are present in each cluster and the impact of a server failure on a cluster is lessened. To minimize communication time between servers, each data grid cluster is ideally confined to a single switch1202which provides single hop communication between servers. A cluster may thus be limited by the number of ports on the switch1202. A typical cluster will therefore include between 4 and 96 physical servers.

In most Wide Area Network (“WAN”) configurations of a distributed data grid1200, each data center in the WAN has independent, but interconnected, data grid clusters (e.g.,1200a,1200b, and1200c). A WAN may, for example, include many more clusters than shown inFIG. 12. Additionally, by using interconnected but independent clusters (e.g.,1200a,1200b,1200c) and/or locating interconnected, but independent, clusters in data centers that are remote from one another, the distributed data grid can secure data and service to clients1250against simultaneous loss of all servers in one cluster caused by a natural disaster, fire, flooding, extended power loss, and the like.

One or more nodes (e.g.,1230a,1230b,1230c,1230dand1230e) operate on each server (e.g.,1220a,1220b,1220c,1220d) of a cluster1200a. In a distributed data grid, the nodes may be, for example, software applications, virtual machines, or the like, and the servers may comprise an operating system, hypervisor, or the like (not shown) on which the node operates. In an Oracle Coherence data grid, each node is a Java virtual machine (“JVM”). A number of JVMs/nodes may be provided on each server depending on the CPU processing power and memory available on the server. JVMs/nodes may be added, started, stopped, and deleted as required by the distributed data grid. JVMs that run Oracle Coherence automatically join and cluster when started. JVMs/nodes that join a cluster are called cluster members or cluster nodes.

Architecture

Each client or server includes a bus or other communication mechanism for communicating information, and a processor coupled to bus for processing information. The processor may be any type of general or specific purpose processor. Each client or server may further include a memory for storing information and instructions to be executed by processor. The memory can be comprised of any combination of random access memory (“RAM”), read only memory (“ROM”), static storage such as a magnetic or optical disk, or any other type of computer readable media. Each client or server may further include a communication device, such as a network interface card, to provide access to a network. Therefore, a user may interface with each client or server directly, or remotely through a network, or any other method.

Computer readable media may be any available media that can be accessed by processor and includes both volatile and non-volatile media, removable and non-removable media, and communication media. Communication media may include computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and includes any information delivery media.

The processor may further be coupled via bus to a display, such as a Liquid Crystal Display (“LCD”). A keyboard and a cursor control device, such as a computer mouse, may be further coupled to bus to enable a user to interface with each client or server.

In one embodiment, the memory stores software modules that provide functionality when executed by the processor. The modules include an operating system that provides operating system functionality each client or server. The modules may further include a cloud identity management module for providing cloud identity management functionality, and all other functionality disclosed herein.

The clients may access a web service such as a cloud service. The web service may be implemented on a WebLogic Server from Oracle Corp. in one embodiment. In other embodiments, other implementations of a web service can be used. The web service accesses a database which stores cloud data.

As disclosed, embodiments implement a microservices based architecture to provide cloud-based multi-tenant IAM services. In one embodiment, each requested identity management service is broken into real-time tasks that are handled by a microservice in the middle tier, and near-real-time tasks that are offloaded to a message queue. Accordingly, embodiments provide a cloud-scale IAM platform.

IAM Functionality Example

In one embodiment, IAM functionality is implemented by software stored in memory or other computer readable or tangible medium, and executed by a processor.

A request is received for performing an identity management service. In one embodiment, the request includes a call to an API that identifies the identity management service and a microservice configured to perform the identity management service. In one embodiment, the microservice is a self-contained module that can communicate with other modules/microservices, and each microservice has an unnamed universal port that can be contacted by others. For example, in one embodiment, a variety of applications/services602may make HTTP calls to IDCS APIs to use IDCS microservices614as illustrated inFIG. 6. In one embodiment, a microservice is a runtime component/process.

In one embodiment, the request includes a URL. In one embodiment, the microservice is identified in a prefix of the URL. In one embodiment, a resource portion of the URL identifies the API. In one embodiment, a host portion of the URL identifies a tenancy of a resource related to the request. For example, in a URL such as “host/microservice/resource” in the web environment of IDCS, a microservice is characterized by having a specific URL prefix, e.g., “host/oauth/v1” where the actual microservice is “oauth/v1”, and under “oauth/v1” there are multiple APIs, e.g., an API to request tokens: “host/oauth/v1/token”, an API to authenticate a user: “host/oauth/v1/authorize”, etc. That is, the URL implements a microservice, and the resource portion of the URL implements an API. Accordingly, multiple APIs are aggregated under the same microservice. In one embodiment, the host portion of the URL identifies a tenant (e.g., https://tenant3.identity.oraclecloud.com:/oauth/v1/token”).

The request is then authenticated. In one embodiment, the request is authenticated by a security gate such as Cloud Gate as described herein, for example, with reference to web routing tier610inFIG. 6and/or cloud gate702inFIG. 7.

The microservice is then accessed based on the API, for example, as described herein with reference to the IDCS “API platform” and accessing microservices in IDCS middle tier614inFIG. 6. In one embodiment, communicating with the microservice is configured through an unnamed universal port of the microservice. In one embodiment, the unnamed universal port of a microservice is a standard communication channel that the microservice exposes by convention (e.g., as a conventional HTTP port) and that allows any other module/microservice within the same service to talk to it. In one embodiment, the microservice provides one or more capabilities by exposing one or more APIs. In one embodiment, communication with the microservice is implemented only through the one or more APIs. That is, the microservice can be reached/contacted only by making calls to such APIs. In one embodiment, communication with the microservice is configured according to a lightweight protocol. In one embodiment, the lightweight protocol includes HTTP and REST. In one embodiment, the request includes a call to a RESTful HTTP API. Accordingly, one embodiment provides dispatching functionality. Each HTTP request includes a URI and a verb. The embodiment parses the endpoint (host/service/resource) from the URI and combines it with the HTTP verb (e.g., POST, PUT, PATCH, or Delete) to dispatch (or invoke) the appropriate method of the appropriate module. This pattern is common to REST and is supported by various packages (e.g., Jersey).

The identity management service is then performed by the microservice, for example, as described herein with reference to the IDCS “API platform” and accessing microservices in IDCS middle tier614inFIG. 6. In one embodiment, the microservice is stateless, horizontally scalable, and independently deployable. In one embodiment, each physical implementation of the microservice is configured to securely support multiple tenants. In one embodiment, the identity management service includes a login service, an SSO service, a federation service, a token service, a directory service, a provisioning service, or an RBAC service.

Distributed High Availability (HA) Agent Architecture for Synchronizing an AD with a SCIM Directory

Embodiments of the present invention generally provide a distributed methodology for managing on-premises high availability (HA) software agents from the cloud, including, for example, checking the health of remote agents and suggesting remediation. In certain embodiments, connections to on-premises systems may be accomplished over standard http protocol without opening ports or maintaining connections to the on-premises systems.

FIG. 13presents a system block diagram1300for an Identity Bridge (IDBridge), in accordance with an embodiment of the present invention.

IDBridge1310is a distributed, lightweight windows-based (.NET) HA agent that synchronizes an on-premise enterprise identity store, such as Microsoft Active Directory (AD)1320, with a cloud-based identity store, such as IDCS1330. IDBridge communicates with AD1320over local network1315, and communicates with IDCS1330over network1335, such as, for example, the Internet. In certain embodiments, the connection to IDCS1330may use Hyper Text Transfer Protocol Secure (“HTTPS”) encryption and OAuth2 for authentication. Advantageously, from a technical perspective, IDBridge1310has a small installed size (˜1 MB) on the client computer, is simple to install and configure, does not require a special configuration in firewall1340, and has read-only access to AD1320.

In many embodiments, AD1320is the “source of truth” for identities (users and groups), and a single IDBridge1310monitors one AD domain. IDBridge1310monitors and synchronizes all users under user-selected organizational units (OUs) in AD1320, and advantageously allows the selection of specific groups to monitor and synchronize under the selected OUs. IDBridge1310stores connection information on-premises; the remainder of the configuration and state is fetched from, and updated on, IDCS1330. In certain embodiments, a single instance of IDBridge1310is configured for each AD domain, such as, for example, in an AD forest environment. Advantageously, the IDBridge1310instance for a given AD domain may be replaced with another IDBridge1310instance with very little effort. The connection information for AD1320and IDCS1330, and the list of OUs and groups to monitor, may be configured by an administrator using a graphical user interface (GUI).

In many embodiments, IDBridge1310does not sync user passwords, does not transmit AD1320passwords over the network to IDCS1330. In these embodiments, IDBridge1310syncs a limited set of user attributes, as required by the IDCS REST API. In certain embodiments, IDBridge1310monitors and synchronizes user and group identities using a filter. In other embodiments, AD passwords may be used to authenticate users to cloud applications using single sign-on (SSO).

Generally, the IDCS management endpoint ensures that each entity under the endpoint represents an AD domain, stores the list of monitored OUs and groups for each AD domain under its entity, stores the synchronization interval for each AD domain under its entity, stores the runtime state and status of sync for each AD domain under its entity, stores the state of each IDBridge instance for the AD domain under its entity, and provides a mechanism to trigger synchronization of the active IDBridge for an AD domain. The endpoint may be located on an administrative service of IDCS1330, and may named, for example, /IDBridgeSources.

In many embodiment, IDCS1330includes a System for Cross-domain Identity Management (SCIM) directory that includes SCIM resource entries that describe SCIM users and groups. Each SCIM resource entry includes a SCIM ID and SCIM attributes, such as, for example, an externalID and a resource type identifying the SCIM resource entry as belonging to a user or a group. Each SCIM attribute includes a name and one or more values.

FIGS. 14 to 18present various graphical user interfaces1400,1500,1600,1700and1800, respectively, for installation and configuration of IDBridge1310on a client computer, in accordance with embodiments of the present invention.

GUI1400includes window1402that receives AD domain name1410for IDBridge1310, and window1404that provides client ID1420and client secret1430for IDBridge1310. GUI1500includes a sequence of windows1502,1504,1506,1508and1510that install IDBridge1310. GUI1600includes window1602to receive IDCS universal resource location (URL)1610, as well as client ID1420and client secret1430. HTTP proxy details, such as, for example, proxy URL1622, proxy user name1624and proxy password1626, are received in a lower portion of window1602that is revealed in response to a selection of HTTP proxy checkbox1620. GUI1700includes window1702that receives AD domain name1410, domain controller host1710, domain controller port1720, and user name1730and password1740for connecting to AD1320.

GUI1800includes window1802that receives an initial selection of OUs and an initial selection of groups within the selected OUs. Pane1810presents a hierarchical display of OUs, and pane1820displays the groups within each selected OU. Various GUI widgets, such as, for example, check boxes, buttons, input fields, etc., are provided. As depicted inFIG. 18, the “Engineering” OU has been selected, as well as the “Quality” and “Development” OUs located under the “Engineering” OU. Several groups from these selected OUs have also been selected, i.e., the “QADemo” group from the “Quality” OU, the “Development” group from the “Development” OU, and the “Engineering Demo” group from the “Engineering” OU.

IDBridge1310generally includes two components, i.e., an IDBridge Service and an IDBridge User Interface (UI); other configurations, having fewer or greater number of components, are also contemplated. The IDBridge Service is a Windows service that continuously synchronizes changes to users in a specified list of OUs in AD1320, such as add, modify and delete, as well as changes to a selected list of groups in AD1320, such as modify, delete and membership changes. The IDBridge UI is a Windows-based GUI that collects AD credentials, cloud credentials and the list of OUs and groups to be monitored. In alternative embodiments, a web-based GUI may be used.

FIGS. 19A to 19Cpresent a graphical user interface1900for the IDBridge UI, in accordance with embodiments of the present invention. IDBridge UI1900includes window1902with Import tab1904, Server Settings tab1906, and Sync History tab1908.

Import tab1904allows the administrator to select a set of AD OUs and related groups to be monitored and synchronized by IDBridge1310. As depicted inFIG. 19A, Import tab1904includes panes1910and1920that receive a selection of OUs and related groups within the selected OUs. Pane1910presents a hierarchical display of OUs, and pane1920displays the groups within each selected OU, similar to panes1810and1820described above. Various GUI widgets, such as, for example, check boxes, buttons, input fields, etc., are provided. As depicted inFIG. 19A, the “Engineering” OU has been selected, as well as the “Quality” and “Development” OUs disposed under the “Engineering” OU. Several groups from these selected OUs have also been selected, i.e., the “QADemo” group from the “Quality” OU, the “Development” group from the “Development” OU, and the “Engineering Demo” group from the “Engineering” OU. This information is stored in a dedicated endpoint in IDCS1330.

Server Settings tab1906includes an Active Directory tab1930and an Oracle Public Cloud Server tab1940. Active Directory tab1930displays domain name1932, domain URL1934, and Bind user name1936and password1938. Domain name1932identifies the AD domain with which this IDBridge1310is associated. The domain URL1934identifies where the AD domain controller is installed. Bind user name1936and password1938are used to connect to AD1320, such as, for example, as administrator, administrator@oracle.com, oracle\administrator, etc.

Oracle Public Cloud Server tab1940(details not depicted) displays the IDCS URL, the client ID, the client secret, and proxy details. The IDCS URL is the IDCS URL for the customer (tenant). The client ID and client secret (described above) are used by IDBridge1310. The proxy details describe the connection to IDCS. These data are stored in the Windows Registry and are protected by Windows User Account Control. The keys will be stored under HKEY_LOCAL_MACHINE→SOFTWARE→Oracle→IDBridge section, which is writable only by the System Administrator. Accordingly, the installation is run under an ‘Administrator’ user in order to write to the Windows registry.

Sync History tab1908displays a sync data table1950. These data may be stored in a sync log in the IDBridge client computer memory. Generally, IDBridge1310polls AD1320at preset synchronization intervals and reports any changes to IDCS1330over a REST channel. In certain embodiments, IDBridge1310has several operational states, including Not Configured, Running, Connection Failed, Success and Failure. The Not Configured state indicates that IDBridge1310has not been configured. The Running state indicates that IDBridge1310is currently querying AD1320and pushing changes to IDCS1330. The Connection Failed state indicates that the previous sync cycle failed because of a connection failure to IDCS1330. The Success state indicates that the previous sync cycle completed successfully. The Failure state indicates that the previous sync cycle was not completed successfully.

Each row or data record of sync data table1950includes a Sync ID, a Status, a number of Records Processed, a duration and a Date Completed. For example, sync data record1952has a Sync ID of “AD0001,” a Status of “SUCCESS,” a number of Records Processed of “10,” a Duration of “01:05,” and a Date Completed of “7/16/2016 12:13:27 AM.” Detailed data1954may also be displayed for each row or data record of sync data table1950that includes the information described above, as well as additional data, such as, for example, a Start Date, a number of group records processed, a number of user Records processed, etc., as depicted inFIG. 19C.

Window1902may also display status information, such as the current sync status1960, the last sync date1962, etc. Additional information may also be displayed, such as, for example, a duration of the last sync cycle, a next sync time, a last sync message, etc.

The IDBridge Service is a Windows service that is installed, configured and run on an on-premises client computer to track the changes occurring in AD1320and synchronize the changes to IDCS1330. In many embodiments, IDBridge Service runs as an “NT Authority\NetworkService” account, having no password and minimum privileges on the local client computer, that is represented by HKCU. In this embodiment, all runtime keys that the IDBridge Service maintains, such as, for example, AD server cookies, sync time, sync state, etc., are stored in the HKCU Registry of the Network Service account. Because IDBridge UI is run with administrator privilege, settings related information, such as, for example, AD connection details, IDCS connection details, etc., may be stored in an HKEY_LOCAL_MACHINE (“HKLM”) registry and accessed in a read-only manner. Other settings, such as, for example, sync interval, etc., may be stored in IDCS1330under a specific endpoint, such as /IDBridgeSources.

As discussed above, changes in user profiles and group memberships are monitored and synchronized. Whenever a user within a selected OU from AD1320is added, modified or deleted, the update is synced to IDCS1330. And, the selected groups from AD1320are continuously tracked so that any membership addition or deletion is identified and appropriately synced to IDCS1330.

In many embodiments, IDBridge1310has two types of synchronization cycles, i.e., e.g., Periodic Synchronization and Heartbeat and Sync Now Synchronization. For Periodic Synchronization, the synchronization cycle runs at a pre-configured interval specified by the administrator from an IDCS admin console. For Heartbeat and Sync Now Synchronization, IDBridge1310sends a heartbeat message to IDCS1330every minute to report health data and listen for a Sync Now request from the IDCS admin console. If a synchronization cycle is requested, synchronization is started within a predetermined timed of the request, such as, for example, 1 minute, 2 minutes, 5 minutes, etc. Preferably, IDBridge1310includes an incremental sync mechanism in order to sync only the changes from AD1320to IDCS1310, and may run continuously in order to identify these changes.

Two features of Microsoft's Active Directory are used to support synchronization, i.e., the Unique Sequence Number (USN) and Directory Synchronization (DirSync) Control.

The USN is a number that is maintained for each entry in AD1320and indicates when the entry was last changed. The USN may be used to determine whether there have been any changes to user profiles under the selected OUs.

DirSync Control is an LDAP server extension that enables an application to search a directory partition for objects that have changed since a previous state. This is a PULL mechanism that requires the client to periodically query AD1320for changes. When a search is first performed using DirSync control, a null cookie is passed and AD1320will return all the matching entries along with a valid cookie. For subsequent searches, if the cookie is passed in the search request, AD1320will send only the changes that have occurred since that cookie was created. Generally, every search request sent by a client, as well as the response sent by a server, will have a cookie, so that the state is maintained and incremental changes alone can be identified using the cookie. This mechanism is used to determine changes to user profiles within the selected OUs and the selected groups in those OUs in AD1320.

After changes are detected in AD1320, those changes are synchronized to IDCS1330.

Table 1 describes the various kinds of changes that are tracked by IDBridge1310, and the expected mode of transmission of that change to IDCS1330.

TABLE 1AD ChangeIDBridge ActivityTransmission Mode to IDCSA new user isIDBridge uniquely identifiesA REST POST request is sentdetected in one ofthe newly added user in ADto/Users end-point with bodythe monitored OUcontaining user details (cn, sn,preferred Language,givenname, mail,samaccountname, objectguid,name). Upon successful usercreation, a PATCH request forthat particular user is sent toupdate the group membershipand include this user.Add a newIDBridge adds the member toA REST PATCH request ismember to athe groupsent to the particular groupgroupresource with body containingthe id of the user to addDelete an existingIDBridge uniquely identifiesA REST PATCH request ismember from thethe member that is deletedsent to the particular groupgroupfrom the groupresource with body containingthe id of the user for themembership deletionUpdating attributeIDBridge uniquely identifiesA REST PATCH request isvalues of usersthe attributes that are modifiedsent to the particular userwho belong to thefor the userresource with body containingmonitored OUthe attributes that are modified(sn, mail, name, etc.)Delete a userIDBridge identifies the userA REST DELETE request isfrom ADwho is deleted; the deletesent to the particular userrequest is always sent to theresourceserver even if the user was nota member of the monitoredgroupDelete a groupIf the deleted group is in theA REST DELETE request isfrom ADlist of groups monitored bysent to the particular groupIDBridge, then group deletionresource Uniquely identifyingrequest will be sent to IDAASUser between AD and IDCSserverserver

In order to construct the proper REST calls to IDCS1330, IDBridge1310may uniquely identify the appropriate resource using the SCIM ID attribute or the SCIM externalID attribute.

The SCIM ID attribute is a unique identifier for a SCIM resource. In certain embodiments, when an entry is created in IDCS1330, a unique “orclguid” value is created for the entry. The SCIM ID attribute for the entry may be set to the unique orclguid value, or UID. The SCIM externalID attribute is a unique identifier for a SCIM resource that may be used by AD1320. In certain embodiments, the value of the SCIM externalID attribute for an entry may be set to the value of the objectGuid attribute for the entry in AD1320.

In these embodiments, uniquely identifying and mapping user entries in IDCS1330and AD1320may includes several processes. For example, IDBridge1310may send a CreateUser request with a SCIM externalID attribute value to IDCS1330, and, if no matching externalID is found in IDCS1330, then IDCS1330will create a new user. If a uniqueness error is indicated during the creation of the new user, IDBridge1310will query IDCS1330, using a filter for matching the EmailID or Username, to retrieve the UID. The SCIM externalID attribute value is then set to the updated UID. All subsequent PATCH/GET/PUT/DELETE operations are performed using the SICM externalID attribute value to uniquely identify the resource.

Table 2 presents a core set of SCIM attributes to be synced from AD1320to IDCS1330, according to an embodiment of the present invention.

User creation in IDCS1330may fail when the user does not have all the mandatory attributes. However, AD1320may only need Full Name and samAccountName to create a new user. In certain embodiments, if familyName is not present in AD1320, familyName may be extracted from the Full Name, or, alternatively, the entire Full Name may be assigned sent to IDCS1330. If email ID is a null value in AD1320, an error is indicated.

Errors may arise between the interaction of IDBridge1310with AD1320and IDCS1330, including network errors related to REST requests sent to IDCS1330, data errors reported by IDCS1330as REST responses, authentication errors when communicating with IDCS1330, network errors related to communications with AD1320, LDAP errors, IDBridge1310crash due to unhandled exception, etc. IDBridge1310may persist errors in an errors.ser file for later inspection. Alternatively, IDBridge1310may report various errors to IDCS1330by sending notifications to the /Notifications end-point. Generally, IDBridge1310logs all operations for future audit.

Communications between IDBridge1310and IDCS1330may be secured via OAuth using HTTPS protocol to ensure data security and encryption on the communication channel. In many embodiments, the authentication scheme OAuth using client credentials.

In many embodiments, IDBridge1310only consumes a subset of endpoints that are exposed in IDCS1330.

When IDBridge1310determines that a new user has been added to one of the monitored AD groups, IDBridge1310sends the user details to IDCS1330in order to create the new user.

POST Payload with tenant name header:

When IDBridge1310determines that an existing user belonging to one of the monitored AD OUs is updated, IDBridge1310sends the user details to IDCS1330to modify the existing user.

PATCH payload with tenant name header:

When a user is deleted from AD1320, IDBridge1310sends the deleted user information to IDCS1330for deletion of that user account.

DELETE request with tenant name header:

AD groups selected for monitoring by IDBridge1310are created in IDCS1330.

POST request with tenant name header:

Any change in group memberships in AD1320for the monitored groups are synced to IDCS1330.

PATCH Request with tenant name header:

When a monitored group is deleted from AD1320, IDBridge1310sends the deleted group information to IDCS1330for deletion of that group.

DELETE request with tenant name header:

When an AD or network error occurs, IDBridge1310sends details about the error to IDAAS server using the notification end point:

Notification request with tenant name header:

In order to support HA and management of IDBridge1310, the settings related to each AD domain and runtime state are pushed to IDCS1330.

PUT(for update) and GET(for reading) with tenant name as header

For those situations that require synchronization of many users and groups at the same time, bulk mode synchronization may be used. In one embodiment, IDCS1330provides a standard SCIM Bulk interface, and IDBridge1310sends all of the changes to AD1320in bulk mode. In one example, when a bootstrap is executed on day 0, IDBridge1310queries all existing users and groups without any previous state reference, and sends all the data to IDCS1330. Upon successful completion, IDBridge1310stores the cookie for further synchronization. When a bootstrap is then executed on day N, IDBridge1310queries AD1320for changes starting from the previous sync state by using the existing cookie. IDBridge1310then compiles the bulk request payload and sends it to IDCS1330. The cookie may be persisted after completion of the bulk operation. IDBridge1310logs any error messages received from IDCS1310for each record processed in the bulk request. If the error indicates that a particular user or group is already present, IDBridge performs an update operation for such entries in bulk mode.

FIG. 20presents a method2000for providing an IDBridge1310between an on-premises AD1320and a cloud-based IDCS1330, in accordance with an embodiment of the present invention.

A connection to AD1320is established (2010) by IDBridge1310. AD1320is coupled to first network, and includes a plurality of OUs, a plurality of groups and a plurality of users. Each group is a member of an OU, and each user is a member of an OU and a group. In certain embodiments, a user may be a member of more than one group, or no groups at all.

A connection to IDCS1330is established (2012) by IDBridge1310. IDCS1330is coupled to a second network, and includes a SCIM directory that has a plurality of user resource entries and a plurality of group resource entries.

In various embodiments, these connections may be established concurrently (indicated by the dotted line surrounding elements2010and2012inFIG. 20), the connection to AD1320may be established before the connection to IDCS1330, or the connection to AD1320may be established after the connection to IDCS1330.

The OUs of AD1320are displayed (2020) in a GUI, such as GUI1900, and each OU is selectable by a user. For example, the use may select a check box next to the name of the OU, as depicted inFIG. 19A.

A selection of one or more OUs is received (2030), and each member group of the selected OUs in the GUI is displayed (2040). Each group is selectable by the user, and a selection of one or more member groups of the selected OUs is then received (2050).

The users of the selected OUs are monitored (2060) to identify users that have been added, modified or deleted. Similarly, the selected member groups of the selected OUs are monitored (2062) to identify groups that have been added, modified or deleted. In certain embodiments, the users and the selected groups may be monitored concurrently (indicated by the dotted line surrounding elements2060and2062inFIG. 20), the users may be monitored before the selected groups, or the users may be monitored after the selected groups.

The identified users are synchronized (2070) to the SCIM directory. Similarly, the identified groups are synchronized (2072) to the SCIM directory. In certain embodiments, the users and the selected groups may be synchronized concurrently (indicated by the dotted line surrounding elements2070and2072inFIG. 20), the users may be synchronized before the selected groups.

In certain embodiments, the connection to AD1320is read-only, and AD1320may be a single domain, as discussed above. The OUs may displayed in a hierarchical tree in a GUI, such as pane1910of GUI1900depicted inFIG. 19A. Advantageously, the identified users may be synchronized to the SCIM directory without transmitting AD password information over the second network, as discussed above.

In certain embodiments, the identified users and the identified groups are synchronized incrementally and periodically at a pre-determined time interval, such as, for example, Periodic Synchronization discussed above. The identified users and the identified groups may be synchronized using REST post, patch and delete operations to the SCIM directory, as discussed above.

FIG. 21presents present a cloud-based IDCS user interface2100for managing IDBridge1310, in accordance with an embodiment of the present invention.

In certain embodiments, IDBridge1310uses the AD Directory Synchronization (DirSync) Control to find changes to memberships in AD groups. DirSync Control returns changes in objects from one point in time to another based on a cookie returned at the end of each query. Advantageously, IDBridge1310improves the performance of DirSync Control by combining multiple groups in a single request, which reduces the number of requests sent to AD1320.

Alternatively, when many groups are newly selected in a particular sync cycle, each group is queried separately for memberships without DirSync Control. Because all members are required for the newly selected groups, this process is faster than using DirSync control. Additionally, multiple groups may be combined in the same query, so that AD1320is not loaded by too many requests. To generate a DirSync cookie for use in next sync cycle, a temporary cookie is generated and saved. Because a single request is sent with the DirSync cookie, performance improves significantly.