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.

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

Add support for kid header in call to Oauth2 servers #4626

Closed
bscholtes1A opened this issue Nov 14, 2024 · 0 comments · Fixed by #4627
Closed

Add support for kid header in call to Oauth2 servers #4626

bscholtes1A opened this issue Nov 14, 2024 · 0 comments · Fixed by #4627
Assignees
Labels
bug_report Suspected bugs, awaiting triage triage all new issues awaiting classification

Comments

@bscholtes1A
Copy link
Contributor

Bug Report

Describe the Bug

As of today, Oauth2AssertionDecorator does not provide the capability to encode the optional kid header in the access token request to Oauth2 server.

Expected Behavior

We should be able to specify a kid: https://www.rfc-editor.org/rfc/rfc7515#page-11

Observed Behavior

kid header is not supported.

Steps to Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Context Information

Add any other context about the problem here.

  • Used version [e.g. EDC v1.0.0]
  • OS: [e.g. iOS, Windows]
  • ...

Detailed Description

If applicable, add screenshots and logs to help explain your problem.

Possible Implementation

You already know the root cause of the erroneous state and how to fix it? Feel free to share your thoughts.

@bscholtes1A bscholtes1A added bug_report Suspected bugs, awaiting triage triage all new issues awaiting classification labels Nov 14, 2024
@bscholtes1A bscholtes1A self-assigned this Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug_report Suspected bugs, awaiting triage triage all new issues awaiting classification
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant