Skip to content
This repository has been archived by the owner on Dec 11, 2020. It is now read-only.

Handle unauthorized responses, retries and expired bearer in Authorizer #6

Open
PimCoumans opened this issue Jul 11, 2018 · 0 comments
Labels
enhancement New feature or request

Comments

@PimCoumans
Copy link
Contributor

PimCoumans commented Jul 11, 2018

Currently the Authorizer class only stores a bearer and adds it to a given request. It should be responsible for the actual authentication and could also handle the case of unauthorized responses and when the sent bearer is expired.
The actual authentication part is currently done in the authorize() logic, which should be revised with most responsibility given to the Authorizer class

@PimCoumans PimCoumans changed the title Handle unauthorized responses and expired bearer in Authorizer Handle unauthorized responses, retries and expired bearer in Authorizer Jul 16, 2018
@PimCoumans PimCoumans mentioned this issue Jul 17, 2018
Merged
1 task
@PimCoumans PimCoumans added the enhancement New feature or request label Jul 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant