WAS v8.5 > Secure applications > Authenticate users > Implement single sign-on to minimize web user authentications > Create a single sign-on for HTTP requests using SPNEGO Web authentication > Step 4. Configure the client application on the client application machine

Configure the client browser to use SPNEGO

We can configure your browser to utilize the Simple and Protected GSS-API Negotiation (SPNEGO) mechanism.

You need to know how to display and set options in the Microsoft Internet Explorer browser or any other browser (such as Firefox). You must have a browser installed that supports SPNEGO authentication.

To ensure that your Microsoft Internet Explorer browser is enabled to perform SPNEGO authentication.

  1. At the desktop, log in to the windows active directory domain.
  2. Activate Internet Explorer.
  3. In the Internet Explorer window, click Tools > Internet Options > Security tab.

  4. Select the Local intranet icon and click Sites.
  5. In the Local intranet window, ensure the "check box" to include all local (intranet) not listed in other zones is selected, then click Advanced.
  6. In the Local intranet window, fill in the Add this web site to the zone field with the web address of the host name so the SSO can be enabled for the list of websites shown in the websites field. Your site information technology staff provides this information. Click OK to complete this step and close the Local intranet window.

  7. On the Internet Options window, click the Advanced tab and scroll to Security settings. Ensure the Enable Integrated Windows Authentication (requires restart) box is selected.

  8. Click OK. Restart your Microsoft Internet Explorer to activate this configuration.

To ensure that your Firefox browser is enabled to perform SPNEGO authentication.

  1. At the desktop, log in to the windows active directory domain.
  2. Activate Firefox.
  3. At the address field, type about:config.
  4. In the Filter, type network.n
  5. Double click on network.negotiate-auth.trusted-uris. This preference lists the sites that are permitted to engage in SPNEGO Authentication with the browser. Enter a comma-delimited list of trusted domains or URLs.

    Set the value for network.negotiate-auth.trusted-uris.

  6. If the deployed SPNEGO solution is using the advanced Kerberos feature of Credential Delegation double click on network.negotiate-auth.delegation-uris. This preference lists the sites for which the browser may delegate user authorization to the server. Enter a comma-delimited list of trusted domains or URLs.

  7. Click OK. The configuration appears as updated.

  8. Restart your Firefox browser to activate this configuration.


Results

Your Internet browser is properly configured for SPNEGO authentication. We can use applications deployed in WebSphere Application Server that use secured resources without being repeatedly requested for a user ID and password.

If we are prompted multiple times for a user ID and password, make sure that you enabled SPNEGO support on your client browser per the instructions above. You must also verify the Allow fall back to application authentication mechanism support option is enabled on the WAS server side.


Related


Create a single sign-on for HTTP requests using SPNEGO Web authentication
Create a Kerberos service principal (SPN) and keytab file on your Microsoft domain controller machine
Create SPNEGO tokens for J2EE, .NET, Java, web service clients for HTTP requests
Create a Kerberos service principal name and keytab file
Add or modifying SPNEGO web authentication filters


Reference:

SPNEGO web authentication configuration commands
SPNEGO web authentication filter commands
SPNEGO web authentication enablement
SPNEGO web authentication filter values


+

Search Tips   |   Advanced Search