Flowing Credentials -> Even after a request has been authorized in the proxy, the destination server may still need to know who the user is (authentication) and what they're allowed to do (authorization) #2784
Unanswered
pastrasigns
asked this question in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Yarp devs,
Is there any solid example of Flowing Credentials out there? I have a Yarp Web API which does Identity SPA login, but I would like my other APIs in the back to also pass down the bearer token in the request (which it currently does) and re authenticate the user again with the same Identity. How to do this??
https://learn.microsoft.com/en-us/aspnet/core/fundamentals/servers/yarp/authn-authz?view=aspnetcore-9.0
"Flowing Credentials
Even after a request has been authorized in the proxy, the destination server may still need to know who the user is (authentication) and what they're allowed to do (authorization). How you flow that information will depend on the type of authentication being used."
Beta Was this translation helpful? Give feedback.
All reactions