WS-Federation (which is short for Web Services Federation) is a protocol that can be used to negotiate the issuance of a token. You can use this protocol for your client applications (such as a Windows Identity Foundation-based app) and for identity providers (such as Active Directory Federation Services or Azure AppFabric Access Control Service).
For Client Applications
By registering your application as a client in Auth0, it will automatically be assigned a WS-Fed endpoint of the form:
You can find all available options for configuring WS-Federation under the advanced settings area for your client.
You will need to configure the Relying Party, which can be done using the following metadata endpoint:
You can also use the samlConfiguration object (available in rules) to configure claims sent via the SAML token, as well as other lower-level WS-Fed and SAML-P settings.
When redirecting your users to your WS-Fed enpoint, you can use the following (optional) parameters:
- wreply: Callback URL
- wctx: Your application's state
- whr: The name of the connection (to skip the login page)
Here's a sample of what your URL with the optional parameters might look like:
If you're using using Auth0 with an identity provider that utilizes the WD-Federation protocol (such as Active Directory Federation Services, Azure AppFabric Access Control Service, and IdentityServer), the easiest way to set up your integration is to create and use the ADFS connection type. When setting up an ADFS-based connection, you can import the required parameters by providing Auth0 with the Federation Metadata endpoint or by importing uploading your Federation Metadata file.
Click Save to proceed. You will then be presented with the instructions you need to finish configuring the integration.
The Federation Metadata file contains information about the the identity provider's certificates. If you provide the Federation Metadata endpoint (typically of the form ending with /FederationMetadata/2007-06/FederationMetadata.xml), Auth0 can check daily for changes in the configuration, such as the addition of a new signing certificate that was added in preparation for a rollover.
Because of this, enabling the Federation Metadata endpoint is preferred to providing a standalone metadata file. If you provide a standalone metadata file, we will notify you via email when the certificates are close to their expiration date.