You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| JWKS_URL | Endpoint to obtain JWKS for token validation. Enables token validation | No | - |
25
25
| ISSUER | Expected `iss` value of incoming bearer tokens | No | - |
26
-
| AUDIENCE | Expected `aud` value of incoming bearer tokens | No | - |
27
26
| TOKEN_URL | Endpoint to perform token exchange. Required for token exchange. | No | - |
28
-
| CLIENT_ID | Client ID to authenticate to auth server with. Required for token exchange. | No | - |
27
+
| CLIENT_ID | Client ID to authenticate to auth server with. Required for token exchange. Expected `aud` value of incoming bearer tokens | No | - |
29
28
| CLIENT_SECRET | Client secret to authenticate to auth server with. Required for token exchange. | No | - |
30
-
| TARGET_AUDIENCE | Audience of token exchanged token | No | - |
31
29
| TARGET_SCOPES | Requested scopes of token exchanged token | No | - |
32
30
33
31
> **Note on Authorization configuration**
34
-
> By default, no token validation is performed. To enable token validation, set `JWKS_URL`.
35
-
> If `ISSUER` is additionally set, the `iss` claim will be checked to equal this value.
36
-
> If `AUDIENCE` is additionally set, the `aud` claim will be checked to equal this value.
37
-
> If all of `TOKEN_URL`, `CLIENT_ID`, and `CLIENT_SECRET` are set in addition, token exchange will be performed using Bearer tokens from incoming requests, to send to the MCP endpoint.
38
-
> In addition to `TOKEN_URL`, `CLIENT_ID`, `CLIENT_SECRET`, which trigger token exchange, `TARGET_AUDIENCE` and `TARGET_SCOPES` can be optionally configured as the values of `audience` and `scope` in the token exchange request, respectively.
39
-
32
+
> By default, no token validation is performed. To enable token validation, set `JWKS_URL`.
33
+
> If `ISSUER` is additionally set, the `iss` claim will be checked to equal this value.
34
+
> If all of `TOKEN_URL`, `CLIENT_ID`, and `CLIENT_SECRET` are set in addition, token exchange will be performed using Bearer tokens from incoming requests, to send to the MCP endpoint.
35
+
> In addition to `TOKEN_URL`, `CLIENT_ID`, `CLIENT_SECRET`, which trigger token exchange, `TARGET_SCOPES` can be optionally configured to be the `scope` in the token exchange request.
40
36
41
37
## Running in Kagenti
42
38
When deploying in the Kagenti UI - You will need to attach 3 environments to the agent deployment:
@@ -47,4 +43,4 @@ When deploying in the Kagenti UI - You will need to attach 3 environments to the
47
43
2.`mcp-slack` - This provides the value of the slack MCP server (`MCP_URL`)
48
44
3.`slack-researcher` - This provides the remainder of the necessary configuration settings
49
45
50
-
NOTE if you are connecting to a tool that is OAuth-secured, you MUST set the `JWKS_URL` variable or the token will not be passed to the tool.
46
+
NOTE if you are connecting to a tool that is OAuth-secured, you MUST set the `JWKS_URL` variable or the token will not be passed to the tool.
0 commit comments