OpenID Connect - SSO
OpenID Connect allows your users to sign in using an external authentication provider instead of the Church Online Platform’s built-in login system.
Important: Once OpenID is activated, all users (including existing ones) must use your external provider to sign in.
Note: This setup requires a working knowledge of OpenID Connect specifications. If you’re unfamiliar, we strongly recommend working with a developer or someone experienced with OpenID Connect.
How to Set Up OpenID Connect
- Log in to the Admin.
- Go to Integrations > OpenID Connect.
- Click Set Up.
Configuration Steps
- You’ll see callback URLs to use in your external provider settings.
- Enter the required values:
- Issuer URI
- Client ID
- Client Secret
- Click Test Configuration to verify everything works.
Finalize Setup
- If the test is successful, click Save and Activate.
- If the test fails, troubleshoot the configuration or consult your provider’s documentation.
Troubleshooting
If there’s a problem with your OpenID provider, admin users may be locked out of the platform.
Workaround: Contact support to temporarily disable OpenID Connect. Once the issue with your provider is resolved, you can re-enable it from Admin > Integrations > OpenID Connect.
Integration Support Compatibility Standards
The Church Online Platform is built to the OAuth 2.0 Framework and the OpenID Connect 1.0 (OIDC) identity layer. To ensure a successful integration, your Identity Provider must be compliant with these standards.
Verified Integration Partners
We've tested and verified integrations with Rock RMS and Auth0. We don't provide direct technical support for configuring these third-party platforms, but both are used extensively by Life.Church and offer the most stable experience for our users.
Untested Providers
Other OIDC and OAuth 2.0 compliant services, including Supabase, Planning Center, Okta, and Microsoft Entra ID, haven't been explicitly tested. They should theoretically work, but we can't guarantee full compatibility or provide platform-specific configuration support.
Integration Troubleshooting
If you run into an issue with your provider, try connecting with the free version of Auth0 first. If that connection works but your primary provider's doesn't, contact that provider's support team. Let them know it's working with Auth0 and ask for help identifying any protocol differences on their end.
If you successfully integrate an untested provider, we’d love to hear about it so we can consider expanding our list to include community-verified services!