FID for Cloud Provisioning
Bridge Your On-Prem Identity to Azure AD and Amazon Web Services
As the move to the cloud accelerates, there are multiple security and access implications for your identity infrastructure. This shift began with the need to provision identities to SaaS applications, such as Salesforce or Workday. The advent of Office 365 means that hosting and syncing your AD domains and forests with a cloud directory such as Microsoft Azure AD is a new business imperative—and the move to the cloud does not end there. More organizations are beginning to shift some—or all—of their Linux/Unix applications from data centers to cloud infrastructures such as Amazon Web Services (AWS). So 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 in 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.
Building a Global Reference Image of Identity to Seed & Sync 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-premises 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.
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.
Selecting a Target Cloud Directory: Which Environment is Right for You?
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 a big data-driven LDAP v3 directory.
In either case, RadiantOne can unify your underlying identity infrastructure and create the rationalized reference image needed to provision and sync your identity to cloud directories.
- Download our white paper on How to Provision and Sync Your Identity Infrastructure to Cloud Directories.
- Check out our webinar on Simplifying Cloud Access and Provisioning with a Federated Identity Service.