Explanation |
The policy cannot be instantiated because the contextID is null. |
System action |
The Common Authorization Component cannot continue with a null contextID. The Common Authorization Component will be stopped now. |
Operator response |
Check that the contextID was defined correctly during configuration. |
Explanation |
The policy cannot be deleted because there was an error with the specified contextID. |
System action |
The Common Authorization Component cannot continue without deleting this current policy. The Common Authorization Component will be stopped now. |
Operator response |
Check that the contextID was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
The policy cannot be retrieved because the contextID is null. |
System action |
The Common Authorization Component cannot continue with a null contextID. The Common Authorization Component will be stopped now. |
Operator response |
Check that the contextID was defined correctly during configuration. |
Explanation |
The role mapping context cannot be retrieved for the specified contextID. |
System action |
The Common Authorization Component cannot continue with this contextID. The Common Authorization Component will be stopped now. |
Operator response |
Check that the policyContextID was defined correctly during configuration. Check the reason message and trace file for cause of failure. |
Explanation |
The policy cannot be constructed because the contextID is null. |
System action |
The Common Authorization Component cannot continue with this contextID. The Common Authorization Component will be stopped now. |
Operator response |
Check that the contextID was defined correctly during configuration. |
Explanation |
The policy cannot be constructed for the specified contextID. |
System action |
The Common Authorization Component cannot continue without a configuration instance. The Common Authorization Component will be stopped now. |
Operator response |
Check that the contextID was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
All policies cannot be retrieved for the specified role. |
System action |
The Common Authorization Component cannot continue without retrieving all policy. The Common Authorization Component will be stopped now. |
Operator response |
Check that the contextID was defined correctly. Check that the role was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
The roles cannot be retrieved from the policy. |
System action |
The Common Authorization Component cannot continue without retrieving roles. The Common Authorization Component will be stopped now. |
Operator response |
Check that the contextID was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
The inherited roles cannot be retrieved for the specified base role. |
System action |
The Common Authorization Component cannot continue without retrieving the inherited roles. The Common Authorization Component will be stopped now. |
Operator response |
Check that the contextID was defined correctly. Check that the baseRole was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
The linked policies cannot be retrieved. |
System action |
The Common Authorization Component cannot continue with this contextID. The Common Authorization Component will be stopped now. |
Operator response |
Check that the contextID was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
The policy cannot be committed. |
System action |
The Common Authorization Component cannot continue without committing this policy instance. The Common Authorization Component will be stopped now. |
Operator response |
Check that the contextID was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
The policy cannot be linked to a null policy. |
System action |
The Common Authorization Component cannot continue with linking to a null policy. The Common Authorization Component will be stopped now. |
Operator response |
Check that the policy to link to was defined correctly. |
Explanation |
The current policy cannot be linked to the target policy. |
System action |
The Common Authorization Component cannot continue with linking the two policies. The Common Authorization Component will be stopped now. |
Operator response |
Check that the contextID was defined correctly. Check that the target contextID was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
The policy's state could not be changed to deleted. |
System action |
The Common Authorization Component cannot continue with deleting this policy. The Common Authorization Component will be stopped now. |
Operator response |
Check that the contextID was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
The current policy cannot be deleted. |
System action |
The Common Authorization Component cannot continue with deleting the current policy. The Common Authorization Component will be stopped now. |
Operator response |
Check that the policy to link to was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
The excluded permission is null and cannot be removed. |
System action |
The Common Authorization Component cannot continue with removing a null excluded permission. The Common Authorization Component will be stopped now. |
Operator response |
Check that the permission was defined correctly. |
Explanation |
The unchecked permission is null and cannot be removed. |
System action |
The Common Authorization Component cannot continue with removing a null unchecked permission. The Common Authorization Component will be stopped now. |
Operator response |
Check that the permission was defined correctly. |
Explanation |
The permission cannot be removed from the role. One or both is null. |
System action |
The Common Authorization Component cannot continue with removing the permission. The Common Authorization Component will be stopped now. |
Operator response |
Check that the permission was defined correctly. Check that the role was defined correctly. |
Explanation |
The role cannot be removed from the policy because it is null . |
System action |
The Common Authorization Component cannot continue with removing a null role. The Common Authorization Component will be stopped now. |
Operator response |
Check that the role was defined correctly. |
Explanation |
The policy for the specified role could not be removed. If permission was specified (not null), then this permission could not be removed for the role. |
System action |
The Common Authorization Component cannot continue with removing policy or permission for this role. The Common Authorization Component will be stopped now. |
Operator response |
Check that the roleName was defined correctly. Check that the permission was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
The excluded permission could not be added to the policy because it is null. |
System action |
The Common Authorization Component cannot continue with adding a null excluded permission. The Common Authorization Component will be stopped now. |
Operator response |
Check that the permission was defined correctly. |
Explanation |
The unchecked permission could not be added to the policy because it is null. |
System action |
The Common Authorization Component cannot continue with adding a null unchecked permission. The Common Authorization Component will be stopped now. |
Operator response |
Check that the permission was defined correctly. |
Explanation |
The permission collection could not be added to the policy. |
System action |
The Common Authorization Component cannot continue with adding null excluded permissions to the policy. The Common Authorization Component will be stopped now. |
Operator response |
Check that the excluded permissions were defined correctly. |
Explanation |
The permission collection could not be added to the policy. |
System action |
The Common Authorization Component cannot continue with adding null unchecked permissions to the policy. The Common Authorization Component will be stopped now. |
Operator response |
Check that the unchecked permissions were defined correctly. |
Explanation |
The permission cannot be added to the role. One or both is null. |
System action |
The Common Authorization Component cannot continue with adding permission to the role. The Common Authorization Component will be stopped now. |
Operator response |
Check that the permission was defined correctly. Check that the role was defined correctly. |
Explanation |
The permission collection cannot be added to the role. One or both is null. |
System action |
The Common Authorization Component cannot continue with adding permissions to the role. The Common Authorization Component will be stopped now. |
Operator response |
Check that the permissions were defined correctly. Check that the role was defined correctly. |
Explanation |
The permission could not be deployed for the role specified. |
System action |
The Common Authorization Component cannot continue with deploying permission to the role. The Common Authorization Component will be stopped now. |
Operator response |
Check that the role was defined correctly. Check that the permission was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
The role could not be added to base role because one or both is null. |
System action |
The Common Authorization Component cannot continue with adding role inheritance. The Common Authorization Component will be stopped now. |
Operator response |
Check that the base role was defined correctly. Check that the role was defined correctly. |
Explanation |
The role could not be added to base role. |
System action |
The Common Authorization Component cannot continue with adding role inheritance. The Common Authorization Component will be stopped now. |
Operator response |
Check that the base role was defined correctly. Check that the role was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
The XACML policy cannot be written to the specified output stream because it is null. |
System action |
The Common Authorization Component cannot continue writing to this output stream. The Common Authorization Component will be stopped now. |
Operator response |
Check that the output stream was defined correctly. Check if there are write permissions to the output stream. |
Explanation |
The XACML policy could not be retrieved or written to the specified output stream. |
System action |
The Common Authorization Component cannot continue writing XACML policy to the output stream. The Common Authorization Component will be stopped now. |
Operator response |
Check that the output stream was defined correctly. Check if there are write permissions to the output stream. Check the reason message and trace file for cause of failure. |
Explanation |
The XACML policy cannot be read from the specified input stream because it is null. |
System action |
The Common Authorization Component cannot continue reading from the input stream. The Common Authorization Component will be stopped now. |
Operator response |
Check that the input stream was defined correctly. Check if there are read permissions on the input stream. |
Explanation |
The XACML policy could not be deployed from the specified input stream. |
System action |
The Common Authorization Component cannot continue with deploying XACML policy from the input stream. The Common Authorization Component will be stopped now. |
Operator response |
Check that the input stream was defined correctly. Check if there are read permissions on the input stream. Check the reason message and trace file for cause of failure. |
Explanation |
The state cannot be changed to open. |
System action |
The Common Authorization Component cannot continue without updating state to open. The Common Authorization Component will be stopped now. |
Operator response |
Check the reason message and trace file for cause of failure. |
Explanation |
Role mapping cannot be instantiated with a null contextID. |
System action |
The Common Authorization Component cannot continue with a null contextID. The Common Authorization Component will be stopped now. |
Operator response |
Check that the contextID was defined correctly. |
Explanation |
Current role mappings cannot be deleted.. |
System action |
The Common Authorization Component cannot continue without deleting the current role mappings. The Common Authorization Component will be stopped now. |
Operator response |
Check that the contextID was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
Cannot check if role mapping is inService because the contextID is null. |
System action |
The Common Authorization Component cannot continue with a null contextID. The Common Authorization Component will be stopped now. |
Operator response |
Check that the contextID was defined correctly. |
Explanation |
Role mapping cannot be instantiated because the contextID was null. |
System action |
The Common Authorization Component cannot continue with a null contextID. The Common Authorization Component will be stopped now. |
Operator response |
Check that the contextID was defined correctly. |
Explanation |
Role mapping cannot be constructed for the specified contextID. |
System action |
The Common Authorization Component cannot continue without constructing a role mapping instance. The Common Authorization Component will be stopped now. |
Operator response |
Check that the contextID was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
The role condition or principal was null. |
System action |
The Common Authorization Component cannot continue with a null role condition or principal. The Common Authorization Component will be stopped now. |
Operator response |
Check that the role condition was defined correctly. Check that the principal was defined correctly. |
Explanation |
The role condition cannot be added to the principal. |
System action |
The Common Authorization Component cannot continue with adding role mapping to principal. The Common Authorization Component will be stopped now. |
Operator response |
Check that the role condition was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
Role mappings cannot be removed from the principal because it is null. |
System action |
The Common Authorization Component cannot continue with removing role mapping from principal. The Common Authorization Component will be stopped now. |
Operator response |
Check that the principal was defined correctly. |
Explanation |
Role mappings cannot be removed from the principal. |
System action |
The Common Authorization Component cannot continue with removing all role mappings from principal. The Common Authorization Component will be stopped now. |
Operator response |
Check that the principal was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
Role condition cannot be removed from the principal because one or both are null. |
System action |
The Common Authorization Component cannot continue with removing role mapping from principal. The Common Authorization Component will be stopped now. |
Operator response |
Check that the role condition was defined correctly. Check that the principal was defined correctly. |
Explanation |
Role condition cannot be removed from the principal. |
System action |
The Common Authorization Component cannot continue with removing role mapping from principal. The Common Authorization Component will be stopped now. |
Operator response |
Check that the role condition was defined correctly. Check that the principal was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
Role condition cannot be retrieved with a null principal. |
System action |
The Common Authorization Component cannot continue with a null principal. The Common Authorization Component will be stopped now. |
Operator response |
Check that the principal was defined correctly. |
Explanation |
Role conditions cannot be retrieved from the specified principal. |
System action |
The Common Authorization Component cannot continue with retrieving role conditions for principal. The Common Authorization Component will be stopped now. |
Operator response |
Check that the principal was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
Principals cannot be retrieved from the policy. |
System action |
The Common Authorization Component cannot continue with retrieving principals. The Common Authorization Component will be stopped now. |
Operator response |
Check the reason message and trace file for cause of failure. |
Explanation |
Changes to the role mapping configuration could not be committed. |
System action |
The Common Authorization Component cannot continue without committing the configuration. The Common Authorization Component will be stopped now. |
Operator response |
Check the reason message and trace file for cause of failure. |
Explanation |
The state could not be set to deleted. |
System action |
The Common Authorization Component cannot continue without changing the state to deleted. The Common Authorization Component will be stopped now. |
Operator response |
Check the reason message and trace file for cause of failure. |
Explanation |
The combining algorithm could not be set. |
System action |
The Common Authorization Component cannot continue with a null algorithmID. The Common Authorization Component will be stopped now. |
Operator response |
Check that the algorithm was defined correctly. |
Explanation |
The combining algorithm could not be set. |
System action |
The Common Authorization Component cannot continue with setting the combining algorithm. The Common Authorization Component will be stopped now. |
Operator response |
Check that the algorithm was defined correctly. Check the reason message and trace file for cause of failure. |
Explanation |
The combining algorithm could not be retrieved. |
System action |
The Common Authorization Component cannot continue without retrieving the combining algorithm. The Common Authorization Component will be stopped now. |
Operator response |
Check the reason message and trace file for cause of failure. |
Explanation |
The current roles could not be removed. |
System action |
The Common Authorization Component cannot continue without removing all current roles. The Common Authorization Component will be stopped now. |
Operator response |
Check the reason message and trace file for cause of failure. |
Explanation |
The contextID is null. |
Operator response |
Check that the contextID was defined correctly. |
Explanation |
The policy was not found. |
Operator response |
Check that the contextID was defined correctly. |
Explanation |
The policy was already inService. |
Operator response |
Check that the contextID was defined correctly. |
Explanation |
The policy state was already deleted. |
Operator response |
Check that the contextID was defined correctly. |
Explanation |
The policy state was already deleted. |
Operator response |
Check that the contextID was defined correctly. |
Explanation |
The state was already inService. |
Operator response |
Check that the contextID was defined correctly. |
Explanation |
The role policy state was already deleted. |
Operator response |
Check that the contextID was defined correctly. |
Explanation |
The cache encountered an internal error. See the excepiotn for the details. |
System action |
Internal error. |
Operator response |
Check the cache configuration to ensure that the parameters are valid. |
Explanation |
The MCCFile class had problems initalizing |
System action |
Failure to start. |
Operator response |
Check the configuration to ensure that the parameters are valid. Check the xmt for valid data |
Explanation |
The xmt file defines classes that do not exist in the class path |
System action |
These classes and xmt options will be ignored |
Operator response |
Check the classpath to ensure all the required classes exist. Check the xmt files for correct classnames |
Explanation |
The xmt file defines invalid information |
System action |
XMT entries ignored |
Operator response |
Check the xmt file is correctly defined |
Explanation |
The xmt file defined in the configuration could not be loaded |
System action |
The file will be ignored |
Operator response |
Check the configuration to ensure the xmt file name exists and is readable by the system. |
Explanation |
The user defined xmt file does not contain valid data |
System action |
The file will be ignored |
Operator response |
Check the configuration to ensure the xmt file is in the correct format. |
Explanation |
The user defined xmt file could not be loaded |
System action |
The file will be ignored |
Operator response |
Check the configuration to ensure the xmt file located where configured and is readable. |
Explanation |
The xmt is incorrectly specified |
System action |
The xmt action will be ignored |
Operator response |
Check the configuration to ensure the xmt file is in the correct format. |
Explanation |
The XMT file could not be opened |
System action |
The xmt file will be ignored |
Operator response |
Check the configuration to ensure the xmt file readable and existing on the file system. |
Explanation |
The XMT file is incorrectly specified |
System action |
The xmt constructor will be ignored |
Operator response |
Check the configuration to ensure the xmt is correctly specified. |
Explanation |
The xmt handler is incorrectly specified |
System action |
The xmt action will be ignored |
Operator response |
Check the configuration to ensure the xmt file is a valid format. |
Explanation |
The xmt mapping is incorrectly specified |
System action |
The xmt action will be ignored |
Operator response |
Check the configuration to ensure the xmt file is a valid format. |
Explanation |
The xmt node is incorrectly specified |
System action |
The xmt action will be ignored |
Operator response |
Check the configuration to ensure the xmt file is a valid format. |
Explanation |
Exception contains the reason |
System action |
Act based on the exception |
Operator response |
Work out why an exception is occurring. |
Explanation |
Exception contains the reason |
System action |
Act based on the exception |
Operator response |
Work out why an exception is occurring. |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
Some XMT property definitions reference other properties. One of these references was invalid. |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions. |
System action |
Fix the xmt based on the error. |
Operator response |
Check that the xmt is defined correctly. |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions |
System action |
Fix the xmt based on the error |
Operator response |
Check that the xmt is defined correctly |
Explanation |
The XMT file has incorrect XMT definitions. |
System action |
Fix the xmt based on the error. |
Operator response |
Check that the xmt is defined correctly. |
Explanation |
The XML export system needs a SAX ContentHandler to write policy data to. Policy export cannot continue. |
System action |
Export of policy to XML aborted. |
Operator response |
Contact support. |
Explanation |
Conversion of a piece of stored policy information to XML failed. |
System action |
Remaining policy information will be written. |
Operator response |
Inspect exported XML for errors. Contact support. |
Explanation |
The XML export could not get an instance of a class required to retrieve policy information. Exported XML may be incomplete. |
System action |
Remaining policy information will be written. |
Operator response |
Inspect exported XML for errors. Contact support. |
Explanation |
The context IDs linked to the current context could not be retrieved. |
System action |
Remaining policy information will be written. |
Operator response |
Contact support. |
Explanation |
The context IDs linked to the current context could not be retrieved. |
System action |
Remaining policy information will be written. |
Operator response |
Contact support. |
Explanation |
The context ID as specified in the XML file being imported must match the current context ID. |
System action |
No policy information will be imported. |
Operator response |
Ensure the correct file is being imported. Connect using the desired context ID. |
Explanation |
The imported document must be well-formed. If using a custom XSLT stylesheet to transform an input document, ensure the output adheres to the schema. |
System action |
No policy information will be imported. |
Operator response |
If using a custom XSLT stylesheet, ensure the output document is correct. If using the default XACML-format stylesheet, ensure the XACML document is well-formed. If the XACML document is correct, contact support. |
Explanation |
If the configuration instance was opened to configure principal-to-role mapping, it cannot be used to import an XML document containing permission-to-role mapping policy. |
System action |
No policy information will be imported. |
Operator response |
Ensure the correct document is being imported. Open a separate configuration instance to import permission-to-role mappings |
Explanation |
If the configuration instance was opened to configure permission-to-role mapping, it cannot be used to import an XML document containing principal-to-role mapping policy. |
System action |
No policy information will be imported. |
Operator response |
Ensure the correct document is being imported. Open a separate configuration instance to import principal-to-role mappings |
Explanation |
The section of the imported document containing role-based policy contained a section without a specified role name. |
System action |
No policy information will be imported. |
Operator response |
If using a custom XSLT stylesheet, ensure the output document correctly identifies role names. If using the default XACML-format stylesheet, ensure the XACML document is well-formed. If the XACML document is correct, contact support. |
Explanation |
The XML imported requires a org.w3c.dom.Document object. This object could not be created. |
System action |
No policy information will be imported. |
Operator response |
Contact support. |
Explanation |
The imported XML document specified that additional context IDs should be linked to the current context. This action could not be performed due to an error. |
System action |
No policy information will be imported. |
Operator response |
See the error details for more information. |
Explanation |
Information specifying a permission object was extracted from the XML. However, an error occurred when storing this information. |
System action |
No policy information will be imported. |
Operator response |
If using a custom XSLT stylesheet, ensure the output document correctly formats permission data. If using the default XACML-format stylesheet, ensure the XACML document is well-formed. If the XACML document is correct, contact support. |
Explanation |
Information specifying a RoleCondition object was extracted from the XML. However, an error occurred when storing this information. |
System action |
No policy information will be imported. |
Operator response |
If using a custom XSLT stylesheet, ensure the output document correctly formats role mapping data. If using the default XACML-format stylesheet, ensure the XACML document is well-formed. If the XACML document is correct, contact support. |
Explanation |
Information specifying a piece of policy data was extracted from the XML. The conversion of this object to the internal format failed. |
System action |
No policy information will be imported. |
Operator response |
If using a custom XSLT stylesheet, ensure the output document correctly formats role mapping data. If using the default XACML-format stylesheet, ensure the XACML document is well-formed. If the XACML document is correct, contact support. |
Explanation |
The specified combining algorithm could not be stored as an internal error occurred. |
System action |
No policy information will be imported. |
Operator response |
Contact support. |
Explanation |
An exception was caught when extracting policy information from storage. See the log for more details. |
System action |
Extraction will continue, however the policy returned for this role may be incomplete. |
Operator response |
See the error log for more detailed information. |
Explanation |
An exception was caught when extracting role-mapping information from storage. See the log for more details. |
System action |
Extraction will continue, however the role-mappings returned for this principal may be incomplete. |
Operator response |
See the error log for more detailed information. |
Explanation |
An exception was caught when extracting the role combining algorithm from storage. See the log for more details. |
System action |
Extraction will continue, however the role combining algorithm may be omitted. |
Operator response |
See the error log for more detailed information. |
Explanation |
An exception was caught when extracting the list of known role names from storage. |
System action |
Extraction will continue, however the list of known roles may be incomplete. |
Operator response |
See the error log for more detailed information. |
Explanation |
An exception was caught when extracting the list of principals from storage. |
System action |
Extraction will continue, however the list of principals may be incomplete. |
Operator response |
See the error log for more detailed information. |
Explanation |
The import of the specified XML document failed. See the error log for the returned reason. |
System action |
The data in the imported document will be ignored. |
Operator response |
Ensure the imported XML document is valid. |
Explanation |
The export of the specified policy as XML failed. See the error log for the returned reason. |
System action |
Execution will continue, however the exported XML may be invalid. |
Operator response |
Contact support. |
Explanation |
An instance of an org.w3c.dom.Document could not be created. This object is required for conversion to and from XML objects. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Contact support. |
Explanation |
If validation is enabled, objects imported from XML will be instantiated as validation. This process failed for an object of the specified class. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Contact support. |
Explanation |
An object read from an imported XML document was invalid. See the root exception for the cause. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Contact support. |
Explanation |
All objects converted to XML must have a URN mapped as an identifier. An URN was not found for an object being exported, so conversion will not continue. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Contact support. |
Explanation |
The parameter specifying the class of an XMTObject was not found. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Contact support. |
Explanation |
The property definitions required for conversion of the object could not be found. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Contact support. |
Explanation |
An error occurred during the conversion of the XMTObject to an XML DataValue element. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Contact support. |
Explanation |
An error occurred during the conversion of the XMTObject to an XML DataValue element. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Contact support. |
Explanation |
A null value was passed to the XML conversion class. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Contact support. |
Explanation |
An XML fragment specified an object whose class cannot be found. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Check the imported XML is valid, and that the JVM classpath settings are correct. |
Explanation |
Each object specified in XML must specify it's class in a ClassName element. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Check the imported XML is valid. |
Explanation |
Each object specified in XML must specify it's type in a DataType attribute. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Check the imported XML is valid. |
Explanation |
The DataType specified for the object must map to a known object type. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Check the imported XML is valid. |
Explanation |
The DataType specified for the object must map to a known object type. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Check the imported XML is valid. Check the XMT configuration file is valid. |
Explanation |
The element passed for conversion is of an invalid type. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Check the imported XML is valid. |
Explanation |
The class passed for conversion does not have an XMT type mapped to it. This probably means the class is not defined at all the XMT configuration files. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Ensure the class is defined in the XMT configuration files. |
Explanation |
The passed object could not be converted to the requested type. See the error log for the cause. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Contact support. |
Explanation |
The object could not be converted from an XMTObject to a Java insantiated class. Ensure the XMT definition of the class is correct. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Ensure the XMT configuration file is correct. Contact support |
Explanation |
The object could not be converted from an XMTObject to a Java insantiated class. Ensure the XMT definition of the class is correct. |
System action |
Execution cannot continue, an exception will be thrown. |
Operator response |
Ensure the XMT configuration file is correct. Contact support |
Explanation |
Each properties definition in the XMT configuration file requires the <ClassName> element to be present. |
System action |
Error logged, validation of file failed. |
Operator response |
Ensure the XMT configuration file is correct. |
Explanation |
A variable passed to the constructor of the CfgDataProcessingImpl class contained an invalid value. |
System action |
Construction cannot continue, DataProcessingException will be thrown. |
Operator response |
Contact support. |
Explanation |
An error occurred while loading the Common Authorization Component properties file. Check the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Check the properties file is in the Common Authorization Component's home directory and is valid. Contact support. |
Explanation |
An error occurred while creating an instance of a required class. Check the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
A null InputStream was passed to the XACML import function. |
System action |
Throwing DataProcessingException. |
Operator response |
Ensure the location of the file exists. Contact support. |
Explanation |
An exception was thrown during the import of XACML-based policy. Check the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Ensure the XACML input file is valid. Contact support. |
Explanation |
The XACML import requires an XSLT stylesheet to translate the XML into an internal format. This stylesheet could not be found. |
System action |
Throwing DataProcessingException. |
Operator response |
Check the classpath is set up correctly. Contact support. |
Explanation |
An exception was thrown during the export of policy in XACML foramt. Check the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
The XACML export requires an XSLT stylesheet to translate the internal format into XACML. This stylesheet could not be found. |
System action |
Throwing DataProcessingException. |
Operator response |
Check the classpath is set up correctly. Contact support. |
Explanation |
Attempt to deploy a null policy object. This action is invalid. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
All policy objects are converted to XMT format for storage. This conversion process failed. See the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Ensure the class of the converted object is known to the XMT system. Contact support. |
Explanation |
When retrieving policy, we pass an object specifying what we want to extract from storage. This object was null. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
The format used in storage needs to be converted to Java objects. This process failed. See the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
When remove policy, we pass an object specifying what we want to remove from storage. This object was null. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
All policy objects are converted to XMT format for the storage system. This conversion process failed. See the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Ensure the class of the converted object is known to the XMT system. Contact support. |
Explanation |
The code representing the state to set was an unknown value. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
When linking policy, both the target and source must be non-null and non-empty strings. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
This function requires an instance of the PolicyMgmt class. An instance of this class could not be obtained. |
System action |
Action depends on calling function. |
Operator response |
Contact support. |
Explanation |
An exception was thrown while linking policy. Check the error log for details. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
Invalid input was detected when attempting to add an inherited role. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
An exception was thrown when attempting to add an inherited role. See the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
The specified combining algorithm must be both non-null and not blank. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
An exception was thrown when it was attempted to set the combining algorithm. See the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
An exception was thrown when it was attempted to retrieve linked policy contexts. See the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
A base role must be specified to retrieve inhertied roles. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
Data is returned from storage in multiple pages. An error occurred while moving to the next page of results. See the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
Only one combining algorithm should be specified, however multiple combining algorithms were returned from storage. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
The inputs to the function should be non-null, and non-empty strings if applicable. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
An exception was caught when attempting to retrieve the list of known role-mapping policy context IDs. See the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
An exception was caught when attempting to check the uniqueness of a context ID. See the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
An exception was caught when extracting the permission policy contexts from storage. See the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
An exception was caught when extracting the role-mapping context for a specifiy policy context from storage. See the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
An exception was caught when instantiating an interface to the storage system. See the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
An exception was caught when retrieving policy information from storage. See the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
The object cache must be both not null and initialized. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
An exception was thrown when moving to a certain page of the result set. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
An exception was thrown when checking if the current version of policy held by runtime is the current version. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
An exception was thrown when retrieving the version of policy held in storage. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
An error was encountered while attempting to refresh the current version. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
An instance of the MCCJavaHandler class is required, however this instance could not be created. |
System action |
Throwing Exception. |
Operator response |
Contact support. |
Explanation |
Data retrieved from storage needs to be converted back to a usable format. This processed failed, see the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
Data retrieved from storage needs to be converted back to a usable format. This process returned a null value, which is not meant to happen. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
The system property specifying the Common Authorization Component's home directory needs to be set in order to load the configuration file. |
System action |
No properties will be loaded. |
Operator response |
Ensure the JVM arguments are correctly set. |
Explanation |
The Common Authorization Component properties file was not found in the home directory specified as a system argument. |
System action |
No properties will be loaded. |
Operator response |
Ensure the file is in the home directory. Ensure the home directory is correctly set. |
Explanation |
The Common Authorization Component properties file could not be loaded as an input stream could not be created to read the file. |
System action |
No properties will be loaded. |
Operator response |
Ensure the file is readable by the current user. Ensure the file is formatted correctly. |
Explanation |
The Common Authorization Component properties file could not be loaded due to an exception. See the error log for more details. |
System action |
No properties will be loaded. |
Operator response |
Ensure the file is readable by the current user. Ensure the file is formatted correctly. |
Explanation |
An exception was thrown when checking the permissions for a method. See the error log for more details. |
System action |
Throwing security exception. |
Operator response |
Contact support |
Explanation |
A method requested a check on the validity of the current state. This check failed. |
System action |
Throwing UnsupportedOperationException. |
Operator response |
Contact support |
Explanation |
The size of the buffer used when writing data to storage can be specified in the Common Authorization Component properties file. However, an invalid value was specified. |
System action |
Using the default value for the buffer size. |
Operator response |
Ensure the properties file specifies the buffer size correctly. Only positive integers are valid. |
Explanation |
The amount of time data will be buffered when writing data to storage can be specified in the Common Authorization Component properties file. However, an invalid value was specified. |
System action |
Using the default value for the buffering period. |
Operator response |
Ensure the properties file specifies the buffering period correctly. An value larger than 0.001 is valid. |
Explanation |
The StorageBuffer interfaces with the storage layer to save and retrieve data. An exception was caught during this process, see the error log for more details. |
System action |
Logging error and continuing. |
Operator response |
Inspect the error logged by the root exception for information. |
Explanation |
The StorageBuffer could not obtain a lock on its internal buffer. |
System action |
Logging error and continuing. |
Operator response |
Contact support. |
Explanation |
The utility class cannot convert a null PagedResultSet from XMTObjects to Java objects. |
System action |
Throwing MCCUtilException |
Operator response |
Contact support. |
Explanation |
No defined constructor could be found that matches the data present in the XMTObject. |
System action |
Returning a null value. |
Operator response |
Contact support. |
Explanation |
The construction of the object failed for an unknown reason. Check the error log for more details. |
System action |
Returning a null value. |
Operator response |
Contact support. |
Explanation |
The XMT engine subsystem threw an exception when converting an XMTObject back to a Java instance. See the error log for more details. |
System action |
Throwing MCCUtilException. |
Operator response |
Contact support. |
Explanation |
A null object was passed to create a query from. This is invalid. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
An exception was thrown when looking up the XMT type of the specified class. Check the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
An exception was thrown when looking up the XMT type of the specified class. Check the error log for more details. |
System action |
Throwing DataProcessingException. |
Operator response |
Contact support. |
Explanation |
Each connection to storage must be identified by a context and a client ID. No client ID has been specified. |
System action |
Connection cannot continue, throwing exception. |
Operator response |
Contact support. |
Explanation |
Each connection to storage must be identified by a context ID and a client ID. No context ID has been specified. |
System action |
Connection cannot continue, throwing exception. |
Operator response |
Contact support. |
Explanation |
Data extracted from storage is placed in an implementation-neutral result set before being returned. The creation of a result set failed. See the error log for more details. |
System action |
Extraction of data cannot continue, throwing exception. |
Operator response |
Contact support. |
Explanation |
An error occurred during the process of writing policy data to storage. See the error log for more details. |
System action |
Extraction of data cannot continue, throwing exception. |
Operator response |
Contact support. |
Explanation |
An error occurred during the process of writing policy data to storage. See the error log for more details. |
System action |
Extraction of data cannot continue, throwing exception. |
Operator response |
Contact support. |
Explanation |
An error occurred during the process of writing policy data to storage. See the error log for more details. |
System action |
Extraction of data cannot continue, throwing exception. |
Operator response |
Contact support. |
Explanation |
An error occurred during the process of removing policy data to storage. See the error log for more details. |
System action |
Operation cannot continue, throwing exception. |
Operator response |
Contact support. |
Explanation |
An error occurred during the process of retrieving changed policy data from storage. See the error log for more details. |
System action |
Extraction of data cannot continue, throwing exception. |
Operator response |
Contact support. |
Explanation |
An exception was thrown during the creation of a PolicyStore. See the error log for more details. |
System action |
Creation cannot continue, throwing exception. |
Operator response |
Contact support. |
Explanation |
An exception was thrown during the initialization of required sessions. See the error log for more details. |
System action |
Execution will continue, but functionality may be diminished. |
Operator response |
If errors are thrown later during execution, contact support. |
Explanation |
An exception was thrown while attempting to change to different page of a result set. See the error log for more details. |
System action |
Execution will continue, but functionality may be diminished. |
Operator response |
If errors are thrown later during execution, contact support. |
Explanation |
An IndexOutOfBoundsException was caught when attempting check if two rows match. See the error log for more details. |
System action |
Match function is returning false. |
Operator response |
This error may not effect normal operation. |
Explanation |
The Common Authorization Component properties file did not specify a storage back-end adapter to use. The default file-based storage adapter will be used. |
System action |
Creating an instance of the FileSystemAdapterImpl class. |
Operator response |
If an adapter has been specified, check that the property has been set correctly. |
Explanation |
The class specified in the Common Authorization Component properties file as the storage adapter class could not be found. |
System action |
Throwing an exception. |
Operator response |
Check the class is specified correctly in the properties file. Check the classpath is specified correctly. |
Explanation |
While the class specified as the storage adapter was found, the getAdapter() method could not be invoked to get an instance of this adapter. See the error log for more details. |
System action |
Throwing an exception. |
Operator response |
Ensure the storage adapter implementation correctly defines the required methods. |
Explanation |
The files could not be copied as the data could not be either read from the source or written to the target. |
System action |
Throwing IOException. |
Operator response |
Ensure the current user has appropriate permissions for this operation. |
Explanation |
The files could not be copied as the source file does not exist. |
System action |
Throwing IOException. |
Operator response |
Ensure the copy operation has specified the correct source file. Ensure the current user has appropriate permissions for this operation. |
Explanation |
The property specified references a null value, and will be ignored. |
System action |
Skipping property. |
Operator response |
If the property should have been set, check the spelling matches the correct value. |
Explanation |
An exception was thrown during the creation of the file-based storage adapter. See the error log for more details. |
System action |
Throwing PolicyStoreException. |
Operator response |
Inspect the error log for the cause of the exception. |
Explanation |
The directories required for the file-based adapter could not be created. See the error log for more details. |
System action |
Throwing FSException. |
Operator response |
Ensure the current user has correct privileges to create the directories. |
Explanation |
An exception was thrown while removing a row from a table. See the error log for more details. |
System action |
Throwing PolicyStoreException. |
Operator response |
Check the error log for the cause of the error. |
Explanation |
An exception was thrown while closing a transaction. See the error log for more details. |
System action |
Logging warning and continuing. |
Operator response |
The file may not have been closed completely. This may cause later problems. |
Explanation |
The input to a function was null. |
System action |
Throwing PolicyStoreException. |
Operator response |
Contact support. |
Explanation |
An exception was thrown while attempting to close a transaction. Check the error log for more details. |
System action |
Throwing PolicyStoreException. |
Operator response |
Contact support. |
Explanation |
An exception was thrown while attempting to create the specified table. Check the error log for more details. |
System action |
Throwing PolicyStoreException. |
Operator response |
Check the error log for the root cause of the exception. Contact support. |
Explanation |
An exception was thrown while attempting to perform a search on a table. Check the error log for more details. |
System action |
Throwing PolicyStoreException. |
Operator response |
Check the error log for the root cause of the exception. Contact support. |
Explanation |
Perform this operation requires an active session, however no active session was found. |
System action |
Throwing PolicyStoreException. |
Operator response |
Contact support. |
Explanation |
An exception was thrown while attempting to add data to a table. Check the error log for more details. |
System action |
Throwing PolicyStoreException. |
Operator response |
Check the error log for the root cause of the exception. Contact support. |
Explanation |
A required lock could not be obtained. |
System action |
Throwing PolicyStoreException. |
Operator response |
Contact support. |
Explanation |
An exception was caught during the process of deleting all policy. See the error log for more details. |
System action |
Throwing PolicyStoreException. |
Operator response |
Inspect the error log for the root cause of the problem Contact support. |
Explanation |
The master version the DB was null. The initial version is being returned instead. |
System action |
Returning initial version. |
Operator response |
If unexpected behaviour occurs, contact support. |
Explanation |
The master version the DB was null. |
System action |
Throwing PolicyStoreException |
Operator response |
Contact support. |
Explanation |
An exception was thrown during the policy refresh procedure. See the error log for details. |
System action |
Throwing PolicyStoreException |
Operator response |
Contact support. |
Explanation |
An exception was thrown during the retrieval of full policy. See the error log for details. |
System action |
Throwing PolicyStoreException |
Operator response |
Contact support. |
Explanation |
The name of the sandbox holding changed policy could not be found. |
System action |
Ignoring possibly sandboxed information. |
Operator response |
If unexpected behaviour occurs, contact support. |
Explanation |
The specified context ID was not found in the context table. |
System action |
Throwing PolicyStoreException. |
Operator response |
Contact support. |
Explanation |
An error was encountered while attempting to update the session. See the error log for more details. |
System action |
Throwing PolicyStoreException. |
Operator response |
Contact support. |
Explanation |
An exception was thrown when attempting to commit policy. Check the error log for more details. |
System action |
Throwing PolicyStoreException. |
Operator response |
Contact support. |
Explanation |
Unable to obtain shared lock on session. |
System action |
Throwing PolicyStoreException. |
Operator response |
Contact support. |
Explanation |
Unable to obtain exclusive lock on session. |
System action |
Throwing PolicyStoreException. |
Operator response |
Contact support. |
Explanation |
An exception was thrown when attempting to roll back policy changes. Check the error log for more details. |
System action |
Returning, indicating failure. |
Operator response |
Contact support. |
Explanation |
An exception was thrown when attempting to remove session information for the current context ID and client ID. See the error log for more details. |
System action |
Logging warning and continuing. |
Operator response |
This failure may cause unexpected behaviour. Contact support if this occurs. |
Explanation |
An exception was thrown when attempting to destroy session information. See the error log for more details. |
System action |
Throwing PolicyStoreException. |
Operator response |
Contact support. |
Explanation |
An exception was thrown when attempting to retrieve information from the session table. See the error log for more details. |
System action |
Throwing PolicyStoreException. |
Operator response |
Contact support. |
Explanation |
An error was encountered while attempting to initialize the session. See the error log for more details. |
System action |
Throwing PolicyStoreException. |
Operator response |
Contact support. |
Explanation |
An error was encountered while attempting to remove the session. See the error log for more details. |
System action |
Throwing PolicyStoreException. |
Operator response |
Contact support. |
Explanation |
An error was encountered while attempting to dump a table. See the error log for more details. |
System action |
Throwing PolicyStoreException. |
Operator response |
Contact support. |
Explanation |
An error was encountered while attempting to rebuild a table. See the error log for more details. |
System action |
Logging and continuing |
Operator response |
This failure may cause unexpected behaviour. Contact support if this occurs. |
Explanation |
An error was encountered while attempting to cleanup expired delta tables. See the error log for more details. |
System action |
Logging and continuing |
Operator response |
This failure may cause unexpected behaviour. Contact support if this occurs. |
Explanation |
An error was encountered while attempting to get current session versions. See the error log for more details. |
System action |
Logging and continuing |
Operator response |
This failure may cause unexpected behaviour. Contact support if this occurs. |
Explanation |
An error was encountered while attempting to manipulate a table lock. See the error log for more details. |
System action |
Logging and continuing. |
Operator response |
This failure may cause unexpected behaviour. Contact support if this occurs. |
Explanation |
An exception was caught when searching through a table stored on disk. See the error log for more details. |
System action |
Throwing FSException |
Operator response |
Contact support. |
Explanation |
We expected the symbol marking row changes, but it was not found. This could mean the file has become corrupt. |
System action |
Ignoring this row. |
Operator response |
This failure could indicate a file has become corrupted. |
Explanation |
The record indicated was only partially read. This could mean the file has become corrupted. |
System action |
Ignoring this row. |
Operator response |
This failure could indicate a file has become corrupted. |
Explanation |
The data read from the file didn't match the expected data, as determined by the defined schema. This could mean the file has become corrupted. |
System action |
Skipping this column. |
Operator response |
This failure could indicate a file has become corrupted. |
Explanation |
The type of this record is unknown. |
System action |
Skipping this column. |
Operator response |
This failure could indicate a file has become corrupted. |
Explanation |
The specified table has not been opened. Tables must be open to perform operations on them. |
System action |
Throwing FSException |
Operator response |
Contact support. |
Explanation |
An exception was thrown when copying files. See the error log for details. |
System action |
Throwing FSException |
Operator response |
Ensure the current user has the correct privileges to copy files. |
Explanation |
An exception was thrown when adding data to the open table. See the error log for details. |
System action |
Throwing FSException |
Operator response |
Ensure the current user has the correct privileges to modify files. |
Explanation |
An exception was thrown when opening the specified table. See the error log for details. |
System action |
Throwing FSException |
Operator response |
Ensure the current user has sufficient privileges. |
Explanation |
The specified table was not found. |
System action |
Throwing FSException |
Operator response |
Ensure the current user has sufficient privileges |
Explanation |
An exception was thrown when closing the specified table. See the error log for details. |
System action |
Throwing FSException |
Operator response |
Ensure the current user has sufficient privileges. |
Explanation |
The requested lock could not be obtained as it would cause a deadlock. |
System action |
Lock aborted, throwing FSException |
Operator response |
Contact support. |
Explanation |
The requested lock could not be obtained as nested locking is not supported. |
System action |
Lock aborted, throwing FSException |
Operator response |
Contact support. |
Explanation |
An exception was caught when attempting to obtain a lock on the specified table. |
System action |
Lock aborted, throwing FSException |
Operator response |
Contact support. |
Explanation |
An exception was caught when attempting to release the lock on the specified table. |
System action |
Lock aborted, throwing FSException |
Operator response |
Contact support. |
Explanation |
An exception was caught when attempting to write the header for the specified table. |
System action |
Write aborted, throwing FSException |
Operator response |
Contact support. |
Explanation |
An exception was caught when attempting to read the header for the specified table. |
System action |
Read aborted, throwing FSException |
Operator response |
Contact support. |
Explanation |
A PrivilegedActionException was caught when attempting to executed a command. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
The SearchAction recorded an exception during execution. |
System action |
Logging warning and continuing |
Operator response |
This failure may cause unexpected behaviour. |
Explanation |
This object is an invalid search target, ignoring this object during the search. |
System action |
Logging and continuing. |
Operator response |
This failure may cause unexpected behaviour. Contact support if this occurs. |
Explanation |
This column will be skipped due to previous error. See the error log for more details. |
System action |
Skipping this column. |
Operator response |
See the error log for the reason this column was skipped. |
Explanation |
Could not acquire all the required locks to perform the operation. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
A writer lock could not be obtained for the instance master repository. |
System action |
Logging warning. |
Operator response |
This information is provided as part of a later error message. |
Explanation |
A writer lock could not be obtained for the instance delta repository. |
System action |
Logging warning. |
Operator response |
This information is provided as part of a later error message. |
Explanation |
A writer lock could not be obtained for the instance context repository. |
System action |
Logging warning. |
Operator response |
This information is provided as part of a later error message. |
Explanation |
An exception was caught during the removal of the role context associated with the above policy context. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
Could not acquire all the required locks to perform the operation. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
Could not acquire all the required locks to perform the operation. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
Could not acquire all the required locks to perform the operation. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
Could not acquire all the required locks to perform the operation. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
Could not acquire all the required locks to perform the operation. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
A file system lock for the specified path could not be obtained. The file is most likely locked by another process. |
System action |
Exception is thrown. |
Operator response |
Check that no other applications are locking table files (such Google Desktop). |
Explanation |
An error occurred while attempting to retrieve policy. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
An error occurred while attempting to retrieve policy. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
Could not acquire all the required locks to perform the operation. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
The query used to retrieve delta policy is invalid. |
System action |
Continuing. |
Operator response |
This warning may be the cause of erratic behaviour. |
Explanation |
An error occurred while attempting to retrieve delta policy. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
An exception was thrown while retrieve delta policy. See the error log for details. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
One or both of the specified contexts were either null or empty strings. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
The locks required to link contexts could not be obtained. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
We could not find the entry in the config table for the above context ID. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
The entry in the config table for the above context has already been flagged as deleted. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
The locks required to remove this context could not be obtained. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
The context ID specified was null. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
The locks required to retrieve context information from storage could not be obtained. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
The locks required to retrieve context information from storage could not be obtained. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
Attempted to retrieve role context information, but the specified policy context was null. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
Attempted to add data to the master repository, but some of the required information was null. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
Attempted to delete data from the master repository, but some of the required information was null. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
The locks required to refresh policy could not be obtained. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
An error was encountered while attempting to retrieve the name delta StoreRecords. The classname was null. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
The locks required to create a new session could not be obtained. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
A file system lock for the specified path could not be obtained. The file is most likely locked by another process. |
System action |
A retry attempt will be made. |
Operator response |
Check that no other applications are locking table files (such Google Desktop). |
Explanation |
Attempted to retrieve linked policy information, but the specified context was null. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
The DB name could not be found for the set of StoreRecord objects. |
System action |
Logging warning and continuing. |
Operator response |
Contact support. |
Explanation |
The locks required to get the master version could not be obtained. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
Internal software error. |
System action |
Logging warning and continuing. |
Operator response |
Contact support. |
Explanation |
The locks required to get an instance of the master repository could not be obtained. |
System action |
Throwing exception. |
Operator response |
Contact support. |
Explanation |
Cannot read the runtime directory. |
System action |
Common Authorization Component cannot continue with this runtime directory. |
Operator response |
Check if there are read permissions on the runtime directory. |
Explanation |
This method is not implemented. |
System action |
Return an empty result, or throw a runtime exception. |
Operator response |
Please do not use this method. |
Explanation |
Cannot write the runtime directory. |
System action |
Common Authorization Component cannot continue with this runtime directory. |
Operator response |
Check if there are write permissions on the runtime directory. |
Explanation |
The policy context is null at runtime. |
System action |
Return the result that denies all access requests. |
Operator response |
This should be an exploiter's bug. |
Explanation |
The runtime directory is not a directory. |
System action |
Common Authorization Component cannot continue with this runtime directory. |
Operator response |
Change the runtime directory path name or retry after deleting it. |
Explanation |
The policy context is null at runtime. |
System action |
Return the result that denies all role memberships. |
Operator response |
Check that the role mapping context exists for the policy context under the evaluation. Also, this may be an exploiter's bug. |
Explanation |
EvaluationContext#getContext threw an PolicyContextException. |
System action |
Ignore the exception. |
Operator response |
Check the logging message for more details. |
Explanation |
Failed to open the file input stream. |
System action |
Throw a runtime exception. |
Operator response |
Check if the file exists. |
Explanation |
Found a version inconsistency for the policy configuration. |
System action |
Ignore the inconsistency, and full-retrieve the configuration data from the policy storage. |
Explanation |
Failed to open the file output stream. |
System action |
Throw a runtime exception. |
Operator response |
Check if the file exists. |
Explanation |
Found a version inconsistency for the role mapping configuration. |
System action |
Ignore the inconsistency, and full-retrieve the configuration data from the policy storage. |
Explanation |
Failed to read from the file input stream. |
System action |
Throw a runtime exception. |
Operator response |
Check if there are read permissions on the file. |
Explanation |
Found a version inconsistency for the policy configuration. |
System action |
Ignore the inconsistency and use the current version as the new version. |
Explanation |
Failed to write to the file output stream. |
System action |
Throw a runtime exception. |
Operator response |
Check if there are write permissions on the file. |
Explanation |
Found a version inconsistency for the role mapping configuration. |
System action |
Ignore the inconsistency and use the current version as the new version. |
Explanation |
Failed to delete the file. |
System action |
Throw a runtime exception. |
Operator response |
Check if there are delete permissions on the file. |
Explanation |
Failed to mkdirs the directory. |
System action |
Throw a runtime exception. |
Operator response |
Check if there are create permissions on the directory. |
Explanation |
Failed to check whether a client id is unique. |
System action |
Ignore the error, and proceeds |
Operator response |
Check the root exception for the cause of failure. |
Explanation |
The policy context is not in service. |
System action |
No policy is evaluated. |
Operator response |
Create and commit the policy context. |
Explanation |
Failed to create a client for the context. |
System action |
Throw a runtime exception. |
Operator response |
Explanation |
The role mapping context is not in service. |
System action |
No policy is evaluated. |
Operator response |
Create and commit the role mapping context. |
Explanation |
Failed to get the list of policy contexts from the policy storage. |
System action |
Throw a runtime exception. |
Operator response |
Check if the policy storage is working. |
Explanation |
Failed to get the list of role mapping contexts from the policy storage. |
System action |
Throw a runtime exception. |
Operator response |
Check if the policy storage is working. |
Explanation |
Failed to retrieve the policy configuration data from the policy storage. |
System action |
Ignore this failure so that it has no impact on other policy contexts. Note that the policy context can not be in service. |
Operator response |
Check the root exception for the cause of failure. |
Explanation |
Failed to retrieve the role mapping configuration data from the policy storage. |
System action |
Ignore this failure so that it has no impact on other role mapping contexts. Note that the role mapping context can not be in service. |
Operator response |
Check the root exception for the cause of failure. |
Explanation |
The role mapping context corresponding to the policy context is null at policy refresh. |
System action |
The policy context is ignored and so will not be in service. |
Operator response |
Check the role mapping context is created for the policy context by the policy storage. Contact support. |
Explanation |
Failed to convert the context id to a file name. |
System action |
Throw a runtime exception. |
Operator response |
Check the root exception for the cause of failure. Change the context identifier. |
Explanation |
The policy storage returned a list of context identifiers including a null context id. |
System action |
Ignore the null context identifier. |
Operator response |
Ignore this warning. |
Explanation |
Failed to store a Java object to the file. |
System action |
Throw a runtime exception. |
Operator response |
Check the root exception for the cause of failure. |
Explanation |
The policy storage returned a list of context identifiers including an empty context id. |
System action |
Ignore the empty context identifier. |
Operator response |
Ignore this warning. |
Explanation |
Failed to retrieve a Java object from the file. |
System action |
Throw a runtime exception. |
Operator response |
Check the root exception for the cause of failure. |
Explanation |
The file was not found at refresh-time. |
System action |
Re-create the file from scratch. |
Explanation |
The system property is not set. |
System action |
Throw a runtime exception. |
Operator response |
Check that the system property is set when you start your JVM. |
Explanation |
The role limit was exceeded. The policy context may consume too much memory. |
System action |
Ignore. |
Operator response |
Check whether the policy configuration defines too many roles. Also, check whether the value of the com.ibm.sec.authz.provider.CommonAuthzPolicy.maxNumOfRoles property is appropriate. |
Explanation |
Multiple instances of the class (CommonAuthzPolicy or CommonAuthzRoleMapping) were created in a single JVM. It must be a singleton. |
System action |
Ignore this error, but the Common Authorization Component may not work correctly. |
Operator response |
This should be an exploiter's bug. Check that you do not create multiple instances of the class. |
Explanation |
The permission limit was exceeded. The policy context may consume too much memory. |
System action |
Ignore. |
Operator response |
Check whether the policy configuration has too many excluded permissions. Also, check whether the value of the com.ibm.sec.authz.provider.CommonAuthzPolicy.maxNumOfPermissions property is appropriate. |
Explanation |
The Common Authorization Component properties file is missing. Check the error log for more details. |
System action |
Ignore, and use default property values. |
Operator response |
Check the properties file is in the Common Authorization Component home directory and is valid. Contact support. |
Explanation |
The permission limit was exceeded. The policy context may consume too much memory. |
System action |
Ignore. |
Operator response |
Check whether the policy configuration has too many unchecked permissions. Also, check whether the value of the com.ibm.sec.authz.provider.CommonAuthzPolicy.maxNumOfPermissions property is appropriate. |
Explanation |
The permission limit was exceeded. The policy context may consume too much memory. |
System action |
Ignore. |
Operator response |
Check whether the policy configuration has too many role based permissions. Also, check whether the value of the com.ibm.sec.authz.provider.CommonAuthzPolicy.maxNumOfPermissions property is appropriate. |
Explanation |
The principal limit was exceeded. The role mapping context may consume too much memory. |
System action |
Ignore. |
Operator response |
Check whether the policy configuration defines too many principals. Also, check whether the value of the com.ibm.sec.authz.provider.CommonAuthzRoleMapping.maxNumOfPrincipals property is appropriate. |
Explanation |
The role condition limit was exceeded. The role mapping context may consume too much memory. |
System action |
Ignore. |
Operator response |
Check whether the role mapping configuration has too many role conditions. Also, check whether the value of the com.ibm.sec.authz.provider.CommonAuthzRoleMapping.maxNumOfRoleConditions property is appropriate. |
Explanation |
Failed to the role mapping context corresponding to the policy context. Check the error log for more details. |
System action |
Return null. |
Operator response |
Check the role mapping context is created for the policy context by the policy storage. Contact support. |