Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

  • (OPTIONAL) When landing on the ADFS, the user will be presented with options to authenticate with either AD or Shibboleth - only one of the below needed. 
    • Cookie Enforcement
      • To automatically select Shibboleth over AD, we insert (or overwrite) a cookie into the incoming HTTP request with a Base64 value of the EntityID for the Shibboleth IdP
        • This is achieved in a load balancer or proxy performing man-in-the-middle for SSL.
        • That is, it decrypts the request, performs the manipulation, re-encrypt for the backend
        • There are many types of load balancer/proxy - this article will not go into any of their configuration - please use google with terms like "ssl offloading" and "set header/cookie" with the name of your load balancer/proxy.
      • Key: "MSISIPSelectionPersistent"
      • Value: "aHR0cHM6Ly9pZHAuZXhhbXBsZS5jb20vaWRwL3NoaWJib2xldGg=" (e.g. echo -n https://idp.example.com/idp/shibboleth | base64 )
      • There has recently been a bug with some mobile apps sending a query string that ADFS gets confused with Shibboleth's answer
    • Per Relying-Party enforcement
      • You can specify which Claim Provider a Relying Party must use (if nothing is set, that is when the user is asked to select from the full list of providers)

...