Skip to main content

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.

Jump to: navigation, search

Jetty/Tutorial/JAAS



Introduction

Using JAAS with Jetty requires that you complete these tasks:

#Declaring an org.eclipse.jetty.plus.jaas.JAASLoginService #Creating a JAAS login module configuration file #Specifying this configuration file on the Jetty run line

The following sections explain how to accomplish this work.

Declaring an org.eclipse.jetty.plus.jaas.JAASLogin Service

Configure a Jetty org.eclipse.jetty.plus.jaas.JAASLoginService to match the <realm-name> in your web.xml file. For example, if the web.xml contains a realm called "xyzrealm":




 
&lt;login-config&gt;&lt;auth-method&gt;FORM&lt;/auth-method&gt; &lt;realm-name&gt;xyzrealm&lt;/realm-name&gt; &lt;form-login-config&gt;&lt;form-login-page&gt;/login/login&lt;/form-login-page&gt; &lt;form-error-page&gt;/login/error&lt;/form-error-page&gt; &lt;/form-login-config&gt; &lt;/login-config&gt; fckLRfckLRThen the following JAASLoginService would be declared in a Jetty configuration file:fckLR
 
&lt;call name="addBean"&gt;&lt;arg&gt;&lt;new class="org.eclipse.jetty.plus.jaas.JAASLoginService"&gt;&lt;set name="Name"&gt;Test JAAS Realm&lt;/set&gt; &lt;set name="LoginModuleName"&gt;xyz&lt;/set&gt; &lt;/new&gt; &lt;/arg&gt; &lt;/call&gt; fckLRfckLRAlternatively of course, you can set this up in a context xml file that configures a web app:fckLR
 
&lt;set name="securityHandler"&gt;&lt;new class="org.eclipse.jetty.security.ConstraintSecurityHandler"&gt;&lt;set name="loginService"&gt;&lt;new class="org.eclipse.jetty.plus.jaas.JAASLoginService"&gt;&lt;set name="name"&gt;Test JAAS Realm&lt;/set&gt; &lt;set name="loginModuleName"&gt;xyz&lt;/set&gt; &lt;/new&gt; &lt;/set&gt; &lt;/new&gt; &lt;/set&gt; fckLRfckLR
Warning2.png
It is imperative that the contents of the realm-name element in web.xml file and the value of the 'name' property of the JAASLoginService instance are exactly the same
fckLRfckLR=== Step 2 ===fckLRfckLRSet up your LoginModule in a configuration file, following the syntax rules:fckLR
 
xyz { com.acme.SomeLoginModule required debug=true; }; fckLR
Warning2.png
It is imperative that the application name to the left of the opening brace is exactly the same as the value of the 'LoginModuleName' property specified in Step 2.
fckLRfckLRfckLR=== Step 3 ===fckLRfckLRInvoke jetty with the jaas configuration file you created in step 2:fckLR
 
&amp;gt; java -Djava.security.auth.login.config=mylogin.conf -jar start.jar etc/myjetty.xml fckLRfckLR== A Closer Look at the JAASLoginService ==fckLRfckLRTo allow the greatest degree of flexibility in using JAAS with web applications, the JAASLoginService supports a couple of configuration options. Note that you don't ordinarily need to set these explicitly, as Jetty has defaults which will work in 99% of cases. However, should you need to, you can configure:fckLRfckLR* a policy for role-based authorization (Default: org.eclipse.jetty.plus.jaas.StrictRoleCheckPolicy)fckLR* a CallbackHandler (Default: org.eclipse.jetty.plus.jaas.callback.DefaultCallbackHandler)fckLR* a list of classnames for the Principal implementation that equate to a user role (Default: org.eclipse.jetty.plus.jaas.JAASRole)fckLRfckLRHere's an example of setting each of these (to their default values):fckLR
 
