3 Legal Notice Copyright 2012 Red Hat, Inc. T his document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Java is a registered trademark of Oracle and/or its affiliates. XFS is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project. T he OpenStack Word Mark and OpenStack Logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community. All other trademarks are the property of their respective owners. Abstract T he JBoss Negotiation Guide is aimed at system administrators and developers, who wish to set up the SPNEGO authentication on their JBoss Enterprise Application Platform. T his guide provides instructions for its configuration and additional details on the setup of the AdvancedLdapLoginModule, which allows integration of the SPNEGO authentication with an LDAP server.

7 JBoss Enterprise Application Platform 5 Negotiation User Guide Preface 1. Document Conventions T his manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information. In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts set. T he Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later include the Liberation Fonts set by default Typographic Conventions Four typographic conventions are used to call attention to specific words and phrases. T hese conventions, and the circumstances they apply to, are as follows. Mono-spaced Bold Used to highlight system input, including shell commands, file names and paths. Also used to highlight keys and key combinations. For example: T o see the contents of the file m y_next_bestselling_novel in your current working directory, enter the cat m y_next_bestselling_novel command at the shell prompt and press Enter to execute the command. The above includes a file name, a shell command and a key, all presented in mono-spaced bold and all distinguishable thanks to context. Key combinations can be distinguished from an individual key by the plus sign that connects each part of a key combination. For example: Press Enter to execute the command. Press Ctrl+Alt+F2 to switch to a virtual terminal. T he first example highlights a particular key to press. T he second example highlights a key combination: a set of three keys pressed simultaneously. If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in m ono-spaced bold. For example: File-related classes include filesystem for file systems, file for files, and dir for directories. Each class has its own associated set of permissions. Proportional Bold T his denotes words or phrases encountered on a system, including application names; dialog box text; labeled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example: Choose System Preferences Mouse from the main menu bar to launch Mouse Preferences. In the Buttons tab, select the Left-handed m ouse check box and click Close to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand). T o insert a special character into a gedit file, choose Applications Accessories 4

8 Preface Character Map from the main menu bar. Next, choose Search Find from the Character Map menu bar, type the name of the character in the Search field and click Next. T he character you sought will be highlighted in the Character T able. Double-click this highlighted character to place it in the T ext to copy field and then click the Copy button. Now switch back to your document and choose Edit Paste from the gedit menu bar. T he above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context. Mono-spaced Bold Italic or Proportional Bold Italic Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example: T o connect to a remote machine using ssh, type ssh domain.name at a shell prompt. If the remote machine is example.com and your username on that machine is john, type ssh exam ple.com. T he m ount -o rem ount file-system command remounts the named file system. For example, to remount the /home file system, the command is mount -o remount /home. T o see the version of a currently installed package, use the rpm -q package command. It will return a result as follows: package-version-release. Note the words in bold italics above username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system. Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example: Publican is a DocBook publishing system Pull-quote Conventions T erminal output and source code listings are set off visually from the surrounding text. Output sent to a terminal is set in mono-spaced roman and presented thus: books Desktop documentation drafts mss photos stuff svn books_tests Desktop1 downloads images notes scripts svgs Source-code listings are also set in m ono-spaced rom an but add syntax highlighting as follows: 5

9 JBoss Enterprise Application Platform 5 Negotiation User Guide package org.jboss.book.jca.ex1; import javax.naming.initialcontext; public class ExClient { public static void main(string args[]) throws Exception { InitialContext inictx = new InitialContext(); Object ref = inictx.lookup("echobean"); EchoHome home = (EchoHome) ref; Echo echo = home.create(); System.out.println("Created Echo"); } } System.out.println("Echo.echo('Hello') = " + echo.echo("hello")); 1.3. Notes and Warnings Finally, we use three visual styles to draw attention to information that might otherwise be overlooked. Note Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier. Important Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' will not cause data loss but may cause irritation and frustration. Warning Warnings should not be ignored. Ignoring warnings will most likely cause data loss. 2. Getting Help and Giving Feedback 2.1. Do You Need Help? If you experience difficulty with a procedure described in this documentation, visit the Red Hat Customer Portal at T hrough the customer portal, you can: search or browse through a knowledgebase of technical support articles about Red Hat products. submit a support case to Red Hat Global Support Services (GSS). access other product documentation. 6

