AndyB.76393 (Customer) asked a question.
I am working on implementing Cross App Access for one of the MCP servers we have here at my company. However, I'm running into a strange issue when exchanging the ID token for the ID-JAG token. In the payload that is passed in the token exchange request, it seems the only URL that will work for the 'audience' parameter is 'http://localhost:5001'. This also happens to be the same URL that is used in one of the demos that has been posted (https://github.com/oktadev/okta-cross-app-access-mcp/tree/main). Is this the only URL that can be used for the audience with the pre-built App Integrations for Agent0 (requesting app) and Todo0 (resource app)? If not, is there somewhere in the admin console that I can adjust this and add more URL's that can be used? I'm looking to exchange the JAG token for an access token to one of our SaaS applications, so I would think the 'audience' must be pointing to a token URL for that specific application.
Hello @AndyB.76393 (Customer) Thank you for posting on our Community page!
This question is more appropriate for our dedicated Okta Developer Forum.
My advice would be to reach out via devforum.okta.com to take advantage of their expertise.
While we'll do our best to answer all of your questions here, this medium is more inclined towards Okta core products and features (non-developer work).
Thank you for reaching out to our Community and have a great day!
--
Help others in the community by liking or hitting Select as Best if this response helped you.