
io.quarkus.vertx.http.runtime.PolicyMappingConfig.jdp Maven / Gradle / Ivy
#
#Wed Jun 21 11:12:51 CEST 2023
io.quarkus.vertx.http.runtime.PolicyMappingConfig.policy=The HTTP policy that this permission set is linked to.\n\nThere are 3 built in policies\: permit, deny and authenticated. Role based\npolicies can be defined, and extensions can add their own policies.
io.quarkus.vertx.http.runtime.PolicyMappingConfig.methods=The methods that this permission set applies to. If this is not set then they apply to all methods.\n\nNote that if a request matches any path from any permission set, but does not match the constraint\ndue to the method not being listed then the request will be denied.\n\nMethod specific permissions take precedence over matches that do not have any methods set.\n\nThis means that for example if Quarkus is configured to allow GET and POST requests to /admin to\nand no other permissions are configured PUT requests to /admin will be denied.
io.quarkus.vertx.http.runtime.PolicyMappingConfig.paths=The paths that this permission check applies to. If the path ends in /* then this is treated\nas a path prefix, otherwise it is treated as an exact match.\n\nMatches are done on a length basis, so the most specific path match takes precedence.\n\nIf multiple permission sets match the same path then explicit methods matches take precedence\nover matches without methods set, otherwise the most restrictive permissions are applied.
io.quarkus.vertx.http.runtime.PolicyMappingConfig.enabled=Determines whether the entire permission set is enabled, or not.\n\nBy default, if the permission set is defined, it is enabled.
io.quarkus.vertx.http.runtime.PolicyMappingConfig.authMechanism=Path specific authentication mechanism which must be used to authenticate a user.\nIt needs to match {@link HttpCredentialTransport} authentication scheme such as 'basic', 'bearer', 'form', etc.
© 2015 - 2025 Weber Informatics LLC | Privacy Policy