...
If a given external integration needs to fetch its specific configurations, then it can perform a request and append its OAuth 2.0 client id well-known name. The response will contain any existing configurations related to the specified client idname.
| Info |
|---|
Well-known name refers to a simple identifier for an external integration, typically its short form name. This provides a permanent relative URI that can be hardcoded into artifacts so they can configure themselves at runtime. |
Sample request for
...
Jupyter
GET <ModelOp Center URL>/api/oauth2/.well-known-configuration/jupyter
...
| Code Block | ||
|---|---|---|
| ||
{
"clientId": "my_jupyter_client",
"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
}
} |
...