Provision to Cloud Directories

Bridge On-Prem Identity to Azure AD & Amazon Web Services

As organizations begin to shift some—or all—of their Linux/Unix applications from data centers to cloud infrastructures such as Amazon Web Services (AWS), the need for hosting and syncing identity into some form of cloud directory for authentication and authorization is becoming a high priority. This presents a real challenge, since identities and profiles are distributed across a diverse array of sources, including Active Directory domains and forests, LDAP directories, SQL databases, and within specialized APIs.

Today’s enterprises have stretched the use of AD beyond the traditional LAN-based deployments for which it was designed. This growth of domains and forests has left many companies with complex thickets of identity that are difficult to maintain or evolve. They need a consolidated view of their domains—one that can act as a reference for syncing and provisioning to cloud directories.

To conquer this complexity, you need to create a normalized view of identity that’s capable of identifying and authorizing each user, whether that identity is stored on-prem or in the cloud. Acting as a federated identity hub, RadiantOne FID uses advanced virtualization and synchronization capabilities to integrate identities, creating a global reference image of your identity, so you can secure, populate, and provision hybrid environments where identity is managed on-premises as well as deployed in the cloud.

Azure AD

RadiantOne creates an integrated, rationalized identity source, which can then be used to facilitate cloud access and as a global reference to provision Azure AD and cloud applications using sync tools such as AD Connect.

This global identity image is used to populate Azure AD or an LDAP directory on AWS with the appropriate identity information—and stay in sync across all sources, whether they’re on-premises or in the cloud. Such a reference image drives security, federation, provisioning, and even SSO. Some companies are targeting a move to Azure AD to better secure Office 365, while others require a more neutral environment such as Amazon Web Services, where they can provision and sync all identities—including AD identities and profiles—within HDAP, our big data-driven LDAP v3 directory. In either case, the RadiantOne platform can unify your underlying identity infrastructure and create the rationalized reference image needed to provision and sync your identity to cloud directories.

Dig Deeper: