Explanation | Parameter passed into the method was null." |
Action | Rerun the command making sure call parameter are supplied. |
Explanation | The specifiect object does not exist within the management scope. |
Action | Rerun the command with a a valid object name. |
Explanation | The specified object already exist. Unable to create another one. |
Action | Create the object with a unique name. |
Explanation | Either a provider/algorithm or a keyManagerClass should be specified not both. |
Action | Rerun the command specifing either a provider/algorithm or a keyManagerClass. |
Explanation | The supplied management scope is not in the correct format or contains invalud information. |
Action | Rerun the command with a good management scope name. |
Explanation | The key store provided is not within the same scope as the key set. |
Action | Rerun the command with a key store that is within the key set's management scope. |
Explanation | The supplied key set object name does not exist. |
Action | Rerun the command with a valid key set object. |
Explanation | The supplied management scope type is not valid. |
Action | Rerun the command with a valid management scope type. Valid types include cell, nodegroup, node, cluster, server, and endpoint. |
Explanation | The supplied managemant scope does not match the management scope type that was specified. |
Action | Rerun the command with correct management scope type for the supplied management scope. |
Explanation | The management scope name supplied already exists in the security configuration. |
Action | Rerun the command with a unique management scope name. |
Explanation | Supplied SSL type is not valid. |
Action | Rerun the command with a valid SSL type. |
Explanation | Supplied SSL security level is not valid. |
Action | Rerun the command with a valid SSL security level. |
Explanation | Supplied SSL protocol is not valid. |
Action | Rerun the command with a valid SSL protocol. |
Explanation | The supplied trust manager object name is not valid. |
Action | Rerun the command with a valid trust manager object name. |
Explanation | The supplied SSL configuration direction is not valid. |
Action | Rerun the command with a valid SSL configuration direction, inbound or outbound. |
Explanation | The SSL configuration group already exists. |
Action | Rerun the command with a unique SSL configuration group name. |
Explanation | The specified SSL Configuration needs to be in he same management scope as the SSL configuration group being created. |
Action | Rerun the command with an SSL configuratin that is in the same management scope ask the SSL configuration group being created. |
Explanation | The specified certificate alias is not found it the SSL configuration. |
Action | Rerun the command with a certificate alias that can be found in the configuration. |
Explanation | The specified key alias already exist in the key set. |
Action | Rerun the command with a key alias that does not already exist in the key set. |
Explanation | The password and verify password supplied do not match. |
Action | Rurun the command again with matching passwords. |
Explanation | The specified key store file already exists |
Action | Rerun the command again specifing a key store file that does not already exists. |
Explanation | The specified object already exists, it can not be created again. |
Action | Rerun the command with a unique name. |
Explanation | The specified frequency is not a positive integer. |
Action | Rerun the command using positive integer for a fequency. |
Explanation | The supplied minute value did not fall within the minute range. |
Action | Rerun the command a minute value between 0 and 59. |
Explanation | The supplied day of week value is out of range. |
Action | Rerun the command with a day of week value between 1 and 7. |
Explanation | The hour value is out of range. |
Action | Rerun the command with a hour value between 0 and 23. |
Explanation | The next start date is set to a date in the past. It needs to be set to a date in the future. |
Action | Rerun the command with a next start date set to a date in the future. |
Explanation | Unable to create a wsCertExpMonitor entry because one already exists. Only one is allowed in the security.xml file at a time. |
Action | Delete the existing wsCertExpMonitor entry and create a new one if a different wsCertExpMonitor is desired. |
Explanation | Valid days parameter is out of range. It should be between 1 and 7300 days. |
Action | Rurun the command with a valid days value between 1 and 7300. |
Explanation | Unable to delete the trust manager because it is still referenced by other objects. |
Action | Make sure the trust manager is not referenced by other objects before deleting it. |
Explanation | Unable to add the certificate to the key store because the key store already contains a certficate with the given alias. |
Action | Rerun the command using a unique alias name for the certificate. |
Explanation | The object is not in the management scope. |
Action | Rerun the command using the correct management scope. |
Explanation | Unable to delete the key set because it is still referenced by other objects. |
Action | Make sure the key set is not referenced by other objects before deleting it. |
Explanation | Unable to generate keys since there is not key generator class configured. |
Action | Configure a key generator class for the key set. |
Explanation | Unable to delete the management scope because it is still referenced by other objects. |
Action | Make sure the management scope is not referenced by other objects before deleting it. |
Explanation | Unable to modify the descriptive property without the object parent information. |
Action | Rerun the command with a parent data type value. |
Explanation | Unable to modify the descriptive property without the class name. |
Action | Rerun the command with a class name value. |
Explanation | Unable to modify the descriptive property without the descriptive property name. |
Action | Rerun the command with a descriptive property name value. |
Explanation | Unable to modify the descriptive property without the descriptive property type. |
Action | Rerun the command with a descriptive property type value. |
Explanation | Information about when the certificate will expire. |
Action | none. |
Explanation | Information that the certificate is replaced. |
Action | none. |
Explanation | Information that the certificate is replaced. |
Action | none. |
Explanation | Information that the certificate is deleted. |
Action | none. |
Explanation | Information that the certificae is deleted. |
Action | none. |
Explanation | Information about certificate expiration. |
Action | none. |
Explanation | Information about action taken during certificate expiration monitoring. |
Action | none. |
Explanation | Unable to perform operation on the specfied alias because it does not exist in the key store. |
Action | Rerun the command using a certficate alias that exists for the key store. |
Explanation | Unable to perform operation on the specfied alias because it is not a certificate request. |
Action | Rerun the command using a certficate request. |
Explanation | Unable to perform operation because the certificate file does not exist. |
Action | Rerun the command using a valid certficate file. |
Explanation | Unable to perform operation because a key for the alias specified does not exist. |
Action | Rerun the command using a certificate alias the contains a key. |
Explanation | Unable to recieve the certficate from the certificate authority because public keys do not match. |
Action | Rerun the command using a certificate retrieved from a certificate authority that was generated with the certificate request coming form this specified alias in this key store. |
Explanation | Unable to recieve the certficate from the certificate authority because public keys do not match. |
Action | Rerun the command using a certificate retrieved from a certificate authority that was generated with the certificate request coming form this specified alias in this key store. |
Explanation | The key store file did not verify. The file may not exist or the key file type or password is not correct. |
Action | Rerun the command with a key store that exists and check the key file type and password. |
Explanation | The SSL Configuration must be within the Dynamic SSL Configuration Selection management scope. |
Action | Rerun the command with a SSL Configuration that is within the same management scope of the Dynamic SSL Configuration Selection management scope. |
Explanation | The key store being created is a hareware key store and a hardware crypto key store type must be specified. |
Action | Rerun the command with a hardware crypto key store type. |
Explanation | Only a positive integer can be used for a hardware slot number. |
Action | Rerun the command using a positive integer for a hardware slot number. |
Explanation | Only a positive number can be used for next start date. |
Action | Rerun the command using a positive number for next state date. |
Explanation | The signer certificate was not retrieved, verify the hostname and port are correct. |
Action | Rerun after verifying the hostname is valid and the port is a secure port. |
Explanation | In order to receive a certificate in a key store the public key of the certificate must match the public key of a certificate in the key store. |
Action | Run the command with a certificate that has a public key that matches the public key of a certificate in the key store. |
Explanation | When creating a key store object with an existing key store file the file must exist and valid passord and key store must be supplied. |
Action | Check the password and key store type for the key store file and rerun the command with the correct values. |
Explanation | When creating a key store used for hardware acceleration the configuration file must exist. |
Action | Make sure the key store acceleration configuration file exists and rerun the command. |
Explanation | When creating a key store that is not file based the file specified must exist. |
Action | Make sure the file specified exists and rerun the command. |
Explanation | The certificte specified is not a personal certificate. |
Action | Rerun the command with a personal certificate alias name. |
Explanation | There is already a property by the specified name in the SSL Configuration. |
Action | Rerun the command with a property that does not already exist in the SSL Configuration. |
Explanation | The value is not the type specified. |
Action | Rerun the command making sure the value matches the type supplied. |
Explanation | Remotely mananged key stores can only be done on a deployment manager. |
Action | Only locally manage key stores on a base application server. |
Explanation | Key stores that are read only or key store that are not file based can not be changed. |
Action | Unable to perform password change operation on read only or not file based key stores. |
Explanation | The key store file did not verify. The file may not exist or the key file type or password is not correct. |
Action | Rerun the command with a key store that exists and check the key file type and password. |
Explanation | The alias is either not in the key store or it is not a personal certificate in the key store. |
Action | Rerun the command with a personal certificate that is located in the key store. |
Explanation | When creating a hardware key store object the file in the path specified should already exist. |
Action | Rerun the command with a specifying a file that already exists. |
Explanation | The two alias values supplied are the same. The need to be different for the command to work. |
Action | Rerun the command with a specifying different alaises. |
Explanation | The value is not a valid configuration object name. |
Action | Rerun the command with a valid configuration object name. |
Explanation | The task is missing a parameter required to execute. |
Action | Rerun the command with the correct parameters and values. |
Explanation | The task is missing parameters required to execute. |
Action | Rerun the command with the correct parameters and values. |
Explanation | Unable to perform operation on the specfied alias because it does not exist in the key store. |
Action | Rerun the command using a certficate alias that exists for the key store. |
Explanation | Information about when the certificate expired. |
Action | none. |
Explanation | Information about when the certificate expired. |
Action | none. |
Explanation | Infomation parameter is not formatted correctly. It need to be in the 'protocol,host,port' format. |
Action | Rerun the command with correct format in the Dynamic SSL configuration selection information parameter. |
Explanation | The specifiect alias does not exist. |
Action | Rerun the command with a a valid alias name. |
Explanation | The time out value range should be between 1 and 86400. |
Action | Rerun the command with a valid range. |