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

Audience Checking shouldn't be forced #144

Open
4 tasks done
jag-eagle-technology opened this issue May 2, 2024 · 0 comments
Open
4 tasks done

Audience Checking shouldn't be forced #144

jag-eagle-technology opened this issue May 2, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@jag-eagle-technology
Copy link

Checklist

  • I have looked into the Readme and Examples, and have not found a suitable solution or answer.
  • I have searched the issues and have not found a suitable solution or answer.
  • I have searched the Auth0 Community forums and have not found a suitable solution or answer.
  • I agree to the terms within the Auth0 Code of Conduct.

Description

According to https://datatracker.ietf.org/doc/html/rfc7519#section-4.1.3 the audience claim is OPTIONAL. I'm trying to verify a token without an audience by not providing the audience parameter to this library, but this doesn't appear to be supported.

Reproduction

  1. Leave audience undefined
  2. Assertion in code checks for defined audience => error

Additional context

No response

express-oauth2-jwt-bearer version

1.6.0

Node.js version

18.18.2

@jag-eagle-technology jag-eagle-technology added the bug Something isn't working label May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant