Skip to content
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

Jump to bottom

OIDC token propagation: add option to select named OIDC client and token exchange per REST client with the @AccessToken annotation #39132

Merged
merged 1 commit into from
Mar 4, 2024
Merged

OIDC token propagation: add option to select named OIDC client and token exchange per REST client with the @AccessToken annotation #39132

merged 1 commit into from
Mar 4, 2024

Conversation

michalvavrik
Copy link
Member

closes: #36994
closes: #36458

@quarkus-bot quarkus-bot bot added area/docstyle issues related for manual docstyle review area/documentation area/oidc labels Mar 2, 2024
@quarkus-bot

This comment has been minimized.

Sign in to view
@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 2, 2024 •
edited
Loading

🙈 The PR is closed and the preview is expired.

@quarkus-bot

This comment has been minimized.

Sign in to view
@michalvavrik michalvavrik force-pushed the feature/access-token-named-client branch from cff54f3 to c8ae838 Compare March 4, 2024 11:25
@quarkus-bot

This comment has been minimized.

Sign in to view
@quarkus-bot

This comment has been minimized.

Sign in to view
@michalvavrik michalvavrik force-pushed the feature/access-token-named-client branch from c8ae838 to 5ba2a00 Compare March 4, 2024 17:34
@quarkus-bot
Copy link

quarkus-bot bot commented Mar 4, 2024 •
edited by github-actions bot
Loading

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 5ba2a00.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

⚠️ There are other workflow runs running, you probably need to wait for their status before merging.

You can consult the Develocity build scans.

@quarkus-bot
Copy link

quarkus-bot bot commented Mar 4, 2024

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 5ba2a00.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

sberyozkin
sberyozkin approved these changes Mar 4, 2024
View reviewed changes
Copy link
Member

@sberyozkin sberyozkin left a comment

Choose a reason for hiding this comment

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

Thanks @michalvavrik

@sberyozkin sberyozkin merged commit 58b0395 into quarkusio:main Mar 4, 2024
23 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.9 - main milestone Mar 4, 2024
@quarkus-bot quarkus-bot bot added kind/bugfix kind/enhancement New feature or request labels Mar 4, 2024
@michalvavrik michalvavrik deleted the feature/access-token-named-client branch March 4, 2024 23:01
@gsmet
Copy link
Member

gsmet commented May 14, 2024

Added for consideration for backports after discussion with @gastaldi see QUARKUS-4318.

@gsmet gsmet removed this from the 3.9.0.CR1 milestone May 15, 2024
@gsmet gsmet added this to the 3.8.5 milestone May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@sberyozkin sberyozkin sberyozkin approved these changes

Assignees
No one assigned
Labels
area/docstyle issues related for manual docstyle review area/documentation area/oidc kind/bugfix kind/enhancement New feature or request
Projects
Quarkus Documentation
Status: Done
Milestone
3.8.5
3 participants
@michalvavrik @gsmet @sberyozkin