From ee4be3cb94bb7ede4c2755becbaa359b91239157 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?No=C3=A9=20Samaille?= Date: Sun, 4 May 2025 14:46:10 +0200 Subject: [PATCH] Fixes wrong hardcoded credentials in README MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixes wrong hardcoded credentials in the example for MCP server with OAuth server configuration, causing the following error: ``` ❯ curl -XPOST "http://localhost:8080/oauth2/token" \ --data grant_type=client_credentials \ --user "oidc-client:secret" {"error":"invalid_client"} ``` Signed-off-by: Noé Samaille --- .../weather/starter-webmvc-oauth2-server/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/model-context-protocol/weather/starter-webmvc-oauth2-server/README.md b/model-context-protocol/weather/starter-webmvc-oauth2-server/README.md index e8eed10..7779beb 100644 --- a/model-context-protocol/weather/starter-webmvc-oauth2-server/README.md +++ b/model-context-protocol/weather/starter-webmvc-oauth2-server/README.md @@ -16,12 +16,12 @@ Obtain a token by calling the `/oauth2/token` endpoint: ```shell curl -XPOST "http://localhost:8080/oauth2/token" \ --data grant_type=client_credentials \ - --user "oidc-client:secret" + --user "mcp-client:secret" # And copy-paste the access token # Or use JQ: curl -XPOST "http://localhost:8080/oauth2/token" \ --data grant_type=client_credentials \ - --user "oidc-client:secret" | jq -r ".access_token" + --user "mcp-client:secret" | jq -r ".access_token" ``` Store that token, and then boot up the MCP inspector: