Open cmasantos opened 1 day ago
/cc @sberyozkin (security)
To clarify situation TestSecurity#permissions using SecurityIdentityAugmentor only work with proactive auth
- the TestSecurity#permission
works, but it sets string permissions. So the issue I can see is that your augmentor is not applied.
Internally, it may require radical changes as we basically need to drop TestIdentityAssociation
or apply augmentors in there (which feels wrong). I'll have try it. Thanks
Description
Hello,
The
TestSecurity#permissions
method says that "If you need to test custom permissions, you can add them with io. quarkus. security. identity. SecurityIdentityAugmentor.
. But when we use it with a custom annotation like following example, that permission does not get invoked.Example:
with custom permission:
then on the test:
it ends up on a 403 - (Quarkus 3.16.2) -
If we try to user the
SecurityIdentityAugmentor
it will not have any different effect, the identity will be anonymous and no permission will get call.Implementation ideas
No response