My use case is that I’m looking to add some social providers to ADFS.
So the flow would be:
Applications → ADFS → Auth0 → Social
All the documentation suggests that Auth0 can only be added as an RP.
The applications would use their existing login screens.
According to this documentation more recent versions of ADFS would support a CP that talks SAML or WS-Federation so you can take a look at the relevant Auth0 documentation available for when Auth0 is acting as a SAML or WS-Federation identity provider for a given client application (which in this case it would be ADFS).
In particular, you may want to look at:
- https://auth0.com/docs/protocols/saml/saml-idp-generic - for SAML based communication.
- Web Services Federation Protocol - for WS-Federation based communication.
All versions of ADFS have always supported RP and CP modes.
The WS-Fed link is for ADFS as an IDP which I don’t want.
The SAML link is the one I need.
All versions of ADFS have always supported RP and CP modes.
The WS-Fed link is for ADFS as an IDP which I don’t want.
The SAML link is the one I need.
Yeah, I used the specific wording because I never used some of the initial version and was not sure if both protocols were always supported for CP’s. Also, the WS-Federation link also contemplates the scenario (in the for apps scenario) where Auth0 is the IdP/CP for a WS-Federation exchange, but if using SAML is okay there’s is indeed more detailed documentation for it than for WS-Federation.