Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Jetty/Feature/Realms"
(New page: {{Jetty Feature | introduction = Security realms allow you to secure your web applications against unauthorized access. Protection is based on authentication that identifies who is request...) |
|||
| Line 4: | Line 4: | ||
| body = | | body = | ||
| − | A webapp statically declares its security requirements in | + | A webapp statically declares its security requirements in its web.xml file. Authentication is controlled by the <login-config> element. Access controls are specified by <security-constraint> and <security-role-ref> elements. When a request is received for a protected resource, the web container checks if the user performing the request is authenticated, and if the user has a role assignment that permits access to the requested resource. |
The Servlet Specification does not address how the static security information in the {{WEB-INF/web.xml}} file is mapped to the runtime environment of the container. Jetty does this with the "realm" concept. | The Servlet Specification does not address how the static security information in the {{WEB-INF/web.xml}} file is mapped to the runtime environment of the container. Jetty does this with the "realm" concept. | ||
Revision as of 18:42, 23 December 2009
Introduction
Security realms allow you to secure your web applications against unauthorized access. Protection is based on authentication that identifies who is requesting access to the webapp and access control that restricts what can be accessed and how it is accessed within the webapp.
Feature
A webapp statically declares its security requirements in its web.xml file. Authentication is controlled by the <login-config> element. Access controls are specified by <security-constraint> and <security-role-ref> elements. When a request is received for a protected resource, the web container checks if the user performing the request is authenticated, and if the user has a role assignment that permits access to the requested resource.
The Servlet Specification does not address how the static security information in the Template:WEB-INF/web.xml file is mapped to the runtime environment of the container. Jetty does this with the "realm" concept.
A realm has a unique name, and is composed of a set of users. Each user has authentication information (e.g. a password) and a set of roles associated with him/herself.
Additional Resources
See Configuring Security Realms tutorial for information on how to configure Jetty security realms.