1. Copy the Conduit values
In Conduit, open Settings → Sign-in, find your Okta provider, and choose Agent access from its menu. Copy Access-token audience for Okta and MCP server URL for your Agent. Both are shown before you save. For example, the audience ishttps://conduit.example.com/mcp and the MCP
server URL is https://conduit.example.com/mcp/WORKSPACE_ID. Use each value
exactly as shown.
2. Configure Okta and collect three values
Create an OIDC Web Application for the Agent. Enable Authorization Code, register your Agent backend’s sign-in redirect URI, and assign your test person. Give each Agent its own application, and use a separate one in each Conduit workspace: a token works in every workspace that approved its application. The Conduit browser sign-in app stays as it is. In Okta, open Security → API → Authorization Servers and use a custom server for Conduit:- Set Audience to the value you copied from Conduit.
- Add the scope
conduit:connectors. - Create an access policy for your Agent app and test person, allowing Authorization Code and the requested scopes. Set the access-token lifetime to 10 minutes. Conduit refuses lifetimes over 15 minutes.
The quickest setup uses the same custom server for Conduit’s browser sign-in
and the Agent. A different server must be on the same Okta domain as the
sign-in provider, including when you use an Okta custom domain. See
Okta’s server setup guide.
3. Turn on Agent access in Conduit
As a workspace owner, reopen the provider’s Agent access:- Turn on Allow Agent access with this provider.
- If the sign-in issuer is the custom server from step 2, keep it. Otherwise, turn on Use a different Okta authorization server and enter that issuer under Access-token issuer.
- Select Save, reopen Agent access, then select Check signing keys.
- Check the claims in Okta:
the ID token of Conduit’s sign-in carries the person’s Okta user ID as
sub, and the Agent’s access token carries the same ID asuid.
4. Create the Agent and choose its access
- In Agents, select Create agent.
- As an owner, select Configure authentication, choose the Sign-in provider, and enter the Agent app’s Client ID as Agent OAuth client ID.
- Add the Agent to a group whose policy grants your test tool, set its Delegation to your test person, and switch the Agent on. See Agent access.
5. Connect your Agent
Configure your Agent backend for Authorization Code with PKCE with the issuer and Agent app credentials from step 2, requestingopenid conduit:connectors for the test person. Give the access token to
the backend’s MCP client:

