Skip to main content

Standard OIDC Client

OIDC discovery

Casdoor has fulfilled the OIDC protocol completely. If your application is already running against another OAuth 2.0 (OIDC) identity provider via a standard OIDC client library and you want to migrate to Casdoor, using OIDC discovery will be very easy for you to switch to Casdoor. Casdoor's OIDC discovery URL is:


E.g., the OIDC discovery URL for the demo site is: , with the following content:

"issuer": "",
"authorization_endpoint": "",
"token_endpoint": "",
"userinfo_endpoint": "",
"jwks_uri": "",
"introspection_endpoint": "",
"response_types_supported": [
"code token",
"code id_token",
"token id_token",
"code token id_token",
"response_modes_supported": [
"grant_types_supported": [
"subject_types_supported": [
"id_token_signing_alg_values_supported": [
"scopes_supported": [
"claims_supported": [
"request_parameter_supported": true,
"request_object_signing_alg_values_supported": [

List of OIDC client libraries

Here we list a few OIDC client libraries for some languages like Go and Java:

OIDC client libraryLanguageLink

The above table is far from being complete. For a full list of OIDC client libraries, please see more details at:

    1. Certified OpenID Connect Implementations
    2. Uncertified OpenID Connect Implementations