10 Preface Red Hat also hosts a large number of electronic mailing lists for discussion of Red Hat software and technology. You can find a list of publicly available mailing lists at https://www.redhat.com/mailman/listinfo. Click on the name of any mailing list to subscribe to that list or to access the list archives Give us Feedback If you find a typographical error, or know how this guide can be improved, we would love to hear from you. Submit a report in Bugzilla against the product JBoss Enterprise Application Platform 5 and the component doc-negotiation_user_guide. T he following link will take you to a pre-filled bug report for this product: Fill out the following template in Bugzilla's Description field. Be as specific as possible when describing the issue; this will help ensure that we can fix it quickly. Document URL: Section Number and Name: Describe the issue: Suggestions for improvement: Additional information: Be sure to give us your name so that you can receive full credit for reporting the issue. 7

11 JBoss Enterprise Application Platform 5 Negotiation User Guide Chapter 1. Introduction JBoss Negotiation is a component of JBoss Enterprise Application Platform, which provides the SPNEGO-based (Simple and Protected Negotiation) SSO (Single Sign On) mechanism. JBoss Negotiation is located in $JBOSS_HOME/jboss-as/com m on/lib/jboss-negotiation.jar SPNEGO is a Generic Security Services Application Program Interface (GSSAPI) mechanism for clientserver authentication. It allows silent authentication to remote systems and access to security services. It can also delegate user credentials to a remote system so the remote system can contact further systems on behalf of the user SPNEGO Authentication Process Generally, the client sends the input credentials to the server and the login module of the server verifies the credentials against its credential store when a user is authenticating to a server. SPNEGO authentication differs in several aspects: 1. T he application server authenticates itself against the KDC and obtains a ticket before it can authenticate the user. 2. Only then, the server prompts the client to authenticate. T he client responds with a SPNEGO token and the server uses its own ticket to decode client's ticket and then responds to the client. 3. A client can request the server to authenticate itself if required. 4. A client can delegate its credentials to the server so that the server can call other systems on behalf of the calling client. JBoss Negotiation is typically useful in the following scenario: The user logs into a desktop computer with a log in that is governed by an Active Directory domain or FreeIPA. T he user launches a web browser and accesses a web application that uses JBoss Negotiation. T he web browser transfers the desktop credentials to the web application. Important You can configure Active Directory and FreeIPA to use JBoss Negotiation (refer to Chapter 6, Configuring FreeIPA and Chapter 5, Configuring Microsoft Active Directory ) Configuration Overview T o have your environment configured to use JBoss Negotiation, you need to do the following: Configure your application server to use JBoss Negotiation (refer to Chapter 2, Application Server Configuration). Optionally configure Active Directory or FreeIPA to use JBoss Negotiation (refer to Chapter 5, Configuring Microsoft Active Directory or Chapter 6, Configuring FreeIPA). Configure client web browsers to use JBoss Negotiation (refer to Chapter 7, Configuring Web Browsers). T est the setup with Negotiation T oolkit (refer to Chapter 8, Negotiation Toolkit). Configure your web applications to use JBoss Negotiation (refer to Chapter 9, Configuring Web 8

13 JBoss Enterprise Application Platform 5 Negotiation User Guide Chapter 2. Application Server Configuration T o configure JBoss Negotiation to run on JBoss Enterprise Application Platform, you need to do the following: Extend the core authentication mechanism to support JBoss Negotiation (add the SPNEGO authenticator). Define the application security domain, which allows an application to communicate with the application server through the SPNEGOLoginModule. Define the server security domain, which allows the application server to authenticate itself to the KDC for the first time. You may also need to configure the realm properties to allow the server to locate the authentication realm (Kerberos realm) if the server was not previously configured to do so. JBoss Negotiation comes with Negotiation T oolkit, a web application, which allows you to test your SPNEGO setup. Consider using the application before testing on your own web applications (refer to Chapter 8, Negotiation Toolkit) Adding the SPNEGO Authenticator T o add the SPNEGO authenticator to the core authentication mechanism, do the following: 1. Open the $JBOSS_HOME/server/PROFILE/deployers/jbossweb.deployer/MET A- INF/war-deployers-jboss-beans.xm l file for editing. 2. Locate the property authenticators. 3. Add the following entry to the property: <property name="authenticators"> <map class="java.util.properties" keyclass="java.lang.string" valueclass="java.lang.string"> <entry> <key>spnego</key> <value>org.jboss.security.negotiation.negotiationauthenticator</value> </entry> The key value is arbitrary; however, if you want to use the Negotiation Toolkit to test your server setup, make sure you use the SPNEGO value as the tool works only with the SPNEGO authenticator with this name Defining Server Security Domain The application server must define a security domain to be able to authenticate to the KDC for the first time. Local Credentials Cache in Kerberos Krb5LoginModule can use a local credentials cache; however, this option is incompatible with the storekey option, which is required by SPNEGO. Make sure the module does not use the local credentials cache. To define a server security domain, do the following: 10

