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
As a consumer of AuthenticationTokenHandler class, I don't expect that my requests should already contain an auth header prior to be sent in the pipeline for my request to be authenticated.
Actual Behavior
If I send a request into the AuthenticationTokenHandler delegating handler and this request doesn't already contain an authorization header, the token will not be fetched nor included in the request.
Steps to Reproduce the Problem
Setup a refit endpoint in an Uno app from UnoApplicationTemplate
Make sure you don't specify any authorization header on an api call (check for default headers too, class and method HeadersAttributes)
Setup an AuthenticationService properly implementing the IAuthenticationTokenProvider, to provide ability to fetch a token.
Make an API call to an authorized service through your pipeline that is using the Mallard AuthenticationTokenHandler.
Notice the call is not authenticated.
Specifications
Version: 0.2.0-dev.21
Platform: all
Subsystem:
The text was updated successfully, but these errors were encountered:
Expected Behavior
As a consumer of AuthenticationTokenHandler class, I don't expect that my requests should already contain an auth header prior to be sent in the pipeline for my request to be authenticated.
Actual Behavior
If I send a request into the AuthenticationTokenHandler delegating handler and this request doesn't already contain an authorization header, the token will not be fetched nor included in the request.
Steps to Reproduce the Problem
Specifications
The text was updated successfully, but these errors were encountered: