This repository has been archived by the owner on Aug 10, 2021. It is now read-only.
forked from dgrijalva/jwt-go
-
Notifications
You must be signed in to change notification settings - Fork 18
aud not handling a string vs. #5
Comments
@Waterdrips, @martinreus-form3 could we fix this on this fork? |
Hey, got an example payload? Thought this was a test for a single string audience here: |
Thanks! We will test it out. |
This fork is now archived. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
https://tools.ietf.org/html/rfc7519#section-4.1.3
RFC above says this should support a string or an array of strings but currently it only supports an array of strings in this package.
The repo you forked from appears to have started this in an unreleased version here:
https://github.com/dgrijalva/jwt-go/blob/v4.0.0-preview1/claim_strings.go
We're running into an issue with Azure tokens not being able to validate because aud returns from it as just a string and not an array of strings. Before going on to fix this ourselves we thought to see if it's something you wanted to fix here rather than have another repo out there doing the same thing.
The text was updated successfully, but these errors were encountered: