Repository navigation
ADFS
Doug Hagan edited this page Sep 17, 2017
·
5 revisions
When communicating with an ADFS store via SAML, the process (SAML v2 redirect flow) is:
- User comes to MeTL unauthenticated
- MeTL sends user to IDP (IDentity Provider) [MeTL configuration for the location of the IDP]
- IDP needs to agree that it will send assertions to MeTL [IDP configuration]
- IDP provides the user with an assertion packet to give to MeTL [IDP signed with private key for which MeTL has public key, via IDP relaying trust config]
- User comes to MeTL with an assertion, which tells MeTL who the user is
- MeTL uses public key to validate that the assertion hasn't been tampered with [MeTL public key for IDP]
- MeTL gets some attributes from the packet (eg username, groups)
There are two ways of configuring a service provider for an IDP.
- The non-Microsoft way which requires knowledge of the IDP (federation metadata), and the public key
- The Microsoft way which provides the knowledge of the IDP via a publicly accessible endpoint along with the public key