Skip to content

Conversation

@chillleader
Copy link
Collaborator

@chillleader chillleader commented Jun 24, 2025

Support client_assertion flow when getting a token from an OIDC provider

related: camunda/connectors#4938

keyStore.load(fis, password != null ? password.toCharArray() : null);
}

String alias = keyStore.aliases().nextElement();
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The alias is configurable in the zeebe client. Could be done here as well.


String alias = keyStore.aliases().nextElement();
PrivateKey privateKey =
(PrivateKey) keyStore.getKey(alias, password != null ? password.toCharArray() : null);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The password could be different from the keystore password. Here, the zeebe client also has a second password option.

@jonathanlukas
Copy link
Collaborator

I merge the changes for now and extend in a separate PR

@jonathanlukas jonathanlukas merged commit b532fbe into camunda-community-hub:main Jun 25, 2025
3 checks passed
jonathanlukas pushed a commit that referenced this pull request Jun 25, 2025
jonathanlukas added a commit that referenced this pull request Jun 25, 2025
* feat(auth): support client assertions (#257)

(cherry picked from commit b532fbe)

* add more fine-grained config for client assertion keystore (#258)

* add more fine-grained config for client assertion keystore

* added docs

* added undeclared deps

(cherry picked from commit 750d891)

---------

Co-authored-by: Pavel Kotelevsky <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants