WAS v8.5 > Troubleshoot > Troubleshooting security

Troubleshooting security configurations

The following topics help to troubleshoot specific problems related to configuring and enabling security configurations.

Refer to Security components troubleshooting tips for instructions on how to troubleshoot errors related to security.

Refer to SPNEGO TAI troubleshooting tips for instructions on how to troubleshoot errors related to diagnosing Simple and Protected GSS-API Negotiation (SPNEGO) TAI problems and exceptions.

Deprecated feature:

In WAS v6.1, a TAI that uses the Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) to securely negotiate and authenticate HTTP requests for secured resources was introduced. This function was deprecated in WAS 7.0. SPNEGO web authentication has taken its place to provide dynamic reload of the SPNEGO filters and to enable fallback to the application login method. depfeat

• Errors when configuring or enabling security
  
• Errors after enabling security
  
• Access problems after enabling security
  
• Errors after configuring or enabling Secure Sockets Layer
  
• Errors configuring Secure Sockets Layer encrypted access
  
• Single sign-on configuration troubleshooting tips
  
• Authorization provider troubleshooting tips
  

Subtopics

• Security components troubleshooting tips
  This document explains basic resources and steps for diagnosing security-related issues in WAS.
• Security configuration and enablement errors
  Use this information to troubleshoot problems with configuring or enabling security.
• Security enablement followed by errors
  Use this information if you are experiencing errors after security is enabled.
• Access problems after enabling security
  Use this information if you are experiencing access problems after enabling security.
• SSL errors for security
  You might encounter various problems after configuring or enabling SSL. You may not be able to stop the deployment manager after configuring the SSL. You may not be able to access resource using HTTPS. The client and the server may not be able to negotiate the proper level of security. The problems mentioned here are only a few of the possibilities. Solving these problems is imperative to the successful operation of WAS.
• Errors configuring SSL encrypted access for security
  You might have errors returned when we are trying to configure SSL for encrypted access. This article describes some of the common errors you might encounter and makes suggestions on how to fix the problems.
• Single sign-on configuration troubleshooting tips for security
  Several common problems can occur when we configure SSO between a WAS and a Domino server. Some such problems are: Failure to save the Domino Web SSO configuration, authentication failures when accessing a protected resource, and SSO failures when accessing a protected resource. We can take some actions to correct these error situations and restore the SSO.
• Security authorization provider troubleshooting tips
  This article describes the issues you might encounter using a Java Authorization Contract for Containers (JACC) authorization provider. Tivoli Access Manager is bundled with WAS as an authorization provider. However, you also can plug in our own authorization provider.
• SPNEGO TAI troubleshooting tips (deprecated)
  Presented here is a list of trouble shooting tips useful in diagnosing Simple and Protected GSS-API Negotiation (SPNEGO) TAI problems and exceptions.
• SPNEGO troubleshooting tips
  We can securely negotiate and authenticate HTTP requests for secured resources in WAS using the Simple and Protected GSS-API Negotiation Mechanism (SPNEGO). This article describes the issues you might encounter using Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) as the web authentication service for WAS.
• Security components troubleshooting tips
  This document explains basic resources and steps for diagnosing security-related issues in WAS.
• Security configuration and enablement errors
  Use this information to troubleshoot problems with configuring or enabling security.
• Security enablement followed by errors
  Use this information if you are experiencing errors after security is enabled.
• Access problems after enabling security
  Use this information if you are experiencing access problems after enabling security.
• SSL errors for security
  You might encounter various problems after configuring or enabling SSL. You may not be able to stop the deployment manager after configuring the SSL. You may not be able to access resource using HTTPS. The client and the server may not be able to negotiate the proper level of security. The problems mentioned here are only a few of the possibilities. Solving these problems is imperative to the successful operation of WAS.
• Errors configuring SSL encrypted access for security
  You might have errors returned when we are trying to configure SSL for encrypted access. This article describes some of the common errors you might encounter and makes suggestions on how to fix the problems.
• Single sign-on configuration troubleshooting tips for security
  Several common problems can occur when we configure single sign-on (SSO) between a WAS and a Domino server. Some such problems are: Failure to save the Domino Web SSO configuration, authentication failures when accessing a protected resource, and SSO failures when accessing a protected resource. We can take some actions to correct these error situations and restore the SSO.
• Security authorization provider troubleshooting tips
  This article describes the issues you might encounter using a Java Authorization Contract for Containers (JACC) authorization provider. Tivoli Access Manager is bundled with WAS as an authorization provider. However, you also can plug in our own authorization provider.
• SPNEGO TAI troubleshooting tips (deprecated)
  Presented here is a list of trouble shooting tips useful in diagnosing Simple and Protected GSS-API Negotiation (SPNEGO) TAI problems and exceptions.
• SPNEGO troubleshooting tips
  We can securely negotiate and authenticate HTTP requests for secured resources in WAS using the Simple and Protected GSS-API Negotiation Mechanism (SPNEGO). This article describes the issues you might encounter using Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) as the web authentication service for WAS.

+

Search Tips   |   Advanced Search