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
Copy file name to clipboardExpand all lines: a2a/slack_researcher/README.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,11 +24,19 @@ The Slack Researcher Agent is designed to perform research tasks across Slack ch
24
24
| 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
26
| AUDIENCE | Expected `aud` value of incoming bearer tokens | No | - |
27
+
| 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 | - |
29
+
| 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
+
| TARGET_SCOPES | Requested scopes of token exchanged token | No | - |
27
32
28
33
> **Note on Authorization configuration**
29
34
> By default, no token validation is performed. To enable token validation, set `JWKS_URL`.
30
35
> If `ISSUER` is additionally set, the `iss` claim will be checked to equal this value.
31
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
40
33
41
## Running in Kagenti
34
42
When deploying in the Kagenti UI - You will need to attach 3 environments to the agent deployment:
0 commit comments