For Internal Access
- The client sends a request to access the Dynamics CRM website.
- IIS refuses the connection and sends a HTTP 302 and redirect to ADFS
- The client sends a request for a security token to ADFS
- ADFS returns a HTTP 401.1 error indicating the client must supply a Kerberos ticket
- The client sends an Kerberos Authentication request to Active Directory
- Active Directory validates the client and sends a Kerberos ticket
- The client sends a request for security token to ADFS along with the Kerberos ticket.
Typically for internal access the Client logons to internal domain example mydomain.com and is already validated by Active Directory and hence the Kerberos ticket is already available so steps 4 through to 7 are skipped.
- ADFS provides a security token containing claims for providing access to CRM data
- The client sends the security token containing claims as obtained from ADFS to CRM server
- The CRM server decrypts and validates the security token and presents the user with the information.
For External Access
The flow is similar to Internal Access with the exception of the following:
- The Client will not be logging onto the domain directly and hence there is no Kerberos ticket.
- The ADFS will present the client a logon page to select a attribute store at which point they enter the credentials which are then validated against Active Directory.