Hi everybody,
I installed WAS 4.0.3 under Solaris and configure security to enable SSO between WAS and Domino.
I use the Domino LDAP and everything worked fine.
I
test the protected ressources without using Domino as Web server so directly on the 9080 port of WAS.
It's working fine but there's a moment where I get an error about security.
And the only way is to restart the admin server !
I give you the tracefile part where the error is.
If you could help me, it would be very cool.
Thank you.
Here's the tracefile (copy it and paste it in a text file, it looks better) :
[6/21/02 14:38:10:722 WEST] 51be4e SystemOut U 1> [2002-06-21 14:38:10.712], [ServerID: 1917109904], [LoginHelperImpl.request_login_controlled]:
[6/21/02 14:38:10:723 WEST] 51be4e SystemOut U JSAS0240E: Login failed. Verify the userid/password is correct. Check the properties file to ensure the login source is valid. If this error occurs on the server, check the server properties to ensure the principalName has a valid realm and userid.
[6/21/02 14:38:10:725 WEST] 51be4e SystemOut U 2> [2002-06-21 14:38:10.724], [ServerID: 1917109904], [CredentialsImpl.refresh]:
[6/21/02 14:38:10:725 WEST] 51be4e SystemOut U JSAS0240E: Login failed. Verify the userid/password is correct. Check the properties file to ensure the login source is valid. If this error occurs on the server, check the server properties to ensure the principalName has a valid realm and userid.
[6/21/02 14:38:10:731 WEST] 51be4e SystemOut U 4> [2002-06-21 14:38:10.73], [ServerID: 1917109904], [CredentialsImpl.refresh]:
[6/21/02 14:38:10:732 WEST] 51be4e SystemOut U JSAS0240E: Login failed. Verify the userid/password is correct. Check the properties file to ensure the login source is valid. If this error occurs on the server, check the server properties to ensure the principalName has a valid realm and userid.
[6/21/02 14:38:10:733 WEST] 51be4e SystemOut U 5> [2002-06-21 14:38:10.732], [ServerID: 1917109904], [CredentialsImpl.refreshServerCred]:
[6/21/02 14:38:10:733 WEST] 51be4e SystemOut U JSAS0474W: Unable to refresh the server's credentials, reset to minimum expiration time. Restart the server. If the problem persists, contact support for assistance.
[6/21/02 14:40:33:857 WEST] 468e73 SystemOut U 6> [2002-06-21 14:40:33.856], [ServerID: 1917109904], [SecureAssociationInterceptorImpl.handleAssocRejectResponse], Error code = 7:
[6/21/02 14:40:33:858 WEST] 468e73 SystemOut U JSAS0200E: Attempt to establish a secure association at the target server failed. Check your userid/password to verify the correctness. Retry the operation after a few minutes. If the problem persists, contact support for assistance. Authentication failed.
[6/21/02 14:40:33:869 WEST] 468e73 SystemOut U 7> [2002-06-21 14:40:33.869], [ServerID: 1917109904], [SecureAssociationInterceptorImpl.handleAssocRejectResponse], Error code = 7:
[6/21/02 14:40:33:870 WEST] 468e73 SystemOut U JSAS0200E: Attempt to establish a secure association at the target server failed. Check your userid/password to verify the correctness. Retry the operation after a few minutes. If the problem persists, contact support for assistance. Authentication failed.
[6/21/02 14:40:33:871 WEST] 468e73 SystemOut U 8> [2002-06-21 14:40:33.871], [ServerID: 1917109904], [VaultImpl.get_security_context]:
[6/21/02 14:40:33:872 WEST] 468e73 SystemOut U JSAS0170E: Null session handle in session table. Check to see if a server process has terminated just prior to receiving these errors. If a process has terminated, restart the process and retry the operation. Verify that the client userid/password is valid. If the login fails, the session will be deleted on the client side and the credentials will be marked invalid. If a retry occurs, you will likely see this error. Restart the client program after verifying the login info. If the errors persist, contact support for assistance.
[6/21/02 14:40:33:874 WEST] 468e73 SystemOut U 9> [2002-06-21 14:40:33.873], [ServerID: 1917109904], [VaultImpl.init_security_context]:
[6/21/02 14:40:33:885 WEST] 468e73 SystemOut U JSAS0070E: Unable to complete secure association at the client. Retry the client program after a few minutes wait. If the problem still persists, contact support for assistance.
[6/21/02 14:40:33:899 WEST] 468e73 SystemOut U 11> [2002-06-21 14:40:33.898], [ServerID: 1917109904], [SecureAssociationInterceptorImpl.handleAssocRejectResponse], Error code = 7:
[6/21/02 14:40:33:923 WEST] 468e73 SystemOut U JSAS0200E: Attempt to establish a secure association at the target server failed. Check your userid/password to verify the correctness. Retry the operation after a few minutes. If the problem persists, contact support for assistance. Authentication failed.
[6/21/02 14:40:33:926 WEST] 468e73 SystemOut U 12> [2002-06-21 14:40:33.925], [ServerID: 1917109904], [SecureAssociationInterceptorImpl.handleAssocRejectResponse], Error code = 7:
[6/21/02 14:40:33:926 WEST] 468e73 SystemOut U JSAS0200E: Attempt to establish a secure association at the target server failed. Check your userid/password to verify the correctness. Retry the operation after a few minutes. If the problem persists, contact support for assistance. Authentication failed.
[6/21/02 14:40:33:927 WEST] 468e73 SystemOut U 13> [2002-06-21 14:40:33.927], [ServerID: 1917109904], [VaultImpl.get_security_context]:
[6/21/02 14:40:33:928 WEST] 468e73 SystemOut U JSAS0170E: Null session handle in session table. Check to see if a server process has terminated just prior to receiving these errors. If a process has terminated, restart the process and retry the operation. Verify that the client userid/password is valid. If the login fails, the session will be deleted on the client side and the credentials will be marked invalid. If a retry occurs, you will likely see this error. Restart the client program after verifying the login info. If the errors persist, contact support for assistance.
[6/21/02 14:40:33:930 WEST] 468e73 SystemOut U 14> [2002-06-21 14:40:33.929], [ServerID: 1917109904], [VaultImpl.init_security_context]:
[6/21/02 14:40:33:930 WEST] 468e73 SystemOut U JSAS0070E: Unable to complete secure association at the client. Retry the client program after a few minutes wait. If the problem still persists, contact support for assistance.
[6/21/02 14:40:33:946 WEST] 468e73 SystemOut U 16> [2002-06-21 14:40:33.945], [ServerID: 1917109904], [SecureAssociationInterceptorImpl.handleAssocRejectResponse], Error code = 7:
[6/21/02 14:40:33:946 WEST] 468e73 SystemOut U JSAS0200E: Attempt to establish a secure association at the target server failed. Check your userid/password to verify the correctness. Retry the operation after a few minutes. If the problem persists, contact support for assistance. Authentication failed.
[6/21/02 14:40:33:948 WEST] 468e73 SystemOut U 17> [2002-06-21 14:40:33.948], [ServerID: 1917109904], [SecureAssociationInterceptorImpl.handleAssocRejectResponse], Error code = 7:
[6/21/02 14:40:33:949 WEST] 468e73 SystemOut U JSAS0200E: Attempt to establish a secure association at the target server failed. Check your userid/password to verify the correctness. Retry the operation after a few minutes. If the problem persists, contact support for assistance. Authentication failed.
[6/21/02 14:40:33:951 WEST] 468e73 SystemOut U 18> [2002-06-21 14:40:33.949], [ServerID: 1917109904], [VaultImpl.get_security_context]:
[6/21/02 14:40:33:951 WEST] 468e73 SystemOut U JSAS0170E: Null session handle in session table. Check to see if a server process has terminated just prior to receiving these errors. If a process has terminated, restart the process and retry the operation. Verify that the client userid/password is valid. If the login fails, the session will be deleted on the client side and the credentials will be marked invalid. If a retry occurs, you will likely see this error. Restart the client program after verifying the login info. If the errors persist, contact support for assistance.
[6/21/02 14:40:33:953 WEST] 468e73 SystemOut U 19> [2002-06-21 14:40:33.952], [ServerID: 1917109904], [VaultImpl.init_security_context]:
[6/21/02 14:40:33:953 WEST] 468e73 SystemOut U JSAS0070E: Unable to complete secure association at the client. Retry the client program after a few minutes wait. If the problem still persists, contact support for assistance.
[ June 24, 2002: Message edited by: samuel gaiffe ]