Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove chaining requirement in auth middleware #41

Open
Edward-Upton opened this issue Sep 1, 2022 · 0 comments
Open

Remove chaining requirement in auth middleware #41

Edward-Upton opened this issue Sep 1, 2022 · 0 comments
Labels
enhancement New feature or request med-priority
Projects
Fully Customizable Platform

Comments

@Edward-Upton
Copy link
Contributor

Currently, you must make sure you use the isAuth middelware before isExec, isSuper etc.

We should remove this so that we can reduce middleware dependencies.

This can be done by simply checking that we have extracted the values already in each middleware (like the token and payload), and if not, extract at that point.
@Edward-Upton Edward-Upton added enhancement New feature or request med-priority labels Sep 1, 2022
@Edward-Upton Edward-Upton added this to To do in Fully Customizable Platform via automation Sep 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request med-priority
Projects
Fully Customizable Platform
To do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Edward-Upton