@Auth variable from header value not from header JWT

[verneleem]

Follow this post

GraphQL authorization using standard claims

Hey @dan-j Apologies that we couldn’t get back on this issue in time. No one has come up with such a use case earlier and to prevent collision we made namespace mandatory. For your use case, we can allow an option to read from standard claims and if there is a collision between standard and custom claims then custom claims take preference. I am happy with option 1, i.e. this happening implicitly. So we read the standard claims and then if a namespace is provided and there is a collision betwee…