14 Chapter 2. Application Server Configuration 1. Open the $JBOSS_HOME/server/$PROFILE/conf/login-config.xm l file for editing. 2. Define the application policy element with the authentication element with the following options: storekey If true the private key is cached in the Subject (set to true). usekeyt ab If true the key is loaded from a keytab file (set to true). principal The attribute needs to state the full name of the principal to obtain from the keytab file. keyt ab The attribute defines the full path to the keytab file with the server key (key for encrypting the information between the server and KDC). donotprompt If true password prompting is turned off (as this is a server, set to true). debug If true the system logs additional debug information to ST DOUT. Example 2.1. Server security domain <application-policy name="host"> <authentication> <login-module code="com.sun.security.auth.module.krb5loginmodule" flag="required"> <module-option name="storekey">true</module-option> <module-option name="usekeytab">true</module-option> <module-option KERBEROS.JBOSS.ORG</module-option> <module-option name="keytab">/home/jboss_user/testserver.keytab</module-option> <module-option name="donotprompt">true</module-option> <module-option name="debug">true</module-option> </login-module> </authentication> </application-policy> 2.3. Defining Application Security Domain T o allow an application to communicate with the application server through the SPNEGOLoginModule, you need to define the application security domain on the application server. T o define the application security domain, do the following: 1. Open the $JBOSS_HOME/jboss-as/server/$PROFILE/conf/login-config.xm l file for editing. 2. Define a new application policy with the following chained configuration: T he SPNEGOLoginModule and its configuration with the following options: 11

15 JBoss Enterprise Application Platform 5 Negotiation User Guide <module-option name="password-stacking">usefirstpass</module-option> T he password-stacking option activates client-side authentication of clients with other login modules. Set the password-stacking option to usefirstpass, so the module looks first for a shared user name and password with javax.security.auth.login.name and javax.security.auth.login.password respectively (for further information refer to Password Stacking in the Security Guide). <module-option name="serversecuritydomain">domainname</module-option> T he serversecuritydomain option defines the server security domain, which defines the authentication module (Kerberos) and server authentication properties (refer to Section 2.2, Defining Server Security Domain ). T he login module which returns the roles of the authenticated user and its configuration options. You can make use of the UsersRolesLoginModule that obtains the user roles from a properties file or AdvancedLdapLoginModule, which obtains user roles from an LDAP server following GSSAPI. For further information refer to Section 2.4, Role Mapping. Example 2.2. Application Security Domain <application-policy name="spnego"> <authentication> <login-module code="org.jboss.security.negotiation.spnego.spnegologinmodule" flag="requisite"> <module-option name="password-stacking">usefirstpass</module-option> <module-option name="serversecuritydomain">host</module-option> </login-module> <login-module code="org.jboss.security.auth.spi.usersrolesloginmodule" flag="required"> <module-option name="password-stacking">usefirstpass</module-option> <module-option name="usersproperties">props/spnegousers.properties</module-option> <module-option name="rolesproperties">props/spnegoroles.properties</module-option> </login-module> </authentication> </application-policy> In Example 2.2, Application Security Domain we have defined an application security domain called SPNEGO with two login modules: org.jboss.security.negotiation.spnego.spnegologinmodule provides SPNEGO user authentication; org.jboss.security.auth.spi.usersrolesloginmodule returns the roles of the user authenticated by the SPNEGOLoginModule (the roles are filtered from a users properties file) Role Mapping Once the user has been authenticated against the KDC (this occurs through org.jboss.security.negotiation.spnego.spnegologinmodule), the application server needs to obtain the 12

16 Chapter 2. Application Server Configuration user roles. T he authentication can use either the org.jboss.security.auth.spi.usersrolesloginmodule to obtain user roles from a roles.properties file or the org.jboss.security.negotiation.advancedldaploginmodule to obtain user roles from an LDAP server Setting up Role Mapping with a Roles Properties File T o allow SPNEGO to obtain the roles of an authenticated user from a roles.properties file, do the following: 1. In the application security domain, set the second login module of the SPNEGO authentication to org.jboss.security.auth.spi.usersrolesloginmodule (refer to Example 2.2, Application Security Domain ) and provide the module options. Refer to UsersRolesLoginModule in the Security Guide). 2. If the application security domain is defined in the $JBOSS_HOME/server/$PROFILE/conf/login-config.xml file, define the user roles in the $JBOSS_HOME/server/$PROFILE/conf/props/spnego-users.properties file. Use the following pattern: fullyqualifiedusername=comma-separatedlistofroles Example 2.3. roles.properties file # A roles.properties file for use with the UsersRolesLoginModule KERBEROS.JBOSS.ORG=Users,Admins Setting up Role Mapping with an LDAP Server T he AdvancedLdapLoginModule allows you to obtain the roles of a user, who was previously authenticated against a KDC with the SPNEGOLoginModule. T he AdvancedLdapLoginModule is based on the LdapExtLoginModule and follows GSSAPI. Full LDAP authentication and role look up In this chapter we discuss the module in chained configuration with the SPNEGOLoginModule; however, you can use the module for both authentication and role look up from an LDAP server. For further details on such configuration, refer to Appendix A, Advanced LDAP Login Module: Full LDAP Authentication. T o make use of the AdvancedLdapLoginModule in the chained configuration with the SPNEGOLoginModule, you need to chain it with the SPNEGOLoginModule in the SPNEGO application security domain: set the second login module of SPNEGO authentication to org.jboss.security.negotiation.advancedldaploginmodule (refer to Example 2.2, Application Security Domain ). To set up the role mapping to an LDAP server, you need to do the following: Define InitialLdapContext properties: these properties are used to obtain LDAP connection (refer to Section , Defining Initial LDAP Context with GSSAPI ; for details on the Java API refer to Define DN (Distinguished Name) properties: these properties are used to search for the authenticated user on the LDAP server (refer to Section , Defining DN Search ). Define role search properties: these properties govern the role search on the LDAP server (Section , Defining Role Search ). 13

17 JBoss Enterprise Application Platform 5 Negotiation User Guide T he properties set on the login mode are passed into the InitialLdapContext constructor; that means you can make use of any of the options supported by the LdapCtxFactory Defining Initial LDAP Context with GSSAPI T o obtain the initial LDAP Context, define the following module properties for the AdvancedLdapLoginModule in the application security domain (Section 2.3, Defining Application Security Domain ): bindauthentication defines the authentication type (set the property value to GSSAPI to use GSSAPI-based authentication). jaassecuritydomain defines the security domain that is used to obtain the subject required for the connection (refer to Section 2.2, Defining Server Security Domain for information defining the required jaassecuritydomain) Defining DN Search After the module has created the LDAP initial context, it takes the provided username and searches for the user DN. T o define the properties of the search, provide the following properties: basectxdn defines the fixed DN of the context to search for the user; consider that this is not the Distinguished Name of the location where the actual users are located but DN of the location where the objects containing the users are located (that is, for Active Directory, this is the DN with the user account). basefilter defines the search filter used to locate the context of the user to authenticate; the input username/userdn as obtained from the login module callback substitutes the {0} expression. T his substitution behavior comes from the standard DirContext?.search(Name, String, Object[], SearchControls? cons) method. A common example search filter is (uid={0}) searcht imelimit defines the timeout for the user and role search in milliseconds (defaults to 10000, that is 10 seconds). Note To disable the user DN search, omit the basectxdn property; the provided username will be used as the DN in the login module User Authentication If the AdvancedLdapLoginModule is not the first login module and a previous login module has already authenticated the user, user authentication is skipped. 14

18 Chapter 2. Application Server Configuration For user authentication, you can define the following property: allowemptypassword If empty (length==0) passwords are passed to the LDAP server. An empty password is treated as an anonymous login by an LDAP servers. Set the property to false to reject empty passwords or to true to allow the LDAP server to validate an empty password (the default is false) Defining Role Search T he AdvancedLdapLoginModule passes the properties that define the search for a particular user and its roles to the LDAP server. Important T he following role search settings are similar to the LdapExtLoginModule settings; however, the recursion now finds the roles listed within a DN. rolesctxdn defines the fixed DN of the context to search for user roles; consider that this is not the Distinguished Name of the location where the actual roles are but the DN of the location where the objects containing the user roles are (that is, for Active Directory, this is the DN where the user account is). rolefilter defines the search filter used to locate the roles of the authenticated user. The input username/userdn as obtained from the login module callback substitutes the {0} expression in the filter definition. T he authenticated userdn substitutes the {1} in the filter definition. An example search filter that matches the input username is (m em ber={0}). An alternative that matches the authenticated userdn is (m em ber={1}). Note If you omit the rolefilter attribute, the role search will use the UserDN as the DN to obtain the roleattributeid value. roleattributeid defines the name of the role attribute of the context that corresponds to the name of the role. If the roleattributeisdn property is set to true, this property is the DN of the context to query for the rolenameattributeid attribute. If the roleattributeisdn property is set to false, this property is the attribute name of the role name. roleattributeisdn defines if the role attribute contains the fully distinguished name of a role object or the role name. If false, the role name is taken from the value of the user's role attribute. If true, the role attribute represents the distinguished name of a role object. The role name is taken from 15

