Skip to content

Commit a764c9d

Browse files
authored
Merge pull request #2318 from sberyozkin/secure_mcp_client_blog_fixes
Secure Quarkus MCP client post fixes
2 parents 73dd503 + bd594bd commit a764c9d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

_posts/2025-05-21-secure-mcp-client.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ For example, let's temporarily update the diagram by removing the `AI Gemini`, r
3535

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

38-
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.
38+
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.
3939

4040
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.
4141

@@ -102,7 +102,7 @@ import jakarta.inject.Inject;
102102
public class UserNameProvider {
103103
104104
@Inject
105-
SecurityIdentity securityIdentity; <1>
105+
SecurityIdentity securityIdentity;
106106
107107
@Tool(name = "user-name-provider", description = "Provides a name of the currently logged-in user") <1>
108108
@PermissionsAllowed("read:name") <2>

0 commit comments

Comments
 (0)