Whether it’s a need for cloud SSO, smarter authorization, or a common view of customers for better user experience, the demands for an integrated view of identity keep piling up. But in the current identity infrastructure, user information is distributed in many diverse data stores that may include LDAP directories, SQL databases, and web services. Given this fragmentation, getting a fully integrated view of identity for each user—and providing applications with the view that suits their unique needs—presents a demanding challenge.
With the adoption of federation standards, a marked improvement has been made in terms of funneling access requirements to a common Identity Provider (IdP) layer. Unfortunately, without some form of identity integration layer behind the IdP to address the fragmentation issues, the benefits of a flexible and scalable identity layer amount to empty promises. A Federated Identity Service based on virtualization provides a complete, flexible solution for integrating, storing, and delivering identity data.
In this presentation, Michel Prompt, Founder & CEO at Radiant Logic, will describe why a federated identity service is an essential component of the future identity infrastructure. Attendees will learn how it enables enterprises to achieve global integration and scalability of identity, while keeping local ownership in the data sources.
Key Takeaways:
Authorization is the single area of IAM which is most challenging. This is partially due to the intrusiveness to applications, but also due to the lack of widely adopted standards. While there is logic in moving towards centralized, dynamic and policy-based authorization management (or, in short, ABAC), it is hard to succeed in that journey.
This panel will focus on the way to best integrate applications such as COTS software, cloud services, and home-grown applications, with a solution for managing authorizations centrally. How to do it best? Is it still XACML? Is it OAuth 2.0? Are proprietary approaches best-suited here? And how to build your applications in a way that you can change the Authorization platform without changing application code?
