Skip to content
Discussion options

You must be logged in to vote

The claims aren't a part of the HTTP request so they can't be forwarded as-is. They're inferred by your ASP.NET Core authentication settings based on who the user is and only exist within your process.

If you're already flowing JWTs around, you could have the backend process the JWT again, which would populate the claims again, or you'd have to forward the information to the backend in some other way yourself.
https://learn.microsoft.com/en-us/aspnet/core/fundamentals/servers/yarp/authn-authz

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by RedEye-Developers
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants