private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery
Spnego or Simple and Protected GSSAPI Negotiation Mechanism is a way for users to be seamlessly authenticated when running on a Windows or Active Directory based network. Jetty supports this type of authentication and authorization through the JDK so you must be using a JDK that supports it, which recent versions of Java 6 and 7 do. Also important to note is that this is an incredibly fragile setup where everything needs to be configured just right for things to work, otherwise it can fail in fun and exciting, not to mention obscure ways.
There is a substantial amount of configuration and testing required to enable this feature as well as knowledge and access to central systems on a Windows network such as the Active Domain Controller and the ability to create and maintain service users.
To run with spengo enabled the following command line options are required:
-Djava.security.krb5.conf=/path/to/jetty/etc/krb5.ini \ -Djava.security.auth.login.config=/path/to/jetty/etc/spnego.conf \ -Djavax.security.auth.useSubjectCredsOnly=false
For debugging the spengo authentication the following options are very helpful:
-Dorg.eclipse.jetty.LEVEL=debug \ -Dsun.security.spnego.debug=all
Spengo Authentication must be enabled in the webapp in the following way. The name of the role will be different for your network.
A corresponding UserRealm needs to be created either programmatically if embedded, via the jetty.xml or in a context file for the webapp.
This is what the configuration within a jetty xml file would look like.
This is what the configuration within a context xml file would look like.
There are a number of important configuration files with spnego that are required. The default values for these configuration files from this test example are found in the jetty-distribution.
configures the user realm with runtime properties
configures the underlying kerberos setup
configures the glue between gssapi and kerberos
It is important to note that the keytab file referenced in the krb5.ini and the spengo.conf files needs to contain the keytab for the targetName for the http server. To do this use a process similar to this:
On the windows active domain controller run:
$ setspn -A HTTP/linux.mortbay.org ADUser
To create the keytab file use the following process:
$ ktpass -out c:\dir\krb5.keytab -princ HTTP/linux.mortbay.org@MORTBAY.ORG -mapUser ADUser -mapOp set -pass ADUserPWD -crypto RC4-HMAC-NT -pType KRB5_NT_PRINCIPAL
This step should give you the keytab file which should then be copied over to the machine running this http server and referenced from the configuration files. For our testing we put the keytab into the etc directory of jetty and referenced it from there.
The follows steps have been required to inform Firefox that it should use a negotiation dialog to authenticate.
browse to about:config and agree to the warnings
search through to find the 'network' settings
set network.negotiate-auth.delegation-uris to http://,https://
set network.negotiate-auth.trusted-uris to http://,https://
The follows steps have been required to inform Internet Explorer that it should use a negotiation dialog to authenticate.
Tools -> Options -> Security -> Local Intranet -> Sites (everything should be checked here)
Tools -> Options -> Security -> Local Intranet -> Sites -> Advanced (add url to server (http:// and/or https:// use the hostname!)
Tools -> Options -> Security -> Local Intranet -> Sites -> Advanced -> Close
Tools -> Options -> Security -> Local Intranet -> Sites -> Ok
Tools -> Options -> Advanced -> Security (in the checkbox list)
locate and check 'Enable Integrated Windows Authentication'
Tools -> Options -> Advanced -> Security -> Ok
close IE then reopen and browse to your spengo protected resource
Note: You must go to the hostname and not the IP, if you go to the IP it will default to NTLM authentication...the following conditions must be true for Spnego authentication to work.
You must be within the Intranet Zone of the network
Accessing the server using a Hostname rather then IP
Integrated Windows Authentication in IE is enabled and the host is trusted in Firefox
The server is not local to the browser, it can't be running on localhost.
The client's Kerberos system is authenticated to a domain controller