Problem | Initialization of the SPNEGO Trust Association Interceptor has started. |
User response | None, informational only. |
Problem | A HandshakeFailedException occurred while processing the SPNEGO token received in the HttpServletRequest. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The exception occurred while attempting attempting to execute the negotiateValidateandEstablishTrust() operation. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The Service Provider Name found in the configuration properties has a null value and is invalid. |
User response | Verify and correct the configuration properties. |
Problem | The shown exception occurred when adding the SPNEGO security provider to security configuration. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | Initialization of the SPNEGO Trust Association Interceptor has completed. |
User response | None, informational only. |
Problem | The SPNEGO security provider has been addded to the security configuration. |
User response | None, informational only. |
Problem | The SPNEGO security provider has been removed from the security configuration. |
User response | None, informational only. |
Problem | The configuration properties used to initialize the interceptor are invalid. The error condition that caused the failure is indicated. |
User response | Verify and correct the configuration properties. |
Problem | Use of NT_HOSTBASED_SERVICE name type may cause problems with reverse name lookups. |
User response | None, informational warning only. |
Problem | The SPNEGO token used to authenticate the request is invalid. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | A null string was used as the argument of the init() operation of the HTTPHeaderFilter. |
User response | Correct the filtering rule and restart the application server. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | None, informational only. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | None, informational only. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | None, informational only. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | None, informational only. |
Problem | The initialization state of the SPNEGO Trust Association Interceptor is shown. |
User response | None, informational only. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The error occurred during initialization of the ServerCredential object. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The given spnId value has already been defined in the SPNEGO TAI configuration. |
User response | Verify the SPNEGO TAI properties and specify a value that is not already used; or do not use the spnId option and a value will be automatically selected. |
Problem | The given spnId value is not defined in the SPNEGO TAI configuration. |
User response | Verify the SPNEGO TAI properties and specify a spnId value that exists. |
Problem | No SPNEGO TAI properties are defined in the security configuration for the given spnId. |
User response | Specify each of the SPNEGO TAI properties to be modified. If the selected property is not already defined, it will be defined. |
Problem | The SPNEGO TAI property added to the security configuration and its value are shown. |
User response | None, informational only. |
Problem | The SPNEGO TAI property modified in the security configuration and its current and previous values are shown. |
User response | None, informational only. |
Problem | The SPNEGO TAI property removed from the security configuration is shown. |
User response | None, informational only. |
Problem | All SPNEGO TAI properties have been removed from the security configuration. |
User response | None, informational only. |
Problem | The spnId value must be non-negative. |
User response | Specify a non-negative value for the given spnId. |
Problem | The Kerberos configuration file already exists at the given directory location. |
User response | Specify a different directory location, delete or rename the existing file. |
Problem | The directory path of the Kerberos configuration file does not exist or cannot be written, verify directory exists and is writable. |
User response | Verify that all subdirectories in the specified directory path exist and are writable. |
Problem | The Kerberos configuration file has been successfully created. |
User response | None, informational only. |
Problem | The specified filter rules are invalid. |
User response | Verify the filter rules conform to the syntax supported by the default HTTPHeaderFilter class. |
Problem | A MalformedURLException was encountered parsing one of the specified URLs. |
User response | Verify the URL syntax is correct. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |