Explanation | The entity type must be defined with an entity type name and at least one corresponding Relative Distinguished Name (RDN) property. |
Action | Modify and correct the entity type definition in the server.xml file. |
Explanation | The specified definition of the base entry is incorrect. The syntax for defining a base entry is <baseEntry name="..." baseDN="...."/>. |
Action | Modify and correct the base entry definition in the server.xml file. |
Explanation | The realm tag is missing, or is invalid because of a missing required attribute. |
Action | Modify and correct the realm definition in the server.xml file. |
Explanation | The specified definition of the participating base entry is incorrect. The syntax for defining a participating base entry is <participatingBaseEntry name="..."/>. |
Action | Modify and correct the participating base entry definition in the server.xml file. |
Explanation | The mapping definition of the user registry attribute is defined incorrectly. |
Action | Modify and correct the mapping definition of the user registry attribute in the server.xml file. |
Explanation | The specified realm name is not defined or is incorrect in the server.xml file. |
Action | Ensure that the realm name exists and it is spelt correctly in the server.xml file. If it does not exist, a valid realm must be specified. |
Explanation | At least one valid participating base entry must be defined for a realm. |
Action | Ensure that a valid participating base entry is defined for the realm in the server.xml file. |
Explanation | After adding a repository, at least one base entry must be added to it. |
Action | Add at least one base entry to the repository in the server.xml file. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | An operation has been requested on an entity, but that operation does not support the specified entity type. |
Action | Ensure that the entities provided in the input are of supported entity types, and remove any unsupported entity types from the input. |
Explanation | The operation cannot be performed because the specified entity is not in the scope of the realm. |
Action | Ensure that the unique name of the entity is specified correctly. If a realm name is specified in the Context object of the input object, ensure that the name is spelt correctly. |
Explanation | The operation could not be performed because the default parent for this entity type could not be determined. |
Action | Ensure that the default parent for the entity type is configured for the federated repositories or realm. The parent may also be specified as part of the input. |
Explanation | A SortControl object was passed in for the search operation without a sort key, which is required to perform the sort. |
Action | Set the sort key in the SortControl object and ensure that the property used as the sort key is part of the return property list. |
Explanation | The user registry cannot get the next page of the search results. The cookie parameter that is used to get the next page of the search results must be specified in the PageControl object. |
Action | Ensure that the cookie property is specified in the PageControl object with an initial value of 0. The cookie in the PageResponseControl object returns the cookie value that is used to get the next page of the search results. |
Explanation | The search operation cannot be performed. The expression property must be specified in the SearchControl object. |
Action | Provide a search expression string in the expression property in the SearchControl object. |
Explanation | The operation cannot be performed. The search expression specified in the SearchControl object does not follow a supported XPath syntax. |
Action | Review the syntax of the search expression and correct any errors. |
Explanation | When creating an entity, the relative distinguished name (RDN) must be well formed and contain properties that are not ambiguous. For example, the OrgContainer entity type can represent either an organization (that uses the 'o' RDN property) or an organizational unit (that uses the 'ou' RDN property) in an underlying repository. If both 'o' and 'ou' are specified in the RDN for the input data object for the new entity, a unique name for the new entity cannot be created. |
Action | Determine the entity type that you want to create in the underlying repository and provide the appropriate RDN property for that type. For example, if you want to create an organization, provide only the 'o' property value. |
Explanation | The identifier of the entity was not specified. The system cannot find the entity. The user registry operation cannot continue without finding this entity. |
Action | Ensure that the entity in the input object contains an identifier property. |
Explanation | The specified identifier object is not valid. Either a valid uniqueId or uniqueName attribute must be specified in the identifier object. The user registry operation cannot continue without a valid identifier object. If an identifier object has been specified, either the uniqueId or the uniqueName is empty or null. |
Action | Ensure that the entity in the input object has an identifier with a valid uniqueId or uniqueName (both cannot be null or empty). |
Explanation | The specified unique name syntax is not valid. The uniqueName specified in the identifier property is not correct. The user registry operation cannot continue without the correct unique name. |
Action | Verify that the unique name is spelt correctly. Review the unique name syntax. For example, if it is in a Distinguished Name (DN) format, ensure that the special characters are escaped correctly. |
Explanation | The value of the property is not valid. For example, an identifier type property points to an incorrect entry. |
Action | Ensure that the value of the property is correct and is of the correct data type. If you are trying to retrieve identifier type property along with other properties, then split them into two calls. One call to retrieve non-identifier type properties and the other call to retrieve the identifier type property. |
Explanation | The specified uniqueId of the parent entity is not valid. Please specify a valid unique Id. |
Action | Verify uniqueId for the parent entity is present in the repository and that it is specified correctly. |
Explanation | The operation does not support multiple entities. For example, the update operation can only be performed on one entity at a time. |
Action | Ensure that only one entity is passed for the user registry operation. |
Explanation | The SearchControl object must be specified in the input object of the search operation. |
Action | Specify the SearchControl object in the search input object. |
Explanation | The number of records returned by the search is greater than the maximum number of records specified in the search limit. |
Action | Either increase the maximum search limit or make the search expression more restrictive so that a smaller number of records are fetched. |
Explanation | The countLimit parameter is used to specify the number of search results the caller wants to return in a search operation. It cannot be used together with the PageControl object. |
Action | Based on the requirement, the caller can use either the countLimit parameter or the PageControl object but not both. |
Explanation | The count limit for a search operation cannot be a negative number. A positive number sets the maximum number of entries returned as a result of the search. The value 0 indicates no limit; all entries are returned if the search limit is set to 0. |
Action | Do not specify a negative number for count limit. |
Explanation | During get operation, if the externalName is set, then the ExternalNameControl must be specified. |
Action | Specify the ExternalNameControl or remove the externalName from the input object. |
Explanation | The repository is a read-only repository. It does not support create, update, or delete operations. |
Action | Ensure that a write operation is not invoked on a read-only repository. |
Explanation | The operation cannot be performed because the value of the mandatory property is missing. For example, RDN (Relative Distinguished Name) property is not specified when the entity is created; or propertyName or entityTypeName is missing from PropertyDefinitionControl or ExtensionPropertyDefinitionControl; or entityName is missing from the entitySchema. |
Action | Provide a value for the mandatory property. |
Explanation | The search operation cannot be performed because the search expression is not valid. |
Action | Provide a valid search expression. |
Explanation | The specified operation requires an Entity object. |
Action | The entity object must be defined for the entity that you want to operate on. |
Explanation | The search limit for a search operation cannot be a negative number. |
Action | Do not specify a negative number for the search limit property. The value must be 0 or a positive number. |
Explanation | There is no cross-repository group configuration defined for the repository. |
Action | Refer to the log file for the reason of failure. Check your repository configuration. |
Explanation | User registry cannot get the next page of the search results. The cookie parameter that is used to get the next page of the search results in the PageControl object is not valid. |
Action | Ensure that a valid cookie is specified in the PageControl object. |
Explanation | The specified search base does not exist in the current realm. |
Action | Check the search base specified and ensure that the corresponding base entry is configured in the current realm. |
Explanation | The program encountered a system exception while performing the user registry operation. |
Action | Review the logs for the cause of this error and take appropriate corrective actions. |
Explanation | The program encountered the specified error during the operation. |
Action | Review the logs for the cause of this error and take appropriate corrective actions. |
Explanation | The caller's subject cannot be retrieved because of an unknown error. |
Action | Review the trace logs for the root cause of the error. There might be a problem with the WebSphere security configuration. |
Explanation | The subject's credentials cannot be retrieved because of an unknown error. |
Action | Review the trace logs for the root cause of the error. There might be a problem with the WebSphere security configuration. |
Explanation | The search operation cannot be performed because the search expression is not valid. |
Action | Provide a valid search expression. |
Explanation | An exception was thrown by the custom registry. The custom registry might be unavailable or unable to perform the operation. |
Action | Review the reason message and the trace file to determine the cause of the failure. Fix the error and try again. |
Explanation | An error occurred while mapping the given certificate to the user registry. |
Action | Either correct the certificate mapping in the serve.xml file or login with a valid certificate. |
Explanation | An error occurred while generating the certificate from the input certificate file. |
Action | Log in with a valid certificate. |
Explanation | The specified entity name, which could be a uniqueName or a uniqueId, could not be found in the underlying repository. The user registry operation cannot continue without finding this entity. |
Action | Ensure that the entity exists in the underlying repository. If the entity exists, then verify that the read permission is set for the entity and try again. |
Explanation | The entity cannot be retrieved because of the reason specified by the underlying repository. |
Action | Review the reason message and the trace file to determine the cause of the failure. Fix the error and try again. |
Explanation | The entity cannot be searched because of the reason specified by the underlying registry. |
Action | Review the reason message and the trace file to determine the cause of the failure. Fix the error and try again. |
Explanation | The federated repository could not be initialized due to an underlying failure. |
Action | Review the reason message and the trace file to determine the cause of the failure. Fix the error and try again. |
Explanation | The value of the property level, was specified as a negative number. |
Action | The value of the property, level, must be either 0 or a positive integer. Change the value of the property level and then try again. |
Explanation | The specified property is not defined for the particular entity type. |
Action | Verify that the property name is correct. |
Explanation | The message indicates that a general naming exception has occurred during an LDAP operation. See the exception for additional details. |
Action | Ensure that the related repository (for example, a database or an LDAP server) is started and set up correctly. |
Explanation | The authentication is not supported with the certificate by the repository. |
Action | Ensure that the authentication is supported with the certificate by the repository. |
Explanation | A principal name is required to log in with a password. |
Action | Ensure that the principal name is specified. |
Explanation | The principal name is not found in the repository. The login process cannot continue. |
Action | Ensure that the correct principal name is specified. |
Explanation | Multiple principals were found for the given principal name. The login process cannot continue. |
Action | Ensure that the right principal name is specified. For example, specifying the principal name as a unique name can avoid this type of exception. |
Explanation | If the principal name is specified during login process, then the password cannot be null or empty. |
Action | Specify the password. |
Explanation | Authentication using a certificate is not allowed by the underlying user registry. |
Action | Authenticate using a user ID and password instead of using a certificate. |
Explanation | The valid change types for a search for changed entities are add, modify, delete, rename and * (* is for all change types). |
Action | Specify one of the valid change types. |
Explanation | The user has tried to delete himself or herself from virtual member manager. This action is not allowed. |
Action | Log in as a different user to delete the current user. |