-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Support complex wildcard path matching for authorization of web endpoints #14047
Comments
Is there any hint as to how the requirement can be fulfilled? |
/cc @sberyozkin |
I am having the same issue in which I need to use the wildcard both at the beginning and the end of the path. Sometimes it works sometimes not. I cannot make public path stable enough to be used. |
Our resource has something like: @Path("{tenant}/data/resources/tenants")
@Consumes(MediaType.APPLICATION_JSON)
@Produces(MediaType.APPLICATION_JSON)
public class TenantResource { And the application.properties
|
Hey @sonnb wildcards are only supported at the end. We should implement this issue though, I am going to have a look. |
Description
According to the documentation path matching supports wildcards at the end of the path:
There is a clear limitation regarding the usage of wildcards which doesn't allow us to compose complex authorization expressions.
This use case has come across in many occasions, in which I have an API which requires an authorization config like:
/api/clients/{clientid}/accounts
-> needs to be private/api/clients/{clientid}/public-profile
-> needs to be publicThis could be configured like this:
However this isn't supported since wildcards are only allowed at the end of the path.
Could you consider supporting it?
The text was updated successfully, but these errors were encountered: