JSAS

JSAS0001I: Security configuration initialized.
JSAS0002I: Authentication protocol: {0}
JSAS0003I: Authentication mechanism: {0}
JSAS0004I: Principal name: {0}
JSAS0005I: SecurityCurrent registered.
JSAS0006I: Security connection interceptor initialized.
JSAS0007I: Client request interceptor registered.
JSAS0008I: Server request interceptor registered.
JSAS0009I: IOR interceptor registered.
JSAS0010E: [{0}] Null reference to Vault. Security may be disabled. Exception: {1}.
JSAS0011E: [{0}] Java Exception. Exception = {1}
JSAS0020E: [{0}] Null reference to LoginHelper. The problem may be an out of memory error. Restart the server machine and try again.
JSAS0025E: [{0}] Null reference to ORB. The problem may be an out of memory error. Restart the server machine and try again.
JSAS0026E: [{0}] Exception connecting object to the ORB. Check the SSL configuration to ensure that the SSL keyStore and trustStore properties are set properly. Ensure that the keystore has at least one personal certificate and that the signer for the personal certificate is added to the truststore. Attempt loading the keystore and truststore into WebSphere''s IKeyMan and ensure that the file type specified in the configuration (usually JKS) is the correct file type. Make sure the password specified for the keystore and truststore is valid. Use the same password for both keystore and truststore. {1}
JSAS0027E: [{0}] ORB data conversion exception. This typically occurs when the ORB is processing a data string with characters that are not consistent with the code pages supported by the ORB. Refer to product documentation for additional information. {1}
JSAS0030E: [{0}] Unable to get Current. Check to ensure the correct Java class files are in the program classpath. Make sure you are not using the wrong version of SAS.JAR. {1}
JSAS0040E: [{0}] Unable to initialize security context. Check to ensure the userid/password is valid. Restart the client and retry the operation.
JSAS0051E: [{0}] Invalid authentication target. Verify that the security configuration has a valid authentication target selected.
JSAS0052E: [{0}] Invalid credential token. Retry the operation after a few minutes. If using request_login for Domino, ensure that Domino/WebSphere SSO is setup correctly. {1}
JSAS0053E: [{0}] Unable to validate credential token. Retry the operation after a few minutes. If using request_login for Domino, ensure that Domino/WebSphere SSO is setup correctly.
JSAS0054E: [{0}] Unable to set invocation credentials. Retry the operation. Ensure the program is creating the credential properly before setting it as the invocation credential. You may need to restart the client or server which has the invalid credential. {1}
JSAS0060W: [{0}] Unable to build security context. Occasionally, problems with the client and/or server configuration is responsible for these errors. Often it''s related to SSL connections not being created. This could be due to invalid settings in the security configuration. The SAS.JAR may not be specified in the classpath or is not the same version as the server. The JDK you are using must also have the JSSE extension classes in /java/jre/lib/ext directory. The java.security file must include the IBMJCE provider.
JSAS0070E: [{0}] Unable to complete secure association at the client. Retry the client program after a few minutes wait. {1}
JSAS0071E: [{0}] NO_PERMISSION caught, unable to complete secure association at the client. Retry the client program after a few minutes wait. Ensure that the client program is using the correct version of SAS.JAR in the classpath. {1}
JSAS0100E: [{0}] Null target security name. Verify that the principalName specified in the server configuration is valid.
JSAS0110E: [{0}] Client credentials were not the correct type. Ensure that the client program is correctly following the CORBA programming model. Also, verify that the correct version of SAS.JAR is in the client classpath. {1}
JSAS0120E: [{0}] Unable to create SecurityContext object. Try to review the client security configuration file (sas.client.props). If recent changes have been made you may want to undo these changes. {1}
JSAS0130E: [{0}] Client credentials were not valid. Restart the client so that it logs in with new credentials. Once client credentials are marked invalid, they must be thrown away and news ones created. {1}
JSAS0150E: [{0}] Unable to find session in session table. Retry the operation. If the error repeats itself, restart the client program. Check the client properties to ensure the login information is correct.
JSAS0170E: [{0}] 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.
JSAS0180E: [{0}] Unable to get PrincipalAuthenticator from Current. Check the security configuration to ensure that the authenticationTarget is set properly.
JSAS0185E: [{0}] Validation of BasicAuth Token not supported. Check the client code to ensure it''s not calling validate incorrectly. Resubmit the request after waiting a few minutes.
JSAS0186E: [{0}] Authentication with BasicAuth Token not supported. Check the client code to ensure it''s not calling the wrong principal authenticator. Resubmit the request after waiting a few minutes.
JSAS0190E: [{0}] Invalid or null client security name, unable to authenticate. Verify the information used to login. Retry the operation with a valid userid. If a properties login is performed, check the properties file to ensure a userid has been set.
JSAS0191E: [{0}] Null or empty BasicAuth Token, unable to authenticate. Verify the information used to login. Retry the operation with a valid userid and password. If a properties login is performed, check the properties file to ensure a userid and password has been set.
JSAS0199E: [{0}] Security server could not be initialized. The probable cause for this problem is that the class com.ibm.WebSphereSecurityImpl.SecurityServerImpl cannot be located. This is typically in the wssec.jar file.
JSAS0200E: [{0}] 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. Message={1}, ErrorCode={2}
JSAS0201E: [{0}] Invocation credential realm does not match target''s realm: {0}. If using the SWAM authentication mechanism, you should switch to using LTPA instead for remote IIOP invocations.
JSAS0202E: [{0}] Credential token expired. {1}
JSAS0203E: [{0}] Authentication Failed. Note: The propagation of native registry error information is disabled by default. You may enable it by setting the property "com.ibm.websphere.security.registry.propagateExceptionsToClient=true" from the server''s administrative console by navigating to Security -> Global security -> Custom properties.
JSAS0208E: [{0}] Internal error: system exception.
JSAS0240E: [{0}] 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. {1}
JSAS0241E: [{0}] Attempting to receive LocalOS credential from remote node. LocalOS credentials are only supported on the same node.
JSAS0250E: [{0}] Secure association compromised. Retry the operation. Might want to contact your network administrator to see if any network problems occurred during the time of the errors. Message={1}, ErrorCode={2}.
JSAS0300E: [{0}] Invalid message type returned from target. Retry the operation after a few minutes. If the problem persists, there should be messages on the server system which may give a better indication of what the problem is. Further tracing on the server may be necessary. Message: {1}, ErrorCode: {2}.
JSAS0310E: [{0}] Invalid security attribute type, unable to authenticate. Verify the program to ensure that the attribute being accessed is a valid credential attribute. You may need to contact your system administrator to verify that all of the attributes you need have been set in the user registry. {1}
JSAS0320E: [{0}] Connection type found in session entry was not valid for this security context. Ensure that the security configuration has the SSL keyStore and trustStore properties specified, and that the keystore file has valid, non-expired certificates.
JSAS0340E: [{0}] Invalid communication direction for security feature. Ensure the call to get_security_features passes in org.omg.Security.CommunicationDirection._SecDirectionBoth.
JSAS0350E: [{0}] Security attribute type is null or invalid. Verify the program to ensure that the attribute being accessed is a valid credential attribute. You may need to contact your system administrator to verify that all of the attributes you need have been set in the user registry. {1}
JSAS0355E: [{0}] Duplicate security attribute type specified. Verify the program to ensure that the same attribute is not trying to be retrieved more than once at the same time. {1}
JSAS0360E: [{0}] Security attribute list is null. Verify that the list of attributes that is trying to be set is not null. Retry the operation.
JSAS0370E: [{0}] Security attribute list contains null attribute type or attribute family. Verify that the list of attributes that is trying to be set does not contain a null attribute. Retry the operation.
JSAS0380E: [{0}] Security attribute list contains null member. Verify that the list of attributes that is trying to be set does not contain a null attribute. Retry the operation.
JSAS0400E: [{0}] Could not close the key file; processing will continue.
JSAS0402E: [{0}] The standardClaimQOPModels attribute contains an invalid option; using the default value: {1}. Correct the value specified on the standardClaimQOPModels property if you do not want to use Confidentiality.
JSAS0403E: [{0}] The delegateCredentials property contains an illegal delegation mode. Correct the value specified on the delegateCredentials property. The default is None.
JSAS0404E: [{0}] The loginTimeout property is out of range. Correct the value so that it falls between 0 and 600 specified in seconds. Currently using the value: {1}
JSAS0405E: [{0}] The property contains a non-integer string value; defaulting to {1}. Correct the value specified in the property so that it is an integer number.
JSAS0406E: [{0}] The standardPerformQOPModels attribute contains an invalid option; defaulting to {1}. Correct the value specified on the standardPerformQOPModels property if you do not want to use Confidentiality.
JSAS0408E: [{0}] The SSLCredentialsTimeout property is out of range; using the default value of {1}. Correct the value specified in the property so that it is in the valid range.
JSAS0409E: [{0}] The SSLCredentialsTimeout property contains a non-integer string value; using the default value of {1}. Correct the value specified in the property so that it is an integer number.
JSAS0410E: [{0}] The SSLPort property contains a non-integer string value; using the default value of {1}. Correct the value specified in the property so that it is an integer number.
JSAS0411E: [{0}] The SSLV3SessionTimeout property is out of range; using default value of {1}. Correct the value specified so that it is within the valid range.
JSAS0412E: [{0}] The SSLV3SessionTimeout property contains a non-integer string value; using default value of {1}. Correct the value specified in the property so that it is an integer number.
JSAS0413E: [{0}] A problem occurred while processing the security configuration. Verify the data entered in the security configuration is valid. {1}
JSAS0414E: [{0}] The configuration is incorrect; the server may not start or may not function correctly. If you get this error, other errors will have preceded it which describe the problems with the configuration.
JSAS0415E: [{0}] The configuration is incorrect. If you get this error, other errors will have preceded it which describe the problems with the configuration.
JSAS0416E: [{0}] The configuration is in an unknown state. If you get this error, other errors will have preceded it which describe the problems with the configuration.
JSAS0417E: [{0}] The active correctness verification produced a verification result of {1}
JSAS0418E: [{0}] The configuration has not been initialized. Ensure that the security configuration is complete and in the location specified by the com.ibm.CORBA.ConfigURL. This location is typically WASROOT/properties.
JSAS0420E: [{0}] None of the association options have been set. Ensure that at least one of these association options are set.
JSAS0422E: [{0}] The configuration is incomplete. A preceding message will likely tell you the exact reason why it is incomplete. The likely reasons are no Bootstrap Repository location, no association options selected, or the configuration has not been initialized.
JSAS0423E: [{0}] The completeness verification produced a verification result of {1}.
JSAS0424E: [{0}] The login source is Properties, however either the userid or password were not specified. Specify a userid on com.ibm.CORBA.loginUserid and password on com.ibm.CORBA.loginPassword if you intend to use the login source of properties.
JSAS0425E: [{0}] The login source is KeyTable, however the KeyTable file was not specified. Specify a KeyTable file on com.ibm.CORBA.keytabFileName if you intend to use the login source of KeyTable.
JSAS0427E: [{0}] The specified perform-QOP options are not valid. Verify that the above properties are consistent.
JSAS0428E: [{0}] The specified claim-QOP options are not valid. Verify that the above properties are consistent.
JSAS0429E: [{0}] The configuration is inconsistent. The exact reason of the inconsistency will be in a preceding message.
JSAS0430E: [{0}] The consistency verification produced a verification result of {1}
JSAS0431E: [{0}] The passive correctness verification produced a verification result of {1}
JSAS0433E: [{0}] The performClientAuthentication is set, but none of the server association options are set. Ensure that at least one of the server association properties are set to true.
JSAS0435E: [{0}] Credentials are invalid. Login again to get new credentials. Sometimes it is necessary to restart the client and/or server to ensure that you are using new credentials. Once credentials are marked invalid, they cannot become valid again. {1}
JSAS0436E: [{0}] The configuration is ambiguous about which security mechanism to use. Try to review the client or server security configuration files. If recent changes have been made you may want to undo these changes. {1}
JSAS0437E: [{0}] The DCE tagged component was not correctly formed and can not be parsed. Ensure that the server version you are trying to connect to is supported. Make sure the SAS.JAR you are using on the client side is compatible with that of the server.
JSAS0438E: [{0}] Invalid initial reference name. Verify that security is enabled in the client/server configuration (com.ibm.CORBA.securityEnabled=true). Check the client program to ensure that a valid name is passed into "resolve_initial_references". {1}
JSAS0439E: [{0}] Unable to get Credentials. Verify that the client set the credentials properly before invoking the request. Ensure that the correct userid/password was specified when logging in. {1}
JSAS0441E: [{0}] ASSOC_ACCEPT message is illegal at the target. Retry the operation after a few minutes. Check the client configuration to ensure there''s nothing out of the ordinary that might be causing an exception to occur.
JSAS0442E: [{0}] ASSOC_REJECT message is illegal at the target. Retry the operation after a few minutes. Check the client configuration to ensure there''s nothing out of the ordinary that might be causing an exception to occur.
JSAS0443E: [{0}] Request holder service data key for Security Context invalid. Ensure that the correct SAS.JAR is in the server and client classpath. There might be a mismatch between these files on the client and the server. {1}
JSAS0445E: [{0}] Unknown host. An attempt will be made to use the host name, however, if this fails you''ll need to take action. Contact your network administrator to ensure that the hostname and IP address which you have configured on the server is valid. {1}
JSAS0446E: [{0}] The listening port has not been initialized yet. Check the configuration to ensure there is not a property which inadvertently sets the port to something already using it. Stop the server and wait for about 2 minutes before restarting the server so that all ports that were in use will be released.
JSAS0447E: [{0}] The security tagged component assistor is not an ObjectImpl and therefore can not be registered with the ORB. Check to ensure you have the same version of SAS.JAR as the server. Check the dates of the file on the server to ensure they match the dates of other JAR files on the server in case a mismatch has occurred.
JSAS0449E: [{0}] The SSL tagged component was not correctly formed and can not be parsed. Ensure that the server version you are trying to connect to is supported. Make sure the SAS.JAR you are using on the client side is compatible with that of the server. {1}
JSAS0450E: [{0}] Failed to initialize security context. Have the client verify that the userid/password specified during login is valid. {1}
JSAS0451E: [{0}] Credentials do not contain a Public security name. The client should specify a userid and password in most cases in order to get authenticated.
JSAS0452E: [{0}] The security context is no longer valid. Try to review the client or server security configuration files. If recent changes have been made you may want to undo these changes. {1}
JSAS0453E: [{0}] No credentials could be found identifying the local target. Check the com.ibm.CORBA.PrincipalName, com.ibm.CORBA.LoginUserid, and com.ibm.CORBA.LoginPassword properties to ensure they are valid. For the com.ibm.CORBA.PrincipalName, ensure the correct realm is specified in front of the userid (realm/userid).
JSAS0454E: [{0}] Could not create local credentials. Check the security configuration for com.ibm.CORBA.PrincipalName, com.ibm.CORBA.LoginUserid, and com.ibm.CORBA.LoginPassword properties to ensure they are valid. For the com.ibm.CORBA.PrincipalName, ensure the correct realm is specified in front of the userid (realm/userid). {1}
JSAS0455E: ERROR in {0}: The certificate with alias {1} from keyStore {2} is expired.
JSAS0456W: WARNING in {0}: The certificate with alias {1} from keyStore {2} will be expired in {3} days.
JSAS0461E: [{0}] Invalid credential token, unable to validate. Retry the operation after a few minutes. If using request_login for Domino, ensure that Domino/WebSphere SSO is setup correctly.
JSAS0462E: [{0}] I/O Error trying to open the security bootstrap repository. Check the property bootstrapRepositoryLocation in the security configuration to be sure it points to a valid filename and location. If the path is correct, rename the file to allow it to recreate a new file. {1}
JSAS0463E: [{0}] I/O Error while processing the security bootstrap repository. Stop the adminserver, rename this file to anything else, restart your adminserver and the file should get recreated. Try running "java com.ibm.ISecurityUtilityImpl.BootstrapRepository %WAS_ROOT%/etc/secbootstrap" to see if it can be read. Make sure %WAS_ROOT% points to the correct WebSphere install path. /WebSphere/AppServer. {1}
JSAS0464E: [{0}] I/O Error while writing the security bootstrap repository. Stop the adminserver, rename this file to anything else, restart your adminserver and the file should get recreated. Try running "java com.ibm.ISecurityUtilityImpl.BootstrapRepository %WAS_ROOT%/etc/secbootstrap" to see if it can be read. Make sure %WAS_ROOT% points to the correct WebSphere install path. {1}
JSAS0465E: [{0}] THE SECURITY SERVICE HAS ALREADY BEEN INITIALIZED WITH THIS ORB. The ServiceInit (the call that enables security) will return immediately without reinitializing security multiple times.
JSAS0466E: [{0}] An I/O error occurred while processing the message buffer. Retry the operation. {1}
JSAS0467E: [{0}] The host address in the IOR is null or blank. Make sure the version of SAS.JAR is valid for the WebSphere release you are running. Restart the server and try the operation again.
JSAS0469E: [{0}] The IOR is not correctly formed -- the connection will be refused. Ensure that the client version you are using is supported by the server. Check the SAS.JAR date and size and verify it is the same as that of the server. Check the classpath to ensure it includes the correct version of SAS.JAR.
JSAS0471E: [{0}] The requestCredsExpiration property is out of range; using the default {1}. Correct the value specified in the requestCredsExpiration property so that it is within the valid range.
JSAS0472E: [{0}] The BasicAuth expiration time is smaller than the ORB request timeout; A method request could take longer than the period over which the requesting credentials will remain valid. If you are setting these properties explicitly, ensure that requestTimeout is smaller than requestCredsExpiration.
JSAS0473E: [{0}] Invalid mechanism type. Check the security configuration to ensure the properties are set correctly. Retry the operation.
JSAS0475E: [{0}] Invalid expiry time. Check to ensure the value passed into is_valid is not negative.
JSAS0476E: [{0}] Invalid credential type. Ensure that the client authentication target in the client properties is set to a value that the server supports. {1}
JSAS0477E: [{0}] Invalid credential. Retry the operation. Ensure the program is creating the credential properly before setting it as the invocation credential. You may need to restart the client or server which has the invalid credential. {1}
JSAS0479E: [{0}] Unable to sleep. Restart the server. {1}
JSAS0480E: [{0}] Failed to find the correct entry in key file. Ensure that the property com.ibm.ssl.keyStoreFile is pointing to a keyfile which contains the realm and security name which you are looking for. {1}
JSAS0484E: [{0}] A problem occurred while decoding the loginPassword property. Retype the password on the loginPassword property and restart the program. {1}
JSAS0485E: [{0}] A problem occurred while decoding the keystore password property. Retype the password on the keystore password property and restart the program. {1}
JSAS0486E: [{0}] A problem occurred while decoding the truststore password property. Retype the password on the trustword password property and restart the program. {1}
JSAS0488E: [{0}] An exception was thrown while registering the request interceptor to the orb. The exception is: {1}
JSAS0489E: [{0}] Unauthenticated credentials can not be sent via Identity Assertion because they are not supported by the configuration.
JSAS0490E: [{0}] Identity type stored in the credential (Client Authentication Token) does not match the effective policy Identity type (ITTPrincipalName not supported).
JSAS0491E: [{0}] Identity type stored in the credential (Client certificates) does not match the effective policy Identity type (ITTX509CertChain not supported).
JSAS0492E: [{0}] Identity type stored in the credential (ITTPrincipalName) does not match the effective policy Identity type (ITTPrincipalName not supported).
JSAS0493E: [{0}] Identity type stored in the credential (ITTDistinguishedName) does not match the effective policy Identity type (ITTDistinguishedName not supported).
JSAS0494E: [{0}] The server''s {1} credentials are NULL.
JSAS0495E: [{0}] The server''s {1} credentials are invalid. Realm/security_name == NULL.
JSAS0496E: [{0}] The expiration time for {1} credentials is too short relative to the ORB request timeout and/or the security cache timeout; a method request could take longer than the period over which the credentials will remain valid, or the credentials could expire while in the server cache.
JSAS0497E: [{0}] A problem occurred while decoding the HardwareTokenPassword property. {1}
JSAS0498E: [{0}] The loginSource property contains an illegal option; the default is {1}.
JSAS0499E: The server ID that is received for identity assertion ({0}) does not match any of the configured and trusted server IDs ({1}).
JSAS0500I: CSIv2 protocol has been enabled.
JSAS0501I: Realm name has been set: {1}
JSAS0502I: Realm name has not been set.
JSAS0503I: Claim stateful has been enabled.
JSAS0504I: Claim stateless has been enabled.
JSAS0505I: Claim secure transport layer with SSL/TLS required has been set. <claimTransportAssocSSLTLSRequired>: {1}
JSAS0506I: Claim secure transport layer with SSL/TLS supported has been set. <claimTransportAssocSSLTLSSupported>: {1}
JSAS0507I: No claim secure transport layer has been set.
JSAS0508I: Claim client authentication at transport layer required has been set. <claimTLClientAuthenticationRequired>: {1}
JSAS0509I: Claim client authentication at transport layer supported has been set. <claimTLClientAuthenticationSupported>: {1}
JSAS0510I: No claim client authentication at transport layer has been set.
JSAS0511I: Claim message 128-bit SSL/TLS cipher suites required has been set. <claimMessageConfidentialityRequired>: {1}
JSAS0512I: Claim message 128-bit SSL/TLS cipher suites supported has been set. <claimMessageConfidentialitySupported>: {1}
JSAS0513I: No claim message 128-bit SSL/TLS cipher suites has been set.
JSAS0514I: Claim message 40-bit SSL/TLS cipher suites required has been set. <claimMessageIntegrityRequired>: {1}
JSAS0515I: Claim message 40-bit SSL/TLS cipher suites supported has been set. <claimMessageIntegritySupported>: {1}
JSAS0516I: No claim message 40-bit SSL/TLS cipher suites has been set.
JSAS0517I: Claim client authentication required has been set. <claimClientAuthenticationRequired>: {1}
JSAS0518I: Claim client authentication supported has been set. <claimClientAuthenticationSupported>: {1}
JSAS0519I: No claim client authentication has been set.
JSAS0520I: Claim identity assertion supported has been set. <claimIdentityAssertionSupported>: {1}
JSAS0521I: No claim identity assertion has been set.
JSAS0522I: Perform stateful has been enabled.
JSAS0523I: Perform stateless has been enabled.
JSAS0524I: Perform secure transport layer with SSL/TLS required has been set. <performTransportAssocSSLTLSRequired>: {1}
JSAS0525I: Perform secure transport layer with SSL/TLS supported has been set. <performTransportAssocSSLTLSRequired>: {1}
JSAS0526I: No perform secure transport layer has been set.
JSAS0527I: Perform client authentication at transport layer required has been set. <performTLClientAuthenticationRequired>: {1}
JSAS0528I: Perform client authentication at transport layer supported has been set. <performTLClientAuthenticationSupported>: {1}
JSAS0529I: No perform client authentication at transport layer has been set.
JSAS0530I: Perform message 128-bit SSL/TLS cipher suites required has been set. <performMessageConfidentialityRequired>: {1}
JSAS0531I: Perform message 128-bit SSL/TLS cipher suites supported has been set. <performMessageConfidentialitySupported>: {1}
JSAS0532I: No perform message 128-bit SSL/TLS cipher suites has been set.
JSAS0533I: Perform message 40-bit SSL/TLS cipher suites required has been set. <performMessageIntegrityRequired>: {1}
JSAS0534I: Perform message 40-bit SSL/TLS cipher suites supported has been set. <performMessageIntegritySupported>: {1}
JSAS0535I: No perform message 40-bit SSL/TLS cipher suites has been set.
JSAS0536I: Perform client authentication required has been set. <performClientAuthenticationRequired>: {1}
JSAS0537I: Perform client authentication supported has been set. <performClientAuthenticationSupported>: {1}
JSAS0538I: No perform client authentication has been set.
JSAS0539I: Perform identity assertion supported has been set. <performIdentityAssertionSupported>: {1}
JSAS0540I: No perform identity assertion has been set.
JSAS0541I: Trusted principal list should be defined for Identity Assertion. <claimIdentityAssertion>: {1}. TrustedPrincipalList is not defined.
JSAS0542I: Claim transport security mechanism should be defined when claim transport client auth is enabled. <claimTLClientAuthenticationRequired>: {1}, <claimTLClientAuthenticationSupported>: {2}, <claimTransportAssocSSLTLSRequired>: {3}, <claimTransportAssocSSLTLSSupported>: {4}
JSAS0543I: Claim transport security mechanism should be defined when claim transport QOP is enabled. <claimTransportAssocSSLTLSRequired>: {1}, <claimTransportAssocSSLTLSSupported>: {2}, <claimMessageConfidentialityRequired>: {3}, <claimMessageConfidentialitySupported>: {4}, <claimMessageIntegrityRequired>: {5}, <claimMessageIntegritySupported>: {6}.
JSAS0544I: <claimIdentityAssertionSupported> is not applicable in client configuration. Disabled the property.
JSAS0545I: <performIdentityAssertionSupported> is not applicable in client configuration. Disabled the property.
JSAS0546I: <performIdentityAssertionRequired> is not applicable in client configuration. Disabled the property.
JSAS0547I: Perform transport security mechanism should be defined when perform transport client auth is enabled. <performTLClientAuthenticationRequired>: {1}, <performTLClientAuthenticationSupported>: {2}, <performTransportAssocSSLTLSRequired>: {3}, <performTransportAssocSSLTLSSupported>: {4}.
JSAS0548I: Perform transport security mechanism should be defined when perform transport QOP is enabled. <performTransportAssocSSLTLSRequired>: {1}, <performTransportAssocSSLTLSSupported>: {2}, <performMessageConfidentialityRequired>: {3}, <performMessageConfidentialitySupported>: {4}, <performMessageIntegrityRequired>: {5}, <performMessageIntegritySupported>: {6}
JSAS0549I: Coalescing client config with server security mechanism
JSAS0550I: Evaluation of the transport layer failed.
JSAS0551I: Evaluation of the message layer failed.
JSAS0552I: Evaluation of the identity assertion layer failed.
JSAS0600E: CSIv2 Tagged Component is NULL.
JSAS0601E: The CSIv2 client configuration does not support SECIOP.
JSAS0602E: No valid transport tagged components exist in the IOR.
JSAS0603E: The server does not support SSL/TLS, but the client is configured to require it.
JSAS0604E: The client requires SSL client certificate authentication but the server does not support it.
JSAS0605E: The client supports SSL client certificate authentication but the server does not support it.
JSAS0606E: The server requires SSL client certificate authentication but the client does not support it.
JSAS0607E: The client requires SSL Confidentiality but the server does not support it.
JSAS0608E: The server requires SSL Confidentiality but the client does not support it.
JSAS0609E: The client requires SSL Integrity but the server does not support it.
JSAS0610E: The server requires SSL Integrity but the client does not support it.
JSAS0611E: No authentication mechanism is defined at client authentication layer.
JSAS0612E: The client requires client authentication (e.g., userid/password or token), but the server does not support it.
JSAS0613E: The server requires client authentication (e.g., userid/password or token), but the client does not support it.
JSAS0614E: The authentication mechanism OID supplied by the server is an unsupported OID for this WebSphere release.
JSAS0615E: The client configuration specifies the Kerberos authentication mechanism, but the server does not support it.
JSAS0616E: The client configuration specifies the LTPA authentication mechanism, but the server does not support it.
JSAS0617E: The client configuration specifies the Custom authentication mechanism, but the server does not support it.
JSAS0618E: The target security name is NULL in CSIv2 tagged component.
JSAS0619E: The sending server requires Identity Assertion but the receiving server does not support it.
JSAS0620E: No supported naming mechanisms are defined in attribute layer for Identity Assertion.
JSAS0621E: The target server does not support any identity token types.
JSAS0622E: [{0}] GSSEncodeDecodeException has occurred: {1}
JSAS0623E: [{0}] The verificationLevel property contains an illegal option; the default is {1}.
JSAS0624E: [{0}] Exception caught when instantiating Custom authentication mechanism instance {1}, message: {2}, exception: {3}
JSAS0625E: [{0}] Cannot instantiate WSSecurityContext instance for OID: {1}
JSAS0626E: [{0}] OID verification failed: credential OID ({1}) != configured OID ({2}).
JSAS0627E: [{0}] The com.ibm.CSI.protocol property has an invalid value: {1}. Setting the protocol to {2}.
JSAS0628E: [{0}] The authenticationRetryCount property contains a non-integer string value; the default is {1}.
JSAS0629E: [{0}] MalformedURLException reading com.ibm.CORBA.ConfigURL={1}. Exception: {2}
JSAS0630E: [{0}] IOException reading com.ibm.CORBA.ConfigURL={1}. Exception: {2}
JSAS0631E: [{0}] Exception reading com.ibm.CORBA.ConfigURL={1}. Exception: {2}
JSAS0632E: [{0}] PrivilegedActionException reading com.ibm.CORBA.ConfigURL={1}. Exception: {2}
JSAS0633E: [{0}] NoSuchAlgorithmException - This exception is thrown when a particular cryptographic algorithm is requested but is not available in the environment. Exception: {1}
JSAS0634E: [{0}] KeyStoreException - This is the generic KeyStore exception. Exception: {1}
JSAS0635E: [{0}] UnrecoverableKeyException - This exception is thrown if a key in the keystore cannot be recovered. Exception: {1}
JSAS0636E: [{0}] NoSuchProviderException - This exception is thrown when a particular security provider is requested but is not available in the environment. Exception: {1}
JSAS0637E: [{0}] KeyManagementException - This is the general key management exception, for all operations dealing with key management. Subclasses could include: KeyIDConflict, KeyAuthorizationFailureException, ExpiredKeyException. Exception: {1}
JSAS0638E: [{0}] Client authentication required at the server but no principal information is present in the {1} method request from client {2}.
JSAS0639E: The ID received for identity assertion ({0}) is not trusted by the server, most likely because the ID does not have CONTROL access to the CBIND profile in the RACF (Resource Access Control Facility) database.
JSAS0801E: The received admin RSA token has an expired timestamp of {0} where the current local timestamp is {1}. Check for clock skew issues between servers.
JSAS0802E: The received admin RSA token has a nonce value that has been used recently in this process. This could indicate a replay attack."
JSAS0803E: The received admin RSA token failed validation. The exception message is: {0}
JSAS0804E: An error occurred trying to create an admin RSA token using target certificate with distinguished name of {0}. The exception message is: {1}.
JSAS0805W: The current OID is not the preferred admin authentication mechanism of RSAToken.
JSAS0806W: The current OID is not the preferred admin authentication mechanism of LTPA.
JSAS0807W: The current OID is not the preferred admin authentication mechanism of KRB5.
JSAS0808E: The preferred admin authentication mechanism is not a known ADMIN mechanism.
JSAS0809E: The current OID is RSA but this is not an Admin request.
JSAS1400I: The configuration appears to be actively correct.
JSAS1401I: The configuration has been initialized.
JSAS1402I: Security has been enabled.
JSAS1404I: The login source has been set:
JSAS1405I: The login userid has been set:
JSAS1406I: The login password has been set:
JSAS1407I: The keytab file name has been set:
JSAS1408I: The key file name has been set:
JSAS1409I: The principal has been set: {1}
JSAS1410I: The principal was not set:
JSAS1411I: DCE client-association has been enabled.
JSAS1412I: DCE server-association has been enabled.
JSAS1413I: SSL Type-I client-association has been enabled.
JSAS1414I: SSL Type-I server-association has been enabled.
JSAS1415I: LTPA client-association has been enabled.
JSAS1416I: LTPA server-association has been enabled.
JSAS1417I: Local operating system client-association has been enabled.
JSAS1418I: Local operating system server-association has been enabled.
JSAS1419I: The authentication target has been set:
JSAS1422I: The SSL session timeout has been set:
JSAS1423I: The SSL credentials timeout has been set:
JSAS1425I: The SSL port has been set:
JSAS1426I: The standard perform-QOP model has been set:
JSAS1427I: The perform client-authentication has been set:
JSAS1428I: The perform server-authentication has been set:
JSAS1429I: The perform message replay detection has been set:
JSAS1430I: The perform message out-of-sequence detection has been set:
JSAS1431I: The perform message integrity has been set:
JSAS1432I: The perform message confidentiality has been set:
JSAS1433I: The standard claim-QOP model has been set:
JSAS1434I: The claim client-authentication required has been set:
JSAS1435I: The claim server-authentication required has been set:
JSAS1436I: The claim message replay detection required has been set:
JSAS1437I: The claim message out-of-sequence detection required has been set:
JSAS1438I: The claim message integrity required has been set:
JSAS1439I: The claim message confidentiality required has been set:
JSAS1440I: The claim client-authentication supported has been set:
JSAS1441I: The claim server-authentication supported has been set:
JSAS1442I: The claim message replay detection supported has been set:
JSAS1443I: The claim message out-of-sequence supported has been set:
JSAS1444I: The claim message integrity supported has been set:
JSAS1445I: The claim message confidentiality supported has been set:
JSAS1446I: The delegation mode has been set:
JSAS1447I: The security service will not be disabled during bootstrap activation.
JSAS1448I: The security bootstrap repository port has been set:
JSAS1449I: The configuration appears to be complete.
JSAS1450I: The configuration appears to be consistent.
JSAS1451I: The configuration appears to be passively correct.
JSAS1452I: The SSL server keystore has been set:
JSAS1453I: The SSL server keystore password has been set:
JSAS1454I: The indicated entry was not found in the key file.
JSAS1455I: Unable to login principal: null authentication information.
JSAS1456I: Trying again to form a secure association with the target.
JSAS1457I: [{0}] We couldn''t close the security bootstrap repository. {1}
JSAS1458I: BasicAuth credentials will not expire.
JSAS1459I: The BasicAuth credentials expiration has been set:
JSAS1460I: Successfully loaded configured key file:
JSAS1461I: SSL security compound tag will be exported.
JSAS1474W: [{0}] Unable to refresh the server''s credentials, reset to minimum expiration time. Restart the server.
JSAS1475W: [{0}] The following exception occurred on the server, sending context error back to client: {1}
JSAS1476W: [{0}] The following exception was received from the server: {1}
JSAS1477W: SECURITY CLIENT/SERVER CONFIG MISMATCH: The client security configuration (sas.client.props or outbound settings in GUI) does not support the server security configuration for the following reasons:
JSAS1478W: Security cannot be enabled because the ConfigURL property cannot be processed!
JSAS1479W: The target realm [{0}] does not match the current realm [{1}]. Specify the target realm in the Trusted target realms field. From the AdminConsole, go to: Security -> Global Security -> RMI/IIOP security -> CSIv2 Outbound Authentication.
JSAS1480I: Security is not enabled because the ConfigURL property file is not set.
JSAS1500E: [{0}] AuditEventFactory initialization failed.
JSAS1501E: [{0}] J2EEAuditEventFactory was not initialized.
JSAS1502E: Auditing is enabled but could not get a handle to the audit context objects.
JSAS1503E: AuditServiceProvider failure logging audit event, Exception = {0}.
JSAS1504E: The server does not support the client authentication mechanism: {0}
JSAS1505E: LTPA WSCredential can not go outbound with Kerberos authentication.
JSAS1506E: Kerberos WSCredential without GSSCredential can not go outbound with Kerberos authentication.
JSAS2020W: [{0}] Unable to get credentials. Verify the userid/password supplied is correct. Try restarting the client program to resolve the problem. Increasing the credential timeout value could reduce the likelihood of this error occurring.
JSAS2030W: [{0}] Trying unauthenticated login. Verify the userid/password supplied is correct. Try restarting the client program to resolve the problem. Increasing the credential timeout value could reduce the likelihood of this error occurring.
JSAS2040W: [{0}] No ConnectionData object attached to RequestHolder. Verify the classpath on the client and server both contain the same SAS.JAR and the same SAS e-fixes.
JSAS2070W: [{0}] Session entry already exists. Try to login again.
JSAS2100W: [{0}] Null Credentials list. If an unauthenticated request is not desired, check the client login userid/password to verify correctness. Review the login source property in the sas.client.props.
JSAS2120W: [{0}] Security enabled, but EstablishTrustInClient is not set in IOR. If mutual authentication is desired, check the standardPerformQOPModels property so that it is set to authenticity, integrity, or confidentiality.
JSAS2403W: [{0}] DCE Security Tag not found in IOR. Verify that the client program is attempting the access the correct object. This message could be benign if the object method does not require security to be invoked.
JSAS2404W: [{0}] SSL Security Tag not found in IOR. Verify that the client program is attempting the access the correct object. This message could be benign if the object method does not require security to be invoked.
JSAS2405W: [{0}] Unable to get client security name from credentials. Restart the client so that new credentials will be created. Check with your user registry administrator to ensure the user data is valid.
JSAS2406W: [{0}] SSL Security Compound Tag not found in IOR. Verify that the client program is attempting the access the correct object. This message could be benign if the object method does not require security to be invoked.


Terms and conditions for information centers | Feedback

Last updated: November 13, 2013 05:41 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ISecurityL13SupportImpl.sec.dita
File name: com.ibm.ISecurityL13SupportImpl.sec.html