[
https://issues.apache.org/jira/browse/CAMEL-21760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17928403#comment-17928403
]
Thomas Diesler commented on CAMEL-21760:
----------------------------------------
The camel-oauth module comes with a set of Processors that can be added the
route on the client and resource owner side
Supported OIDC, OAuth functionality is ...
* OIDC Authentication using Authorization Code Flow (OAuthCodeFlowProcessor,
OAuthCodeFlowCallbackProcessor)
* OAuth Client Credentials Grant (OAuthClientCredentialsProcessor,
OAuthBearerTokenProcessor)
* Identity Provider (Keycloak only) logout (OAuthLogoutProcessor)
Keycloak can be deployed to a local k8s cluster with a helm chart that comes
with camel-oauth
There are two test cases that show the above (KeycloakOAuthWebAppTest,
KeycloakOAuthRestTest)
The respective jbang projects live
[here|https://github.com/tdiesler/camel-cloud-examples/tree/main/camel-main]
When this has found it's proper place and acceptance, I can work on proper docs.
> OpenID Connect & OAuth for Camel Kafka, Web, Rest and Messaging
> ---------------------------------------------------------------
>
> Key: CAMEL-21760
> URL: https://issues.apache.org/jira/browse/CAMEL-21760
> Project: Camel
> Issue Type: New Feature
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Priority: Major
> Fix For: 4.x
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
