Class WebSecurity
- All Implemented Interfaces:
Service
Methods that start with "from" are to register WebSecurity with WebServer
- to create SecurityContext
for requests:
Example:
// Web server routing builder - this is our integration pointRouting
routing = Routing.builder() // register the WebSecurity to create context (shared by all routes) .register(WebSecurity
.from(security)
)
Other methods are to create security enforcement points (gates) for routes (e.g. you are expected to use them for a get, post
etc. routes on specific path).
These methods are starting points that provide an instance of SecurityHandler
that has finer grained methods to
control the gate behavior.
Note that if any gate is configured, auditing will be enabled by default except for GET and HEAD methods - if you want
to audit any method, invoke audit()
to create a gate that will always audit the route.
If you want to create a gate and not audit it, use SecurityHandler.skipAudit()
on the returned instance.
secure()
- authentication and authorizationrolesAllowed(String...)
- role based access control (implies authentication and authorization)authenticate()
- authentication onlyauthorize()
- authorization onlyallowAnonymous()
- authentication optionalaudit()
- audit all requests (including GET and HEAD)authenticator(String)
- use explicit authenticator (named - as configured in config or through builder)authorizer(String)
- use explicit authorizer (named - as configured in config or through builder)enforce()
- use defaults (e.g. no authentication, authorization, audit calls except for GET and HEAD); this also give access to more fine-grained methods ofSecurityHandler
Example:
// continue from example above...
// create a gate for method GET: authenticate all paths under /user and require role "user" for authorization
.get("/user[/{*}]", WebSecurity.rolesAllowed("user")
)
-
Field Summary
Modifier and TypeFieldDescriptionstatic final String
Security can accept additional headers to be added to security request. -
Method Summary
Modifier and TypeMethodDescriptionstatic SecurityHandler
If called, authentication failure will not abort request and will continue as anonymous (defaults to false).static SecurityHandler
audit()
Whether to audit this request - defaults to false for GET and HEAD methods, true otherwise.static SecurityHandler
If called, request will go through authentication process - defaults to false (even if authorize is true).static SecurityHandler
authenticator
(String explicitAuthenticator) Use a named authenticator (as supported by security - if not defined, default authenticator is used).static SecurityHandler
Enable authorization for this route.static SecurityHandler
authorizer
(String explicitAuthorizer) Use a named authorizer (as supported by security - if not defined, default authorizer is used, if none defined, all is permitted).static WebSecurity
Create a consumer of routing config to beregistered
with web server routing to process security requests.static WebSecurity
Create a consumer of routing config to beregistered
with web server routing to process security requests.static WebSecurity
Create a consumer of routing config to beregistered
with web server routing to process security requests.static SecurityHandler
enforce()
Return a default instance to create a default enforcement point (or modify the result further).static SecurityHandler
rolesAllowed
(String... roles) An array of allowed roles for this path - must have a security provider supporting roles.static SecurityHandler
secure()
Secure access using authentication and authorization.securityDefaults
(SecurityHandler defaultHandler) Create a new web security instance using the default handler as base defaults for all handlers used.void
update
(Routing.Rules routing) UpdatesRouting.Rules
withhandlers
representing this service.
-
Field Details
-
CONTEXT_ADD_HEADERS
Security can accept additional headers to be added to security request. This will be used to obtain multivalue string map (a map of string to list of strings) from context (appropriate to the integration).- See Also:
-
-
Method Details
-
create
Create a consumer of routing config to beregistered
with web server routing to process security requests. This method is to be used together with other routing methods to protect web resources programmatically. Example:.get("/user[/{*}]", WebSecurity.authenticate() .rolesAllowed("user"))
- Parameters:
security
- initialized security- Returns:
- routing config consumer
-
create
Create a consumer of routing config to beregistered
with web server routing to process security requests. This method configures security and web server integration from a config instance- Parameters:
config
- Config instance to load security and web server integration from configuration- Returns:
- routing config consumer
-
create
Create a consumer of routing config to beregistered
with web server routing to process security requests. This method expects initialized security and creates web server integration from a config instance- Parameters:
security
- Security instance to useconfig
- Config instance to load security and web server integration from configuration- Returns:
- routing config consumer
-
secure
Secure access using authentication and authorization. Auditing is enabled by default for methods modifying content. When using RBAC (role based access control), just userolesAllowed(String...)
. If you use a security provider, that requires additional data, useSecurityHandler.customObject(Object)
.Behavior:
- Authentication: enabled and required
- Authorization: enabled if provider configured
- Audit: not modified (default: enabled except for GET and HEAD methods)
- Returns:
SecurityHandler
instance configured with authentication and authorization
-
authenticate
If called, request will go through authentication process - defaults to false (even if authorize is true).Behavior:
- Authentication: enabled and required
- Authorization: not modified (default: disabled)
- Audit: not modified (default: enabled except for GET and HEAD methods)
- Returns:
SecurityHandler
instance
-
audit
Whether to audit this request - defaults to false for GET and HEAD methods, true otherwise. Request is audited with event type "request".Behavior:
- Authentication: not modified (default: disabled)
- Authorization: not modified (default: disabled)
- Audit: enabled for any method this gate is registered on
- Returns:
SecurityHandler
instance
-
authenticator
Use a named authenticator (as supported by security - if not defined, default authenticator is used).Behavior:
- Authentication: enabled and required
- Authorization: not modified (default: disabled)
- Audit: not modified (default: enabled except for GET and HEAD methods)
- Parameters:
explicitAuthenticator
- name of authenticator as configured inSecurity
- Returns:
SecurityHandler
instance
-
authorizer
Use a named authorizer (as supported by security - if not defined, default authorizer is used, if none defined, all is permitted).Behavior:
- Authentication: enabled and required
- Authorization: enabled with explicit provider
- Audit: not modified (default: enabled except for GET and HEAD methods)
- Parameters:
explicitAuthorizer
- name of authorizer as configured inSecurity
- Returns:
SecurityHandler
instance
-
rolesAllowed
An array of allowed roles for this path - must have a security provider supporting roles.Behavior:
- Authentication: enabled and required
- Authorization: enabled
- Audit: not modified (default: enabled except for GET and HEAD methods)
- Parameters:
roles
- if subject is any of these roles, allow access- Returns:
SecurityHandler
instance
-
allowAnonymous
If called, authentication failure will not abort request and will continue as anonymous (defaults to false).Behavior:
- Authentication: enabled and optional
- Authorization: not modified (default: disabled)
- Audit: not modified (default: enabled except for GET and HEAD methods)
- Returns:
SecurityHandler
instance
-
authorize
Enable authorization for this route.Behavior:
- Authentication: enabled and required
- Authorization: enabled if provider is present
- Audit: not modified (default: enabled except for GET and HEAD methods)
- Returns:
SecurityHandler
instance
-
enforce
Return a default instance to create a default enforcement point (or modify the result further).Behavior:
- Authentication: not modified (default: disabled)
- Authorization: not modified (default: disabled)
- Audit: not modified (default: enabled except for GET and HEAD methods)
- Returns:
SecurityHandler
instance
-
securityDefaults
Create a new web security instance using the default handler as base defaults for all handlers used. If handlers are loaded from config, than this is the least significant value.- Parameters:
defaultHandler
- if a security handler is configured for a route, it will take its defaults from this handler- Returns:
- new instance of web security with the handler default
-
update
Description copied from interface:Service
UpdatesRouting.Rules
withhandlers
representing this service.
-