19 JBoss Enterprise Application Platform 5 Negotiation User Guide the value of the rolenameattributeid attribute of the corresponding object. In certain directory schemas (for example, Microsoft Active Directory), role (group)attributes in the user object are stored as DNs to role objects and not as simple names. In such case, set this property to true. The default value of this property is false. rolenameattributeid defines the role attribute of the context which corresponds to the name of the role. If the roleattributeisdn property is set to true, this property is used to find the name attribute of the role object. If the roleattributeisdn property is set to false, this property is ignored. recurseroles defines if the recursive role search is enabled. The login module tracks already added roles to handle cyclic references. searchscope allows to limit the search scope to one of the following (the default value is SUBTREE_SCOPE): OBJECT_SCOPE - searches the named roles context only. ONELEVEL_SCOPE - searches directly in the named roles context. SUBTREE_SCOPE - searches only the object if the role context is not a DirContext?. If the roles context is a DirContext?, the subtree rooted at the named object and the named object itself are searched. searcht imelimit defines the timeout for the user/role searches in milliseconds (defaults to 10000, that is 10 seconds). Note Both searches use the same searcht imelimit setting Examples of LDAP Configuration with the SPNEGO Module T he following configurations of the SPNEGO authentication uses the SPNEGOLoginModule and LDAP login module. T his chained configuration is identical for FreeIPA and Active Directory with the exception of the basefilter value, which defines the name to search for in LDAP identified by the SPNEGOLoginModule (for the relevant ldiff dump refer to Section A.2.1, Full LDAP Authentication for Active Directory and Section A.2.2, Full LDAP Authentication for Free IPA ). Note that the password-stacking property is set to usefirstpass on both login modules to allow the SPNEGOLoginModule to pass the name of the authenticated user to the AdvancedLdapLoginModule Chained Configuration on FreeIPA T he following configuration shows the AdvancedLdapLoginModule chained after the SPNEGOLoginModule for FreeIPA: 16

22 Chapter 3. TRACE Logging Chapter 3. TRACE Logging To enable logging for JBoss Security and so also for the authenticator of JBoss Negotiation, do the following: 1. Open the $JBOSS_HOME/server/$PROFILE/conf/jboss-log4 j.xm l 2. Add the following to enable full T RACE logging for org.jboss.security: <category name="org.jboss.security"> <priority value="trace"/> </category> 3. Optionally allow additional logging for the com.sun.security.auth.module.krb5loginmodule login module. To do so, set the debug option to true: <module-option name="debug">true</module-option> 4. Set the system property -Dsun.security.krb5.debug=true to get verbose output of the entire GSSAPI negotiation process Configuring Message Tracing You can log the exchanged messages selectively at T RACE level. Both, the Request and Response messages, can be logged and that either as Hex or as Base64 or both. T he base category for message tracing is org.jboss.security.negotiation.messaget race. If you enable TRACE logging for this category, all request and response messages are logged at the TRACE level in both Hex and in Base64 encoding. Example 3.1. Configuration for tracking all messages <category name="org.jboss.security.negotiation.messagetrace"> <priority value="trace"/> </category> To reduce the logging to either just request or just response messages, append.request or.response to the category value. Example 3.2. Configuration for tracking only request messages (messages are logged in both Hex and Base64 ) <category name="org.jboss.security.negotiation.messagetrace.request"> <priority value="trace"/> </category> 19

24 Chapter 4. Passing Authentication Properties to the Server Chapter 4. Passing Authentication Properties to the Server After you have set up JBoss Negotiation, you need to make sure to pass the Kerberos realm properties to JBoss Application Server: java.security.krb5.realm the Kerberos realm the server authenticates against java.security.krb5.kdc KDC hostname Note Skip this step if you are running your JBoss installation on a host which is already configured to authenticate against a KDC. For further information about the properties, refer to Java Generic Security Services (Java GSS) and Kerberos. You can pass the properties to the server either from the command line or add them to the server properties Passing the Properties from the Command Line T o send the properties to the server from the command line, substitute KERBEROS.JBOSS.ORG with your realm and issue the run command with the respective Java properties: On Red Hat Enterprise Linux, run the following command:./run.sh -Djava.security.krb5.realm=KERBEROS.JBOSS.ORG - Djava.security.krb5.kdc=kerberos.security.jboss.org On Windows, run the following command: run.bat Djava.security.krb5.realm=KERBEROS.JBOSS.ORG - Djava.security.krb5.kdc=kerberos.security.jboss.org These properties are valid only until the server shutdown and you need to pass them to the server on every start Adding the Properties to the System Properties T o make the properties permanent and have an application server start always with the SPNEGO mechanism, define the properties in the $JBOSS_HOME/server/$PROFILE/deploy/propertiesservice.xm l descriptor. Make sure the properties are loaded before the first authentication attempt (JBoss does not allow any incoming HTTP connections before the server has started up fully). Open the descriptor and add the following attribute to the jboss:type=service,nam e=system Properties MBean: 21

