Federation & Cloud SSO

From Ad-Hoc Access to Federation: A Better Approach to Reaching the Cloud

As established enterprises continue to grapple with increasing identity complexity, they’re also taking advantage of SAML, OAuth, and OpenID Connect to federate access to cloud-based applications. But deploying federation requires more than just federating the access request to an identity provider (IdP). In fact, identity integration is often required to feed your IdP with cohesive views of identity that match the needs of consuming applications—and that’s difficult in diverse, distributed identity environments that have grown in an ad-hoc fashion over many years.


Federation standards can’t go the last mile into your identity infrastructure, making it difficult to offer your IdP a rationalized view of identity from across heterogeneous silos

The IdP is not designed to find users across data silos or sort out protocol differences and user overlap. It requires a unified, normalized view of identity against which it can authenticate users, and issue the appropriate tokens to connect those users to web or cloud-based applications outside the security perimeter. What you need is an integration layer that can also federate all your identity sources—just as SAML and the other federation protocols federate access itself.

Federated Identity Service

A federated identity layer is the counterpart to the federated access layer,
acting as a hub for all internal authentication

Instead of imposing one unique centralized system on top of all this complexity, a federated integration of all your identity sources offers a rationalized view of the entire system, with the flexibility needed to respond quickly to new demands. See how RadiantOne Federated Identity Service is your on-ramp to the cloud.