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.

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

[RFC] Security resolution as a requirement #12

Open
PedroTroller opened this issue Jul 18, 2016 · 0 comments

Comments

@PedroTroller
Copy link
Member

commented Jul 18, 2016

As @NiR- suggested few month ago, why not use rad-security as a requirement instead of a simple listener.

Pros: you can define 2 different routes with the same path, the same parameters regex but 2 different accesses.

Cons: actually there is a compatibility problem with the rad-resource-resolver because the rad-security matcher will be executed before the resources resolution. And so, resources will not yet be resolved during the security resolution ...

@PedroTroller PedroTroller added the ToDo label Jul 18, 2016

@PedroTroller PedroTroller referenced a pull request that will close this issue Jul 18, 2016

@PedroTroller PedroTroller self-assigned this Jul 18, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.