Skip to content

Add a note to the Secure MCP server about GitHub secret #2298

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 7, 2025
Merged

Add a note to the Secure MCP server about GitHub secret #2298

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions _posts/2025-04-28-secure-mcp-sse-server.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -287,6 +287,21 @@ Access `http://localhost:8080/login`, login to GitHub, and copy the returned acc

image::github_access_token.png[GitHub access token,align="center"]

[NOTE]
====
By default, Quarkus GitHub provider submits the client id and secret in the HTTP Authorization header.
However, GitHub may require that both client id and secret are submitted as form parameters instead.

When you get HTTP 401 error after logging in to GitHub and being redirected back to Quarkus MCP server,
try to replace `%prod.quarkus.oidc.login.credentials.secret=${github.client.secret}` property
with the following two properties instead:

[source,properties]
----
%prod.quarkus.oidc.login.credentials.client-secret.method=post
%prod.quarkus.oidc.login.credentials.client-secret.value=${github.client.secret}
----

[[mcp-inspector]]
=== Use MCP Inspector to access the MCP server

Expand Down
Loading