FID for Federation/Cloud SSO

The Missing Requirement for Secure Access to the Cloud

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

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

We offer a complete solution for federation and cloud SSO. Federate access with our IdP, RadiantOne CFS, and federate identity with our federated identity service, RadiantOne FID. Together, the two products offer complete identity integration that allows you to take full advantage of the cloud. RadiantOne FID also works with other federation solutions such as AFDS, PingFederate, and Okta.

Resources: