Unexpected behavior of path matching for configuration-based security policies

[jmartisk]

If I have a permission for a path like
quarkus.http.auth.permission.mypermission.paths=/a/*
Then requests to /a/anything should be matched to it, but they are not.

If I change it to
quarkus.http.auth.permission.mypermission.paths=/a*
Only then requests to /a/anything will start getting authorization checks.

This is contradictory to what is described in the documentation https://quarkus.io/guides/security#matching-on-paths-methods

[jmartisk]

Not sure who's the right person to look into it, maybe @sberyozkin ?

[jmartisk]

I'll look into it myself, think I know what to do