Skip to content

Secure Quarkus MCP client post fixes #2318

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 21, 2025
Merged

Secure Quarkus MCP client post fixes #2318

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
4 changes: 2 additions & 2 deletions _posts/2025-05-21-secure-mcp-client.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ For example, let's temporarily update the diagram by removing the `AI Gemini`, r

image::typical_oauth2_authorization.png[Typical OAuth2 Authorization,align="center"]

You will very likely find similarities between this diagram and what you do in your projects. It is the OAuth2 authorization code flow is action: the user logs in to the application and authorizes it to access another service offering a poem creation on the user's behalf.
You will very likely find similarities between this diagram and what you do in your projects. It is the OAuth2 authorization code flow in action: the user logs in to the application and authorizes it to access another service offering a poem creation on the user's behalf.

The demo shows that Quarkus MCP Client can work effectively in such architectures by being able to use access tokens acquired during the user login, without you having to write any custom code.

Expand Down Expand Up @@ -102,7 +102,7 @@ import jakarta.inject.Inject;
public class UserNameProvider {

@Inject
SecurityIdentity securityIdentity; <1>
SecurityIdentity securityIdentity;

@Tool(name = "user-name-provider", description = "Provides a name of the currently logged-in user") <1>
@PermissionsAllowed("read:name") <2>
Expand Down
Loading