25 JBoss Enterprise Application Platform 5 Negotiation User Guide <attribute name="properties"> java.security.krb5.kdc=kerberos.security.jboss.org java.security.krb5.realm=kerberos.jboss.org </attribute> Multiple KDCs If you are using one or more slave KDCs in addition to your master KDC, list the KDCs in a colonseparated list after the java.security.krb5.kdc system property. T he system will use the provided alternative KDC if the master KDC is not available. Example 4.1. Running a server with multiple KDCs./run.sh -Djava.security.krb5.realm=KERBEROS.JBOSS.ORG:SLAVE_KDC.JBOSS.ORG - Djava.security.krb5.kdc=kerberos.security.jboss.org 22

26 Chapter 5. Configuring Microsoft Active Directory Chapter 5. Configuring Microsoft Active Directory Important The domain details in this chapter differ from the domain details used in the rest of this guide. T o configure Active Directory to authenticate user through JBoss Negotiation you need to do the following: Create a server user account and configure it as a Service Principal Name (SPN) account: the user of the Service Principal Name account (SPN account) acts as a connection between the Kerberos server, the Active Directory and the JBoss web server. Generate a keytab file for the server user and export it to the application server. The application server uses the keytab to authenticate to KDC in AD. Important Make sure you are using an Active Directory domain controller. It is not possible to use a Windows machine with accounts managed locally. Warning Instructions in this guide apply to Windows 2003 and may differ from the instructions relevant for your Windows operating system User Account for the Application Server To configure an SPN account for the application server on the AD domain controller, you need Setspn and Ktpass. The command line utilities are part of Windows Server 2003 Support Tools and serve for mapping the server user name to the application server and its HTTP service. T he utilities are available on Microsoft web pages. You need to create a regular user account for the server in the AD domain (make sure it is a user account, not a computer account) and map the account to the service account Creating Server User To create a new user for the server, do the following: 1. Go to Start Administrative T ools Active Directory Users and Computers 2. In the Active Directory Users and Com puters window, go to Action New User 23

27 JBoss Enterprise Application Platform 5 Negotiation User Guide Figure 5.1. New User 3. In the New User window, enter the user details and click Next. Figure 5.1, New User uses the vm 104.gsslab.rdu.redhat.com and defines a user called testserver. 4. Enter the password for the user and select the User cannot change password and Password never expires. Important Make sure you have entered a valid password as changing the password later can invalidate the keytab file and break your JBoss installations. 24

28 Chapter 5. Configuring Microsoft Active Directory Figure 5.2. New User Password 5. Click Next and Finish. Figure 5.3. New User Finish 6. In the Active Directory Users and Com puters window, right-click the user and click Properties. 7. In the user properties window, click the Account tab and make sure the Do not require 25

29 JBoss Enterprise Application Platform 5 Negotiation User Guide Kerberos preauthentication and Use DES encryption types for this account are selected under Account Options. Figure 5.4. User Properties Now you need to create and export the keytab file for the created user Exporting Keytab Once you have created the user account for the application server, use the Ktpass utility to map the SPN account as a trusted host and export the keytab for the server: 1. Issue the ktpass command to map the created user as a trusted host and generate the keytab file. The -princ option defines the service principal that is being mapped to and the -mapuser option defines the user account being mapped to. ktpass -princ <service principal mapping> -out <target keytab file> -pass * -mapuser <user mapping> Example 5.1. ktpass command ktpass -princ -out C:\testeserver.host.keytab -pass * -mapuser KERBEROS\testserver 26

31 JBoss Enterprise Application Platform 5 Negotiation User Guide Chapter 6. Configuring FreeIPA Before you configure FreeIPA to use JBoss Negotiation, make sure you have FreeIPA installed and configured correctly, and the clients are able to obtain Kerberos tickets. Detailed FreeIPA documentation is available on Warning Due to the supported encryption types of FreeIPA, the JBoss application server must run on a Java 6 JVM with unlimited cryptography enabled. T o configure FreeIPA to authenticate users through JBoss Negotiation you need to do the following: Create a service principal for the server and add the HTTP service to it. The server user acts as a connection between FreeIPA and the JBoss web server. Generate a keytab file for the server user and export it to the application server. The application server uses the keytab to authenticate to KDC in FreeIPA. Tested on FreeIPA 1.1 T hese instructions apply to FreeIPA Creating Service Principal You need to create the service principal, which represents the HT T P service of your JBoss Application Server to allow the clients to request the ticket for this service. Note Full information on service principal creation is available on 1. The simplest way to create a service principal is through the FreeIPA WebUI: access the tool as an administrator. 2. Click the Add Service Principal link. 28

