Summary
OAuth Single Sign-On lets learners sign in through an external identity provider instead of a separate KnowledgeCity password. An administrator sets up one or more OAuth providers for the account, and each learner can then sign in by choosing a configured provider, approving access, and returning to KnowledgeCity already authenticated.
Introduction
OAuth Single Sign-On in Integrations connects learner login to an external OAuth identity provider, so a learner can authenticate with an account they already have. An administrator configures which providers are available and supplies each provider's connection details, including the OAuth version and the endpoints the login uses.
This capability is used by learners who sign in to KnowledgeCity and is set up by administrators who decide which providers to enable. It reduces the need for a separate password, centralizes authentication with a provider the organization already trusts, and gives every learner a consistent sign-in experience.
Key Concepts
- OAuth Single Sign-On: a login method where a learner authenticates through an external identity provider rather than entering a KnowledgeCity password directly.
- Provider connection: an OAuth provider that an administrator has configured for the account, including its settings, which determines the providers a learner can choose at sign-in.
- OAuth version: the per-provider setting that states whether a provider uses OAuth 2.0 or OAuth 1.0a, which determines how the login request is handled.
- Authorization URL: the provider's authorization address. The learner's browser is sent here to sign in and approve access.
- Token endpoint: the provider address used to obtain an access token after authorization succeeds.
- Request parameters: standard OAuth values such as the client ID, redirect URI, scope, and state, which are filled in automatically when the login request is built.
Steps to Follow
Learn which providers are available
The providers you can use are the ones your administrator has enabled for your account. Each configured provider carries the settings the login needs, so the account's configuration determines which providers appear at sign-in.
Understand a provider's settings
Each provider connection has an OAuth version, an authorization URL, and a token endpoint. The OAuth version tells the login whether the provider uses OAuth 2.0 or OAuth 1.0a. The authorization URL is where you are redirected to sign in, and the token endpoint is where KnowledgeCity retrieves an access token once you approve access.
Understand how the redirect works
When you begin sign-in, KnowledgeCity builds the provider's authorization request with standard OAuth parameters such as the client ID, redirect URI, requested scope, and a state value. These are filled in automatically, so you are sent to the provider with the correct return address and request details.
Sign in as a learner
Begin login and choose the provider your organization has enabled. You are redirected to that provider's sign-in page, where you authenticate and approve the requested access. The provider returns you to KnowledgeCity, and your session is established.
Conclusion
OAuth Single Sign-On gives learners a straightforward way to authenticate through a provider they already trust. Because an administrator configures each provider connection for the account, learners simply choose an enabled provider, approve access, and return to KnowledgeCity signed in.