&lt;new class="org.eclipse.jetty.plus.jaas.JAASLoginService"&gt;&lt;set name="Name"&gt;xyzrealm&lt;/set&gt; &lt;set name="LoginModuleName"&gt;xyz&lt;/set&gt; &lt;set name="RoleCheckPolicy"&gt;&lt;new class="org.eclipse.jetty.plus.jaas.StrictRoleCheckPolicy"&gt;&lt;/new&gt; &lt;/set&gt; &lt;set name="CallbackHandlerClass"&gt;org.eclipse.jetty.plus.jaas.callback.DefaultCallbackHandler &lt;/set&gt; &lt;set name="roleClassNames"&gt;&lt;array type="java.lang.String"&gt;&lt;item&gt;org.eclipse.jetty.plus.jaas.JAASRole&lt;/item&gt; &lt;/array&gt; &lt;/set&gt; &lt;/new&gt; fckLRfckLR=== RoleCheckPolicy ===fckLRfckLRThe RoleCheckPolicy must be an implementation of the org.eclipse.jetty.plus.jaas.RoleCheckPolicy interface and its purpose is to help answer the question "is User X in Role Y" for role-based authorization requests. The default implementation distributed with jetty is the org.eclipse.jetty.plus.jaas.StrictRoleCheckPolicy, which will assess a user as having a particular role iff that role is at the top of the stack of roles that have been temporarily pushed onto the user or if the user has no temporarily assigned roles, the role is amongst those configured for the user.fckLRfckLRRoles can be temporarily assigned to a user programmatically by using the pushRole(String rolename) method of the org.eclipse.jetty.plus.jaas.JAASUserPrincipal class.fckLRfckLRFor the majority of webapps, the default StrictRoleCheckPolicy will be quite adequate, however you may provide your own implementation and set it on your JAASLoginService instance.fckLRfckLR=== CallbackHandler ===fckLRfckLRA CallbackHandler is responsible for interfacing with the user to obtain usernames and credentials to be authenticated.fckLRfckLRJetty ships with the org.eclipse.jetty.plus.jaas.DefaultCallbackHandler which interfaces the information contained in the request to the Callbacks that are requested by LoginModules. You can replace this default with your own implementation if you have specific requirements not covered by the default.fckLRfckLR=== Role Principal Implementation Class ===fckLRfckLRWhen LoginModules authenticate a user, they usually also gather all of the roles that a user has and place them inside the JAAS Subject. As LoginModules are free to use their own implementation of the JAAS Principal to put into the Subject, jetty needs to know which Principals represent the user and which represent his/her roles when performing authorization checks on &amp;amp;lt;security-constraint&amp;amp;gt;s. The example LoginModules that ship with jetty all use the org.mortbay.jetty.plus.jaas.JAASRole class. However, if you have plugged in some other LoginModules, you must configure the classnames of their role Principal implementations.fckLRfckLR=== Sample Login Modules ===fckLRfckLRAt the time of writing, Jetty provides four sample LoginModule implementations:fckLR* org.eclipse.jetty.plus.jaas.spi.JDBCLoginModulefckLR* org.eclipse.jetty.plus.jaas.spi.PropertyFileLoginModulefckLR* org.eclipse.jetty.plus.jaas.spi.DataSourceLoginModulefckLR* org.eclipse.jetty.plus.jaas.ldap.LdapLoginModulefckLRfckLRWe'll take a look at all of these, but first, a word about password handling in Jetty, as it applies to all LoginModules.fckLRfckLR=== Passwords/Credentials ===fckLRfckLRPasswords can be stored in clear text, obfuscated or checksummed. The class org.eclipse.jetty.http.security.Password should be used to generate all varieties of passwords,the output from which can be cut and pasted into property files or entered into database tables.fckLR
 