32 Chapter 6. Configuring FreeIPA Figure 6.1. Adding Service Principal 3. Set the hostname to the host name of your server (test_server.jboss.org) and the service type to HTTP, and click Add Principal. 29

33 JBoss Enterprise Application Platform 5 Negotiation User Guide Figure 6.2. View Service Principal Note Creating the service principal requires the host name to be mapped with DNS. If this procedure fails, on the command line, issue the following command to create the principal: ipa-addservice HT T JBOSS.ORG --force 6.2. Exporting keytab Warning Exporting a new keytab resets the secret associated with the service principal and invalidates any keytabs created previously for the principal. To export a keytab for the server, do the following: 1. Obtain the Kerberos ticket-granting ticket for an administrator: issue the command kinit <admin>. 2. T o obtain the keytab, issue the command ipa-getkeytab with the options: 30

34 Chapter 6. Configuring FreeIPA -s -p -k FreeIPA server to obtain the keytab from Non-realm part of the full principal name File to append the keytab Figure 6.3. Get Keytab Once you have set up the service principal and exported the keytab, make sure your server security domain uses the output keytab file (refer to Section 2.2, Defining Server Security Domain ) and configure the second login module to allow the client to load the roles assigned to the authenticated user (refer to Section 2.4, Role Mapping ). 31

35 JBoss Enterprise Application Platform 5 Negotiation User Guide Chapter 7. Configuring Web Browsers Prerequisite: DNS Setting Web browsers need to trust the application server they communicate with. T o add the application server to trusted resources, add the IP address of the JBoss application server to trusted hosts: on Red Hat Enterprise Linux, edit the /etc/hosts file and make sure the file is used for host name lookups; on Windows edit C:\windows\system 32\drivers\etc\hosts). You can make this change either on your DNS server or locally on the client machine. If the Kerberos realm is KERBEROS.JBOSS.ORG and the server hosting JBoss is testserver then the IP address you need to add as a trusted host is testserver.kerberos.jboss.org Configuring Internet Explorer T he instructions on how to enable JBoss Negotiation in Internet Explorer (IE) apply to Internet Explorer 6 on Microsoft Windows By default Internet Explorer only performs SPNEGO authentication against sites in the Local intranet zone. T o enable the SPNEGO negotiation, add the server URL to the Local intranet sites: 1. On the T ools menu, click Internet Options. Figure 7.1. T ools - Internet Options 2. In the Internet Options dialog, click the Security tab label. 3. In the Security tab, make sure the Local intranet icon is selected and click the Sites button. 32

37 JBoss Enterprise Application Platform 5 Negotiation User Guide T he server appears in the Web sites list below. Internet Explorer now trusts the JBoss installation and performs the SPNEGO negotiation. Make sure to test the Negotiation with the Basic Negotiation servlet (refer to Section 8.2, Basic Negotiation ) Configuring Firefox T he instructions on how to enable SPNEGO negotiation in Mozilla Firefox apply to Mozilla Firefox on Microsoft Windows 2003 and to Firefox on Fedora 9. T o enable the SPNEGO negotiation, change the Mozilla Firefox configuration as follows: 1. Navigate to the about:config URL with the configuration options for Firefox. 2. Set the filter to network.negotiate to display the relevant options. Figure 7.4. Firefox Configuration 3. Double-click the network.negotiate-auth.delegation-uris and in the Enter string value dialog, enter the URI for SPNEGO negotiation. The URI can be entered as a partial URI, for example or testserver or a full URI, for example Figure 7.5. Firefox Configuration 34

39 JBoss Enterprise Application Platform 5 Negotiation User Guide Chapter 8. Negotiation Toolkit The Negotiation Toolkit is a web application for testing of the SPNEGO configuration so you do not need to test your configuration with your application. T he jboss-negotiation-toolkit.war file is available at https://repository.jboss.org/nexus/content/groups/public/org/jboss/security/jbossnegotiation-toolkit/2.0.3.sp1/jboss-negotiation-toolkit sp1.war. Copy the file to the $JBOSSHOME/server/$PROFILE/deploy directory to have the Negotiation T oolkit deployed. T he toolkit assumes that the authenticator has the name SPNEGO and that the application security domain is named SPNEGO. If either of these have other names, deploy the web application as an exploded archive and modify web.xm l and jboss-web.xm l: In the WEB-INF/web.xm l file, update the authenticator key in auth-m ethod (<authm ethod>spnego</auth-m ethod>. In the WEB-INF/jboss-web.xm l file, update the name of the security domain in securitydom ain (<security-dom ain>spnego</security-dom ain>. Once deployed, access the Negotiation T oolkit web application at Note Make sure you have set the DNS entry as described in Prerequisite: DNS Setting in Section 2.3, Defining Application Security Domain Front Page T he main page for the Negotiation T oolkit contains links to the toolkit utilities, which test the mechanisms of SPNEGO authentication. It is recommended that you follow the links from top to bottom. 36

