This documentation is for WSO2 Identity Server 5.7.0 . View documentation for the latest release.

All docs This doc
Skip to end of metadata
Go to start of metadata

WSO2 Identity Server supports OpenID Connect Discovery to discover an end user's OpenID provider, and also to obtain information required to interact with the OpenID provider, including its OAuth 2.0 endpoint locations. For more information, see IssuerDiscovery

The OpenID Connect discovery endpoint is as follows:


The following sections provide information and instructions on the following:

OpenID Provider Issuer discovery

OpenID Provider Issuer discovery refers to the process of determining the location of the OpenID Provider. 


In WSO2 Identity Server, the default OpenID Provider Issuer location path is set to oidcdiscovery/.well-known/openid-configuration

To move the OpenID provider issuer location path to the root <issuer>/.well-known/openid-configuration, edit the <IS_HOME>/repository/conf/identity/identity.xml file, and change the value of <OIDCDiscoveryEPUrl> to the issuer URL as shown below.

Configuring the OpenID Provider Issuer location 

In WSO2 Identity Server, the resident IdP Entity ID for OpenID Connect can be configured as the OpenID Provider Issuer location. Follow the instructions given below to configure the OpenID Provider Issuer location. 

  1. Open the identity.xml file found in the <IS_HOME>/repository/conf/identity/ folder and set the following property to true.


    In future releases, the Entity ID will be used as the OpenID Provider Issuer location by default and will not need to be enabled manually using the property mentioned above. Therefore, the <UseEntityIdAsIssuerInOidcDiscovery> property will be deprecated in the next release.

  2. Log in to the management console. 

  3. Click Resident under Identity Providers on the Main tab. 
  4. Expand the Inbound Authentication Configuration section and then expand OAuth2/OpenID Connect Configuration. 
  5. Enter a valid OpenID Provider issuer location as the Identity Provider Entity Id value. 

    A valid OpenID Provider Issuer location in WSO2 Identity Server has the following format.

    OpenID Provider Issuer URL format
    • <Host>: The host number of WSO2 Identity Server (e.g., https://localhost:9443)

    • {issuer}: The issuer path component. This value can be either ‘token’ or ‘oidcdiscovery’.

    Sample OpenID Provider Issuer location
Obtaining the OpenID Provider Issuer location

Once the issuer location has been configured as instructed in the previous section, you can send a request to the endpoint to retrieve the configured OpenID Provider Issuer location.

The following information is required to make a request.

ParameterDescriptionSample Value
ResourceIdentifier for the target end user that is the subject of the discovery request.acct:[email protected] (for super tenant)
acct:[email protected]@localhost (for tenant)
HostServerWhere the WebFinger service is hosted.localhost
relURI identifying the type of service whose location is being requested.

By default, all endpoints in the WSO2 Identity Server are secured with basic authentication. You will need authentication details to call an endpoint. By default, you can use admin credentials, or an access token for the request.

Sample requests and responses are given below:

Request (for super tenant)
Sample Request
curl -v -k --user admin:admin https://localhost:9443/.well-known/webfinger?resource='acct:[email protected]&rel='
Response (for super tenant)
   "subject": "acct:[email protected]",
   "links": [
         "rel": "",
         "href": "https://localhost:9443/oauth2/token"
Request (for tenant:
Sample Request
curl -v -k --user admin:admin https://localhost:9443/.well-known/webfinger?resource='acct:admin%[email protected]&rel='
Response (for tenant:
   "subject": "acct:[email protected]@localhost",
   "links": [
         "rel": "",
         "href": "https://localhost:9443/t/"

Obtaining the OpenID Provider configuration information

Follow the instructions below to obtain configuration details of the OpenID Proivder.

  1. Once you receive the response as shown in the sample response of the previous section, append "/.well-known/openid-configuration" to the href value that you received.  

  2. Send a request to the endpoint as shown below. 

    Sample Request
    curl -v -k --user admin:admin https://localhost:9443/oauth2/oidcdiscovery/.well-known/openid-configuration
    Sample Response
        "scopes_supported": [
        "check_session_iframe": "https://localhost:9443/oidc/checksession",
        "issuer": "https://localhost:9443/oauth2/token",
        "authorization_endpoint": "https://localhost:9443/oauth2/authorize",
        "claims_supported": [
        "token_endpoint": "https://localhost:9443/oauth2/token",
        "response_types_supported": [
            "id_token token",
        "end_session_endpoint": "https://localhost:9443/oidc/logout",
        "userinfo_endpoint": "https://localhost:9443/oauth2/userinfo",
        "jwks_uri": "https://localhost:9443/oauth2/jwks",
        "subject_types_supported": [
        "id_token_signing_alg_values_supported": [
        "registration_endpoint": "https://localhost:9443/identity/connect/register"
  • No labels