As the identity management space heats up, with new approaches, technologies, and marketing terms being thrown around, it is critical for IT organizations to be able to quickly determine the differences between solutions. Unified access management is a new term that is being developed by analysts and vendors alike to convey that the concept of the user identity isn’t just on-prem or in the cloud. Rather, it is an integration of those two concepts and much more. In this blog post, we’ll discuss the question, “What is unified access management?” But first, we should provide some context.
Intro to Identity & Access Management
Historically, the core of the identity management world has been delivered from the on-prem directory services platform known as Microsoft® Active Directory® (AD). Active Directory was introduced in 1999, at a time when IT networks were largely Windows® based and on-prem. So it made sense for IT admins to implement Microsoft solutions such as Windows-based systems for user endpoints, Office® for productivity applications, Exchange® for email, Windows Server® for the file server and domain controller, and Active Directory to manage it all. The end result was that an end user would simply log in to their system, and they would subsequently have access to virtually any Windows IT resource.
This approach worked well, just so long as the network was on-prem and Windows-based, but then web applications like Salesforce® and Google Apps™ appeared. These applications were not based on Windows, nor were they on-prem. Consequently, Active Directory struggled to connect users to this new type of IT resource. That’s when a generation of web application single sign-on providers emerged to solve this new identity and access management (IAM) problem.
Unified Access with Single Sign-On
Web app SSO platforms were some of the first examples of what would become the Identity-as-a-Service (IDaaS) category of identity management. IDaaS solutions generally worked by integrating with the on-prem Active Directory platform. Their purpose was to federate user identities to web applications and other IT resources that couldn’t be managed directly with AD. (Read more...)
*** This is a Security Bloggers Network syndicated blog from JumpCloud authored by Vince Lujan. Read the original post at: https://jumpcloud.com/blog/what-is-unified-access-management/