Enabling SSO (Single Sign-On) is an integration that's available with the Growth Plan and Mighty Pro.

The benefit of SSO is a unified member login experience between your Mighty Network and your external website or service. With the SSO integration in place, you control and manage account settings for members externally.
​

For this reason, it’s also a feature that requires you to have an established external service and an experienced technical team to ensure everything works smoothly.

SSO operates simply as a way to replace Mighty's built-in login and account management system with your external system. With SSO enabled, you can set up any of the available privacy or access settings for your Network and you can offer both full and limited memberships.

​Ready to proceed? Please share this SSO implementation guide with your technical team.

Is there a way for my technical team to test the integration before enabling it on my main Mighty Network?

Yes! In fact, we recommend it. Full details are available in our SSO implementation guide.
​
​​What protocols do you support to set up the SSO?

We only support OAuth 2.0. OAuth 2.0 is the industry-standard protocol for authorization used by Facebook Connect and other authentication services.
​
​​What happens if I enable SSO, and then decide later to disable it?

​​Disabling SSO will require all existing members to use Mighty's login flows and account management system going forward. As long as members log in using the same email address they were using with your external system when the SSO integration was in place, they will be able to set a new password with Mighty and seamlessly continue accessing their account and activity in Mighty.
​
​​What happens to SSO if I downgrade my Growth Plan or Mighty Pro?

​​Mighty Networks that downgrade will behave the same as Networks that disable SSO (as outlined above).

​​What happens if I get locked out of my Network?

After you finish setting up the SSO integration, you will receive a Host backdoor URL. You will be able to access your Network with that link if your SSO setup is broken or not working properly.

What if my members report frequently needing to sign in?

The likely cause is a missing refresh_token, or a refresh_token that expires too soon. Some SSO providers may also require an ‘offline_access’ scope (or similar) to allow us to keep your members logged in.

As a best practice, we recommend extending your account session times (also known as the refresh token) to 30 days. This will ensure that when a member participates, they aren’t continually prompted for their account name and password.

For more FAQs and detailed information about how to set up the SSO integration, please refer to our SSO implementation guide.