Repository navigation
docs(mcp): correct PROD client_id — DEV and PROD have DISTINCT IAS clients - #2709
Merged
Merged
Conversation
…ients Reverses the incorrect unification from #2700. DEV and PROD each have their OWN tutorials-identity service instance with a DISTINCT clientid: - DEV = 0b1e8b56-5f5d-4ebf-a9e9-28aae2964236 - PROD = 5a7cb5fd-a0f0-4678-8f51-f8c471e0ab34 #2700 wrongly claimed a single shared client (0b1e8b56…) for both envs. That is why PROD failed live with "server rejected a token it had just issued": the interactive id_token's aud = the supplied client_id (0b1e8b56…), but PROD's tutorials-srv-mcp validates aud against its OWN instance clientid (5a7cb5fd…) → WrongAudience 401 after a successful browser login. Proven on PROD 2026-10-11: an M2M JWT (aud=5a7cb5fd…) returns 200 on /mcp-auth/api, and the interactive flow with client_id=5a7cb5fd… now connects end-to-end. Also fixed in IAS console (config, not code): added https://developers.sap.com/mcp-oauth/callback to the PROD client (5a7cb5fd…, app 8164289a…) redirect URIs — it had only the loopback callbacks. (The earlier #2667-era addition had gone onto the DEV client by mistake.) Updates: env table (Production→5a7cb5fd…, Dev→0b1e8b56…), both mcp-remote JSON snippets (default to PROD id), and the prose (distinct per-env clients, how to read each env's clientid). Doc-only; no code change.
jung-thomas
marked this pull request as ready for review
October 11, 2026 14:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Reverses the incorrect unification from #2700. DEV and PROD each have their own
tutorials-identityIAS service instance with a distinct clientid:0b1e8b56-5f5d-4ebf-a9e9-28aae29642365a7cb5fd-a0f0-4678-8f51-f8c471e0ab34Why (the PROD failure, finally root-caused)
#2700 wrongly claimed a single shared client (
0b1e8b56…) for both envs. That's why PROD failed live with "server rejected a token it had just issued": the interactive id_token'saud= the supplied client_id (0b1e8b56…), but PROD'stutorials-srv-mcpvalidatesaudagainst its own instance clientid (5a7cb5fd…) → WrongAudience 401 after a successful browser login.Proven on PROD 2026-10-11: an M2M JWT (
aud=5a7cb5fd…) returns 200 on/mcp-auth/api, and the interactive flow withclient_id=5a7cb5fd…now connects end-to-end (Proxy established successfully).Also fixed (IAS console, config not code)
Added
https://developers.sap.com/mcp-oauth/callbackto the PROD client (5a7cb5fd…, IAS app8164289a…) redirect URIs — it had only loopback callbacks. (An earlier addition had landed on the DEV client by mistake.)Scope
Doc-only (
docs/end-users/mcp-quickstart.md) — no code change. The code fix (#2707, id_token-as-Bearer) was correct; the residual PROD failure was purely config: wrong client_id + missing redirect URI, both now resolved.