C
Cyan Tuna
According to the existing Harness Hosted MCP implementation there is a single URL for all of the instances: https://mcp.harness.io/mcp
When I'm trying to authorise I'm navigated to the following URL first with "Send OTP to email button":
https://id.harness.io/idp/realms/HarnessIDP/protocol/openid-connect/auth?client_id=mcp-client&redirect_uri=http%3A%2F%2Flocalhost%3A55264%2Fcallback&response_type=code&state=O2vbee9sfRrYCuf1ynWqR0B6kbsCkHMjeVB12DDAeMY&code_challenge=V3BvPDu71kQnFB5AxOd7OCPwnbpZvnHX9jPIoZLaYSc&code_challenge_method=S256
Once I complete the OTP process (or Auth via gmail) I'm navigated to instance selection page and then our Okta Auth is started for the selected instance. It is inconvenient UX flow. Is there a way to have separate /mcp endpoint on our app and app3 instance directly, so the backend know the instance from the very beginning and the user should be able to login via regular "Single sign-on" button we have to login to the UI?
Created by Alan Gudiel
·