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 ...
The text was updated successfully, but these errors were encountered:
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 ...
The text was updated successfully, but these errors were encountered: