Create a single sign-on for HTTP requests using SPNEGO Web authentication

Creating single sign-ons for HTTP requests using the SPNEGO web authentication for WAS allows HTTP users to log in and authenticate to the Microsoft domain controller only once at their desktop, and to receive automatic authentication from the WAS.

• We can configure and enable SPNEGO web authentication and filters on the WAS server side using the administrative console.
• Dynamic reload of SPNEGO is provided without the need to stop and restart the WAS server.
• Fallback to an application login method is provided if the SPNEGO web authentication fails.

We can enable either SPNEGO TAI or SPNEGO Web Authentication but not both.

Read about Single sign-on for HTTP requests using SPNEGO web authentication for a better understanding of what SPNEGO Web Authentication is and how it is supported in this version of WAS.

Before starting this task, complete the following checklist:

• A Microsoft Windows Server running the Active Directory Domain Controller and associated Kerberos Key Distribution Center (KDC).

• A Microsoft Windows domain member (client) for example, a browser or Microsoft .NET client, that supports the SPNEGO authentication mechanism, as defined in IETF RFC 2478. Internet Explorer Version 5.5 or later and Mozilla Firefox Version 1.0 qualify as such clients.

  A running domain controller and at least one client machine in that domain is required. Using SPNEGO directly from the domain controller is not supported.

• The domain member has users who can log on to the domain. Specifically, we need to have a functioning Microsoft Windows active directory domain that includes:
  • Domain controller
  • Client workstation
  • Users who can login to the client workstation

• A server platform with WebSphere Application Server running and application security enabled.

• Users on the active directory must be able to access WebSphere Application Server protected resources using a native WebSphere Application Server authentication mechanism.

• The domain controller and the host of WAS should have the same local time.

• Ensure the clock on clients, Microsoft Active Directory and WebSphere Application Server are synchronized to within five minutes.

• Be aware that client browsers must be SPNEGO enabled, which you perform on the client application machine (with details explained in procedure 4, "Configure the client application on the client application machine").

The objective of this machine arrangement is to permit users to successfully access WebSphere Application Server resources without having to authenticate again and thus achieve Microsoft Windows desktop single sign-on capability.

Configuring the members of this environment to establish Microsoft Windows single sign-on involves specific activities that are performed on three distinct machines:

• A Microsoft Windows server running the Active Directory Domain Controller and associated Kerberos Key Distribution Center (KDC).

• A Microsoft Windows domain member (client application), such as a browser or Microsoft .NET client.

• A server platform with WebSphere Application Server running.

Continue with the following steps to create a single sign-on for HTTP requests using SPNEGO Web authentication:

1. Create a Kerberos service principal (SPN) and keytab file on the Microsoft domain controller machine
2. Create a Kerberos configuration file
3. Configure and enable SPNEGO web authentication using the administrative console on the WAS machine
4. Configure the client application on the client application machine
5. Create SPNEGO tokens for J2EE, .NET, Java, web service clients for HTTP requests (Optional)

Related

1. Configure the client application on the client application machine
2. Create SPNEGO tokens for J2EE, .NET, Java, web service clients for HTTP requests (Optional)
3. Create a Kerberos service principal (SPN) and keytab file on the Microsoft domain controller machine
4. Create a Kerberos configuration file
5. Enable and configure SPNEGO web authentication using the administrative console
6. Configure the client browser to use SPNEGO
7. Create SPNEGO tokens for J2EE, .NET, Java, web service clients for HTTP requests
8. Implement single sign-on to minimize web user authentications
9. Create a Kerberos service principal name and keytab file
10. Create a Kerberos service principal and keytab file used by the WAS SPNEGO TAI (deprecated)
11. SPNEGO web authentication configuration commands
12. SPNEGO web authentication filter commands
13. SPNEGO troubleshooting tips