Sign-in window not popup for VS Code client

[hejingkan2005]

The sample code runs perfectly with MCP inspector, however, it seems no sign-in popup when MCP server is configured in VS code client:

Anyway to make VS code client working?

[prjhawar]

we have opened a bug for this to vscode extensions team, once that is fixed, we are going to work on fixing this sample to make it work for VS Code

[apc-k-ida]

i meet same phenomena. i hope this bug is fixed and we can use this remote mcp functions via APIM from vscode.
Thank you in advance.

[ajayrfhp]

I am hitting on the browser authentication from VSCode. It was working and suddenly stopped working. Inspector is able to trigger auth flow and it works.

Client Not Found
The client registration for the specified client was not found.

Client ID:
9937d8a0-2266-48c6-b055-815f9b068fe4

Redirect URI:
http://127.0.0.1:33418/

Please ensure that you are using a properly registered client application.

You can close this window safely.

[okaneconnor]

Pranami Jhawar (@prjhawar) has the fix for this been released yet? I to am still having the same issue with VSCode for this. Or is there anything out there atm for this? thanks

[prjhawar]

I think this is fixed. You can try clearing out your connections from VSCode insiders and create connection again.

[okaneconnor]

Pranami Jhawar (@prjhawar) I have this error persisting, how should the AUTH side of things typically flow in APIM when connecting to the GH Co-pilot?

[dakar93]

Pranami Jhawar (@prjhawar) / Connor O'Kane (@okaneconnor) isnt the issue related to the Dynamic Client Registration feature, provided by the APIM? VS Code is going to call the /register endpoint where it gets assigned an APIM generated Client ID. The policy of "register.policy.xml" is storing the data in the local cache for around 3600 seconds. After that, the reference to the (simulated) Client ID is going to be dropped off. If the token has expired, VS Code is calling the /authorize andpioint again without any issues (if the cookie is still set). If the cookie is not set anymore, the consent page will be called and this results in the error:

But lets imagine the cookie is still set. The /authorize endpoint will not validate if the Client ID still exists (in the APIM cache). As soon as VS Code hits the /token endpoint there will be a cache lookup for:

<cache-lookup-value key="@($"ClientInfo-{context.Variables.GetValueOrDefault<string>("client_id")}")" variable-name="clientInfoJson" />

But this lookup will fail and the client doesnt get any token. As VS Code will not retry a new Client Registration, the connection setup is burned. At this point the "Dynamic Authentication Provider"-Settings within VS Code must be deleted for that Client ID. After that, the connection is working again.

Can you confirm that the issue of Connor O'Kane (@okaneconnor) is related to that? At least this is what I got as result from investigation into this topic.

[apc-n-orita]

Pranami Jhawar (@prjhawar) Chaoyi Yuan (@blackchoey)

After reviewing the merged PR, I noticed that client information is now being stored in Cosmos DB, which effectively ensures indefinite persistence.
Given this update, would it be accurate to say that the following improvements have been achieved?

• The previously encountered "client not found" issue has been resolved
• Dynamic client registration now occurs only once, significantly reducing the burden on users

[prjhawar]

apc-n-orita that seems correct, please give it a try. However, I have not tested that myself and currently not actively working on this.