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

[gateway] [jwt-bearer] sub claim is not mandatory #4135

Closed
brasseld opened this issue Jul 27, 2020 · 0 comments
Closed

[gateway] [jwt-bearer] sub claim is not mandatory #4135

brasseld opened this issue Jul 27, 2020 · 0 comments
Assignees
@brasseld
Labels
project: AM type: bug
Milestone
AM - 3.1.1

Comments

@brasseld
Copy link
Member

With AM 3.0, the sub claims was optional (as per the specification https://tools.ietf.org/html/rfc7519#section-4.1.2)

With AM 3.1 it is now required because of the code, but it shouldn't be.
@brasseld brasseld added this to the AM - 3.1.1 milestone Jul 27, 2020
@brasseld brasseld self-assigned this Jul 27, 2020
brasseld added a commit to gravitee-io/gravitee-access-management that referenced this issue Jul 27, 2020
@brasseld
fix(jwt-bearer): sub claims is an optional claim
e845b32 
Closes gravitee-io/issues#4135
@brasseld brasseld mentioned this issue Jul 27, 2020
Merged
aelamrani pushed a commit to gravitee-io/gravitee-access-management that referenced this issue Jul 30, 2020
@brasseld @aelamrani
fix(jwt-bearer): sub claims is an optional claim
18ad203 
Closes gravitee-io/issues#4135
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@brasseld brasseld

Labels
project: AM type: bug
Projects
None yet
Milestone
AM - 3.1.1
Development

No branches or pull requests
2 participants
@brasseld @aelamrani