40 Chapter 8. Negotiation Toolkit Figure 8.1. Negotiation T oolkit Front Page Note Make sure you have completed the installation before you use the Negotiation T oolkit as the toolkit tests involve communication with the application server, web browser, and the KDC Basic Negotiation T he Basic Negotiation servlet tests if the web browser trusts the application server: it prompts the web browser to negotiation and checks if the application server received a negotiation token. If the web browser failed to send a negotiation token, the servlet displays a web page similar to Figure 8.2, Basic Negotiation Failure 37

42 Chapter 8. Negotiation Toolkit Figure 8.3. Basic Negotiation Success T he web page shows some of the information contained within the negotiation token Security Domain Test T he Security Domain T est tests if the application server can authenticate against the KDC through its security domain. First, the servlet prompts you to enter the name of the security domain (we have been using the domain host throughout this guide; the page is shown in Figure 8.4, Security Domain T est ). 39

Single Sign-On Using SPNEGO Introduction As of Percussion CM Server version 7.0.2, build 201106R01, patch level RX-17069, Windows Single Sign-On (SSO) using SPNEGO is now supported. Through the SSO feature,

ENABLING SINGLE SIGN-ON: SPNEGO AND KERBEROS Technical Bulletin For Use with DSView 3 Management Software Avocent, the Avocent logo, The Power of Being There and DSView are registered trademarks of Avocent

How-to: Single Sign-On Document version: 1.02 nirva systems info@nirva-systems.com nirva-systems.com How-to: Single Sign-On - page 2 This document describes how to use the Single Sign-On (SSO) features

CHAPTER 4 Sponsors are the people who use Cisco NAC Guest Server to create guest accounts. Sponsor authentication authenticates sponsor users to the Sponsor interface of the Guest Server. There are five

CA Performance Center Single Sign-On User Guide 2.4 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is

CHAPTER 39 The single sign on feature allows end users to log into a Windows client machine on a Windows domain, then use certain Cisco Unified Communications Manager applications without signing on again.

Deploying CTERA Agent via Microsoft Active Directory and Single Sign On Cloud Attached Storage September 2015 Version 5.0 Copyright 2009-2015 CTERA Networks Ltd. All rights reserved. No part of this document

Genesys Skills Assessor 8.5.4 Installing and Configuring Active Directory Using the Secure Token Service The information contained herein is proprietary and confidential and cannot be disclosed or duplicated

CHAPTER 39 The single sign on feature allows end users to log into a Windows client machine on a Windows domain, then use certain Cisco Unified Communications Manager applications without signing on again.

Software Release 3.1 November 2014 Two-Second Advantage 2 Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE

This chapter provides information about the feature which allows end users to log into a Windows client machine on a Windows domain, then use certain Cisco Unified Communications Manager applications without

User Source and Authentication Reference ZENworks 11 www.novell.com/documentation Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation,

Ubuntu Linux Server & Client and Active Directory 1 Configuration The following process allows you to configure exacqvision permissions and privileges for accounts that exist on an Active Directory server:

User Manual Onsight Management Suite Version 5.1 Another Innovation by Librestream Doc #: 400075-06 May 2012 Information in this document is subject to change without notice. Reproduction in any manner

Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice. Before installing and using the software, please review the readme files,

CHAPTER 4 This chapter describes how Cisco Identity Services Engine (ISE) manages its network identities and access to its resources using role-based access control policies, permissions, and settings.

VMware Identity Manager Administration VMware Identity Manager 2.4 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new

How to Set up Kerberos Summary This guide guide provides the steps required to set up Kerberos Configure the Application Server User Account on the Domain Server The following instructions are based on

Interworks Interworks Cloud Platform Installation Guide Published: March, 2014 This document contains information proprietary to Interworks and its receipt or possession does not convey any rights to reproduce,

WebSpy Vantage Ultimate 2.2 Web Module Administrators Guide This document is intended to help you get started using WebSpy Vantage Ultimate and the Web Module. For more detailed information, please see

Dell KACE K1000 System Management Appliance Version 5.4 Service Desk Administrator Guide October 2012 2004-2012 Dell Inc. All rights reserved. Reproduction of these materials in any manner whatsoever without