...
In order to retrieve the OAuth2 configuration information, a new endpoint was introduced: /api/oauth2/.well-known-configuration
. This endpoint is used by all ModelOp OAuth2 clients integrations to retrieve generic and client specific information such as authorization URI, client id, response type, scope, and redirect.
Sample response:
Code Block | ||
---|---|---|
| ||
{
"name": "modelop",
"issuerUri": "https://authorization.server",
"authorizationUri": "https://authorization.server/as/authorization.oauth2",
"tokenUri": "https://authorization.server/as/token.oauth2",
"userInfoUri": "https://authorization.server/idp/userinfo.openid",
"userNameAttribute": "sub",
"jwkSetUri": "https://iauthorization.server/pf/JWKS",
"introspectionUri": null
} |
For example, to retrieve common OAuth2 configuration, execute Use case example:
Retrieving OAuth2 configurations for Jupyter integration. Execute a GET request to /api/oauth2/.well-known-configuration
. To retrieve Jupyter client specific information, execute a GET request to /api/oauth2/.well-known-configuration/jupyter
where jupyter
is the OAuth2 client id.
Code Block | ||
---|---|---|
| ||
{ "clientId": "jupyter", "scopes": [ "openid", "profile", "email" ], "redirectUri": "http://modelop.center/jupyter.html", "responseType": "token", "oAuth2Provider": { "name": "modelop", "issuerUri": "https://authorization.server", "authorizationUri": "https://authorization.server/as/authorization.oauth2", "tokenUri": "https://authorization.server/as/token.oauth2", "userInfoUri": "https://authorization.server/idp/userinfo.openid", "userNameAttribute": "sub", "jwkSetUri": "https://authorization.server/pf/JWKS", "introspectionUri": null } } |
...