Description
The documentation for configuring the Keycloak Connector shows an outdated well-known configuration URL in the example image.
Specifically, in the section "Add the following configuration to add a new Key Manager", the URL is listed as:
http://localhost:8080/auth/realms/master/.well-known/openid-configuration
In modern versions of Keycloak (17.0.0 and later), the default context path /auth has been removed. The correct URL should be:
http://localhost:8080/realms/master/.well-known/openid-configuration
This can cause confusion for users setting up Keycloak 18, 19, 20+, as the connection will fail with a 404 error if they follow the guide verbatim.
Steps to Reproduce
Navigate to the WSO2 API-M 4.6.0 documentation: Configure Keycloak Connector.
Scroll down to the section "Add the following configuration to add a new Key Manager."
Observe the Well-known URL field in the screenshot/description.
Version
API-M 4.7.0 alpha
Environment Details (with versions)
Chrome
Windows 11
Description
The documentation for configuring the Keycloak Connector shows an outdated well-known configuration URL in the example image.
Specifically, in the section "Add the following configuration to add a new Key Manager", the URL is listed as:
http://localhost:8080/auth/realms/master/.well-known/openid-configuration
In modern versions of Keycloak (17.0.0 and later), the default context path /auth has been removed. The correct URL should be:
http://localhost:8080/realms/master/.well-known/openid-configuration
This can cause confusion for users setting up Keycloak 18, 19, 20+, as the connection will fail with a 404 error if they follow the guide verbatim.
Steps to Reproduce
Navigate to the WSO2 API-M 4.6.0 documentation: Configure Keycloak Connector.
Scroll down to the section "Add the following configuration to add a new Key Manager."
Observe the Well-known URL field in the screenshot/description.
Version
API-M 4.7.0 alpha
Environment Details (with versions)
Chrome
Windows 11