You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a service that will sit in AWS, behind an ALB. Amazon has a feature where you can to auth at the ALB, and your application will be provided with JWTs in specific headers. Unfortunately, the x-amzn-oidc-data header comes with incorrect base64 encoding, which means that spec-conformant libraries will not verify it's tokens.
Would you be willing to accept a patch that added an AWS-compat mode? I'm happy to write it, but I don't want to just open a PR if it's not a use case you're interested in supporting.
The text was updated successfully, but these errors were encountered:
Is that still the case recently? I found auth0/node-jws#84 (comment)
IMO it doesn't really makes sense to add support for a bug, in that link above they said they were changing it but it does suck :/
It's still an issue. They've at least acknowledged that it's a bug, but it's not looking like it will be fixed any time soon. Perhaps I'll just write a blog post and put up a demo repo showing how to work around the problem, while it persists.
I'm working on a service that will sit in AWS, behind an ALB. Amazon has a feature where you can to auth at the ALB, and your application will be provided with JWTs in specific headers. Unfortunately, the
x-amzn-oidc-data
header comes with incorrect base64 encoding, which means that spec-conformant libraries will not verify it's tokens.Would you be willing to accept a patch that added an AWS-compat mode? I'm happy to write it, but I don't want to just open a PR if it's not a use case you're interested in supporting.
The text was updated successfully, but these errors were encountered: