Support for OIDC SPIFFE Client Authentication#53773
Support for OIDC SPIFFE Client Authentication#53773sberyozkin merged 1 commit intoquarkusio:mainfrom
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
8998167 to
1e43f3b
Compare
|
I forgot to add a test resource, it caused the compilation failure. |
This comment has been minimized.
This comment has been minimized.
|
🙈 The PR is closed and the preview is expired. |
This comment has been minimized.
This comment has been minimized.
|
I'll review sometimes tomorrow. |
michalvavrik
left a comment
There was a problem hiding this comment.
I only run quickly through it + asked Claude to check it. I'll read it properly again when you address my comments. I already did a lot of unrelated reading today, so I need to check tonight. But I presume it will be fine. Thanks
|
Thanks @michalvavrik , I'll have a look |
michalvavrik
left a comment
There was a problem hiding this comment.
I checked again, looks fine. Let's address at least some of my comments and then we can ask George to review.
1e43f3b to
dca417c
Compare
|
@michalvavrik Please have another quick check when you get a chance, I updated the code to log and return null, no actual log statements are checks but null is checked. Did a few field name updates, for ex, |
Status for workflow
|
Status for workflow
|
|
Thanks @michalvavrik @gastaldi, I had to dismiss a few more false positive alerts related to a possible logging of the token, as no actual token is logged |
Fixes #52232
This PR adds support for using SPIFFE JWT tokens for the client authentication between Quarkus OIDC and providers such as Keycloak.
It builds upon the work done by @michalvavrik, with the demo work from @sabre1041 and @maia-iyer at https://github.com/sabre1041/keycloakcon-spiffe/ clarifying a typical pattern for using such tokens for the client authentication.
This PR will fix the linked issue.
As far as X509 client authentication is concerned, it is expected to work out of the box where the OIDC client certificate is located in the file, though I think we'll need to figure out how to handle the dynamism associated with such certificates being regularly refreshed. It will be another enhancement request