**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.
Configure your remote domain
Before you start, you will first have to go to your SSO page to configure your remote domain. Once done, you'll be able to test the payload you create after SSO as been setup. Try to refrain from using any non-alphanumeric characters to prevent conflicts from happening. The name assigned to your remote domain is permanent and non-transferable.
Note that 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.
Configure your application
If you haven't setup an API application yet, do so using our guide. In order for SSO to function properly you'll need to verify that you've setup the following items in your API application:
Domains - Enter each domain that will be using SSO.
SSO Domain - Select the remote domain previously setup.
Authentication - Use OAuth permissions as the authentication method
Note: If you are using the deprecated Inherit Permissions authentication you can safely update to OAuth permissions to use SSO. If you're making any API calls using this application, you can attach admin privileges to any API request by adding your access token and the appropriate scope parameters.
Populate your WordPress SSO Settings
These settings can be found on the Plugin Settings tab within the Disqus WP plugin.
Ensure that "Anyone can register" is checked in Wordpress settings
This allows visitors to register on your site.
Verify that a the
remote_auth_s3payload is being generated within your markup.
Copy the remote_auth_s3 payload generated and paste it in our payload debugger.
Additional steps can be found in our SSO Debug Checklist.