We are integrating Rovo MCP with enterprise-managed authentication using PingFederate as the IdP that mints an ID-JAG (oauth-id-jag+jwt), then redeeming that assertion at Atlassian for an MCP access token.
Flow
- User authenticates via our gateway / IdP.
- Gateway calls PingFederate token exchange and successfully receives an ID-JAG:
issued_token_type = urn:ietf:params:oauth:token-type:id-jag
- Gateway redeems the ID-JAG at Atlassian’s token endpoint with:
grant_type = urn:ietf:params:oauth:grant-type:jwt-bearerassertion = the ID-JAG JWT- client authentication = HTTP Basic using the Atlassian OAuth client_id / client_secret
Atlassian Response:
HTTP 400
error=invalid_client
What we've already Verified:
- PingFederate mint succeeds.
- ID-JAG
client_id claim is set to our Atlassian OAuth client ID (hard-mapped as text in PingFederate token creation; not copied from the PingOne subject-token client). - The redeem call authenticates as that same Atlassian client ID + its current client secret.
- ID-JAG includes a user subject / email (
TOKEN_SUBJECT mapped to the user email). - We are not using a PAT path; this is the ID-JAG → Atlassian jwt-bearer redeem path for Rovo MCP.
Questions
- What exact conditions cause Atlassian to return
invalid_client on ID-JAG / jwt-bearer redemption for Rovo MCP? - Besides client_id/secret mismatch, can
invalid_client also mean:- the OAuth app is not enabled for Rovo MCP enterprise-managed auth / ID-JAG redeem?
- issuer / JWKS trust not configured for our PingFederate issuer?
- wrong token endpoint / auth method?
- Must the ID-JAG
aud be exactly https://auth.atlassian.com/<cloudId> (with cloudId), or is bare https://auth.atlassian.com accepted? (We currently request/mint with the bare resource and still get invalid_client, not an audience error.) - Are there Atlassian-side admin steps / checks we should confirm for the OAuth client used in the ID-JAG
client_id claim?