Cloud Identity Bridge Solution

cloud identity bridge solution

The term cloud identity bridge defines exactly what the name implies – a utility to bridge the gap between a user identity living on-prem and resources living in the cloud. It’s a process of federating on-prem identities through a variety of secure protocols with the purpose of authenticating against cloud resources for access. The result is a far more secure approach to leveraging cloud resources.

Organizations all over the world are moving to the cloud. The benefits are numerous – including scalability and cost-efficiency – but moving to the cloud doesn’t come without it’s own set of challenges. This is especially true for older organizations that are heavily invested in on-prem infrastructure. For most, that means Microsoft Active Directory® (AD). The good news is that a cloud identity bridge solution may be able to help your organization find its place in the cloud.

But first…

Where did Cloud Identity Bridges Come From?

Active Directory has been the preferred option for directory services since the turn of the century. Back then, everything was running Microsoft Windows® for enterprise level computing solutions. Employees had Windows laptops and desktops, they created documents and spreadsheets with Microsoft Office, checked their email with Microsoft Exchange and Outlook, and verified their identities against an Microsoft Active Directory domain controller. Microsoft owned the enterprise space and identity management in the IT world was straight forward.

The IT landscape started to change in the mid-2000’s. New innovations in cloud technology offered a better way to deliver products and services. It enabled vendors to forge their own paths rather than riding on Microsoft’s coattails. Web applications like Salesforce and Dropbox led the way and their success encouraged many others to make the shift to the cloud.

Yet, the cloud wasn’t all sunshine and rainbows. Active Directory was still the choice for identity and access management (IAM) services. While it was great at managing Windows resources on-prem, it was never designed for non-Windows resources in the cloud. Instead, Microsoft’s approach was to enable third party add-ons to connect third party IT resources. Microsoft didn’t want to make it easy (Read more...)

*** This is a Security Bloggers Network syndicated blog from JumpCloud authored by Vince Lujan. Read the original post at:

Vince Lujan

Vince is a documentation and blog writer at JumpCloud, the world’s first cloud-based directory service. Vince recently graduated with a degree in professional and technical writing from the University of New Mexico, and enjoys researching new innovations in cloud architecture and infrastructure.

vince-lujan has 169 posts and counting.See all posts by vince-lujan