Which technology is a prerequisite for populating the cloud-based directory in a federated identity solution?

5 thoughts on “Which technology is a prerequisite for populating the cloud-based directory in a federated identity solution?”

1. might be right answer C STS tokens etc and slightly wrong misquoted question

   Reply

2. Question is populating cloud based directory, which need synchronisation to take place first.

   Not how Federated identity solution works.

   1

   Reply

3. Implement an authentication mechanism that can use federated identity. Separate user authentication from the application code, and delegate authentication to a trusted identity provider. This can simplify development and allow users to authenticate using a wider range of identity providers (IdP) while minimizing the administrative overhead. It also allows you to clearly decouple authentication from authorization.

   The trusted identity providers include corporate directories, on-premises federation services, other security token services (STS) provided by business partners, or social identity providers that can authenticate users who have, for example, a Microsoft, Google, Yahoo!, or Facebook account.

   The figure illustrates the Federated Identity pattern when a client application needs to access a service that requires authentication. The authentication is performed by an IdP that works in concert with an STS. The IdP issues security tokens that provide information about the authenticated user. This information, referred to as claims, includes the user’s identity, and might also include other information such as role membership and more granular access rights.
   https://docs.microsoft.com/en-us/azure/architecture/patterns/federated-identity

   1

   Reply

4. Federated

   Reply

5. https://docs.microsoft.com/en-us/azure/architecture/patterns/federated-identity

   Reply