&amp;gt; java -cp lib/jetty.jar org.eclipse.jetty.http.security.Password Usage - java org.eclipse.jetty.http.security.Password [&lt;user&gt;] &lt;password&gt;&amp;gt; java -cp lib/jetty.jar org.eclipse.jetty.http.security.Password me you you OBF:20771x1b206z MD5:639bae9ac6b3e1a84cebb7b403297b79 CRYPT:me/ks90E221EY fckLRRead more on securing passwords.fckLRfckLR=== JDBCLoginModule ===fckLRfckLRThe JDBCLoginModule stores user passwords and roles in a database that are accessed via JDBC calls. You can configure the JDBC connection information, as well as the names of the table and columns storing the username and credential, and the name of the table and columns storing the roles.fckLRfckLRHere is an example login module configuration file entry for it using an HSQLDB driver:fckLR jdbc { org.eclipse.jetty.plus.jaas.spi.JDBCLoginModule required debug="true" dbUrl="jdbc:hsqldb:." dbUserName="sa" dbDriver="org.hsqldb.jdbcDriver" userTable="myusers" userField="myuser" credentialField="mypassword" userRoleTable="myuserroles" userRoleUserField="myuser" userRoleRoleField="myrole"; }; fckLRfckLRThere is no particular schema required for the database tables storing the authentication and role information. The properties userTable, userField, credentialField, userRoleTable, userRoleUserField, userRoleRoleField configure the names of the tables and the columns within them that are used to format the following queries:fckLR select &lt;credentialfield&gt;from &lt;usertable&gt;where &lt;userfield&gt;=? select &lt;userrolerolefield&gt;from &lt;userroletable&gt;where &lt;userroleuserfield&gt;=? fckLRfckLRCredential and role information is lazily read from the database when a previously unauthenticated user requests authentication. Note that this information is only cached for the length of the authenticated session. When the user logs out or the session expires, the information is flushed from memory.fckLRfckLRNote that passwords can be stored in the database in plain text or encoded formats, using the Jetty password utility.fckLRfckLR=== DataSourceLoginModule ===fckLRfckLRSimilar to the JDBCLoginModule, but this LoginModule uses a DataSource to connect to the database instead of a jdbc driver. The DataSource is obtained by doing a jndi lookup on java:comp/env/$\{dnJNDIName\}fckLRfckLRHere is a sample login module configuration for it:fckLR ds { org.eclipse.jetty.plus.jaas.spi.DataSourceLoginModule required debug="true" dbJNDIName="ds" userTable="myusers" userField="myuser" credentialField="mypassword" userRoleTable="myuserroles" userRoleUserField="myuser" userRoleRoleField="myrole"; }; fckLRfckLR=== PropertyFileLoginModule ===fckLRfckLRWith this login module implementation, the authentication and role information is read from a property file.fckLR props { org.eclipse.jetty.plus.jaas.spi.PropertyFileLoginModule required debug="true" file="/somewhere/somefile.props"; }; fckLRfckLRThe file parameter is the location of a properties file of the same format as the etc/realm.properties example file. The format is:fckLR&lt;username&gt;: &lt;password&gt;[,&lt;rolename&gt;...] fckLRHere's an example:fckLRfred: OBF:1xmk1w261u9r1w1c1xmq,user,admin harry: changeme,user,developer tom: MD5:164c88b302622e17050af52c89945d44,user dick: CRYPT:adpexzg3FUZAk,admin fckLRfckLRThe contents of the file are fully read in and cached in memory the first time a user requests authentication.fckLRfckLR=== LdapLoginModule ===fckLRfckLRNote that the LdapLoginModule ships in a separate jar, in $JETTY-HOME/lib/ext/jetty-ldap-jaas.jar. It requires JDK1.5 or above.fckLRfckLR ldaploginmodule { org.eclipse.jetty.plus.jaas.spi.LdapLoginModule required debug="true" contextFactory="com.sun.jndi.ldap.LdapCtxFactory" hostname="ldap.example.com" port="389" bindDn="cn=Directory Manager" bindPassword="directory" authenticationMethod="simple" forceBindingLogin="false" userBaseDn="ou=people,dc=alcatel" userRdnAttribute="uid" userIdAttribute="uid" userPasswordAttribute="userPassword" userObjectClass="inetOrgPerson" roleBaseDn="ou=groups,dc=example,dc=com" roleNameAttribute="cn" roleMemberAttribute="uniqueMember" roleObjectClass="groupOfUniqueNames"; }; fckLRfckLR=== Writing Your Own ===fckLRfckLRIf you want to implement your own custom LoginModule, there are two classes to be familiar with:fckLRfckLR AbstractLoginModule.java package org.eclipse.jetty.plus.jaas.spi; public abstract class AbstractLoginModule implements LoginModule { ... public abstract UserInfo getUserInfo (String username) throws Exception; } fckLRfckLR UserInfo.java package org.eclipse.jetty.plus.jaas.spi; public class UserInfo { public UserInfo (String userName, Credential credential, List roleNames) { ... } public String getUserName() { ... } public List getRoleNames () { ... } public boolean checkCredential (Object suppliedCredential) { ... } } fckLRfckLRThe org.eclipse.jetty.plus.jaas.spi.AbstractLoginModule implements all of the javax.security.auth.spi.LoginModule methods. All you need to do is to implement the getUserInfo method to return a org.eclipse.jetty.plus.jaas.UserInfo instance which encapsulates the username, password and role names (note: as java.lang.Strings) for a user.fckLRfckLRThe AbstractLoginModule does not support any caching, so if you want to cache UserInfo (e.g. as does the org.mortbay.jetty.plus.jaas.spi.PropertyFileLoginModule) then you must provide this yourself.fckLRfckLR=== Example JAAS WebApp ===fckLRfckLRThere is an example of authentication and web authorization in the jetty distribution in examples/test-jaas-webapp. It uses the PropertyFileLoginModule to perform authentication based on a simple properties file. To use it with the jetty maven plugin:fckLR &amp;gt; cd examples/test-jaas-webapp &amp;gt; mvn jetty:run fckLRfckLRAlternatively, to use it instead with jetty standalone:fckLR &amp;gt; cd examples/test-jaas-webapp &amp;gt; mvn clean install &amp;gt; cd ../../ &amp;gt; java -jar start.jar etc/jetty.xml etc/jetty-jaas.xml fckLRfckLRThen surf to http://localhost:8080/test-jaas/index.htmlfckLRfckLR== Other Goodies ==fckLRfckLR=== RequestParameterCallback ===fckLRfckLRAs all servlet containers intercept and process a form submission with action j_security_check, it is usually not possible to insert any extra input fields onto a login form with which to perform authentication: you may only pass j_username and j_password. For those rare occasions when this is not good enough, and you require more information from the user in order to authenticate them, you can use the JAAS callback handler org.mortbay.jetty.plus.jaas.callback.RequestParameterCallback. This callback handler gives you access to all parameters that were passed in the form submission. To use it, in the login() method of your custom login module, add the RequestParameterCallback to the list of callback handlers the login module uses, tell it which params you are interested in, and then get the value of the parameter back. Here's an example:fckLRfckLR FooLoginModule.java public class FooLoginModule extends AbstractLoginModule { . . . public boolean login() throws LoginException { . . . Callback[] callbacks = new Callback[3]; callbacks[0] = new NameCallback(); callbacks[1] = new ObjectCallback(); //as an example, look for a param named "extrainfo" in the request //use one RequestParameterCallback() instance for each param you want to access callbacks[2] = new RequestParameterCallback (); ((RequestParameterCallback)callbacks[2]).setParameterName ("extrainfo"); . . . callbackHandler.handle(callbacks); String userName = ((NameCallback)callbacks[0]).getName(); Object pwd = ((ObjectCallback)callbacks[1]).getObject(); List paramValues = ((RequestParameterCallback)callbacks[2]).getParameterValues(); //use the userName, pwd and the value(s) of the parameter named "extrainfo" to //authenticate the user . . . } fckLR

Details

{{{details}}}fckLR



</rolename></password></username></userroleuserfield></userroletable></userrolerolefield></userfield></usertable></credentialfield></password></user>

Back to the top