**Access to Single Sign-On (SSO) is currently available as an add-on for users with a Business level subscription. If you would like to subscribe, you can request information from one of our account managers here.
Below are a list of the most common reasons why Single Sign-on might not be working properly.
Verifying initial setup
User not recognized in the embed
1. Have you waited at least 24 hours after configuring your remote domain? After configuring your SSO domain, it can take up to 24 hours for it to be available to create users in. If you're seeing 500 errors in threadDetails.json, this is almost certainly the cause
2. Have you entered at least one domain in your API application settings, and are you testing on a domain that's listed there?
3. Have you configured your API Application to connect to your SSO remote domain?
4. Inspect the network, and find the 'threadDetails.json' XHR request. Do you see X-Disqus-Remote-Auth and X-Disqus-Publisher-API-Key in the headers?
5. Does your remote_auth_s3 payload validate when run through the SSO debug tool?
Custom login button not appearing
Note: These don't apply to the Wordpress plugin SSO integration
Have you set up your SSO login button configuration variables?
Is there more than one
disqus_configvariable in the source code of your page? We will only read from one of them.
Setting up multiple remote domains
It is only possible to create one remote domain per user account, and we recommend using a single remote domain per site. If you require an additional remote domain, please create an additional user account for which we can enable SSO.