Explanation |
See message. |
Explanation |
The embedded error message should assist in problem determination. If this is not the case, failure to delete a role is usually caused by an error in a lower level component. This error generally occurs when a Tivoli Access Manager component is incorrectly configured. |
Explanation |
See message. |
Explanation |
The embedded error message should assist in problem determination. If this is not the case, failure to add a role is usually caused by an error in a lower level component. This error generally occurs when a Tivoli Access Manager component is incorrectly configured. |
Explanation |
Operations on a PolicyConfiguration instance can only be made when it is in the inService or open states. This is an internal error. |
Explanation |
The specified file could not be found. |
Explanation |
See message. |
Explanation |
See message. |
Explanation |
See message. |
Explanation |
During the access decision Principals were found in the ProtectionDomain instance that was passed into the access decision. However, the WSSubject did not contain any PDPrincipal or WSPrincipal instances. |
Explanation |
During the access decision the retrieval of the Subject from the J2EE container failed. The Subject is required to retrieve the Principal making the request. |
Explanation |
During the access decision the retrieval of the Subject from the J2EE container failed. This is required to get the Principal that is making the request. |
Explanation |
See message. |
Explanation |
This is an internal error where the name or actions of the Permission are invalid. |
Explanation |
The Permissions, WebUserDataPermission and WebResourcePermission should only ever contain a single HTTP method during an access decision. |
Explanation |
Only special roles, Excluded and Unchecked can be added to WebUserDataPermissions. The J2EE container should not pass invalid roles. |
Explanation |
The configuration Permission should contain at least one HTTP method. |
Explanation |
See message. |
Explanation |
WebSphere Application Server is passing the GSO alias in an incorrect format. The GSO alias should be of the form resource/user. |
Explanation |
See message. |
Explanation |
The properties file that defines the mapping's between the J2EE Permission classes and the lower layers of embedded Tivoli Access Manager was not found. |
Explanation |
A PDPrincipal is required for embedded Tivoli Access Manager to perform authorization decisions. A PDPrincipal was not found in the Subject and errors were encountered when attempting to generate one. |
Explanation |
The context ID retrieved from the J2EE container was invalid. The expected format is href!cellName/appName/moduleName. |
Explanation |
The base class of all handlers failed during construction. Handlers are used to map Permission objects into Tivoli Access Manager protected objects. Execution cannot continue. |
Explanation |
Committing the configuration changes that were made during J2EE application deployment to the Tivoli Access Manager Policy Server failed. |
Explanation |
The deletion of policy within the specified context failed. The embedded error message will provide further information. |
Explanation |
A search of the Tivoli Access Manager Protected Object Space failed while attempting to ascertain whether the objects representing the specified Permission existed. |
Explanation |
See message |
Explanation |
A TAMPolicyConfiguration delete was requested but there was an error deleting any remaining WebUserDataPermission resources in Tivoli Access Manager in the current context. |
Explanation |
The AmasSession is used to establish a context with Tivoli Access Manager server. Execution cannot continue when this error occurs. |
Explanation |
The resource handlers are required to map J2EE role based policy into the Tivoli Access Manager protected object space. Execution cannot continue when this error occurs. |
Explanation |
See message. |
Explanation |
See message. |
Explanation |
See message. |
Explanation |
Operations performed on a RoleConfiguration instance can only be made when it is in the inService or open states. This is an internal error. |
Explanation |
The management context requires a valid value for cell, module and application name. |
Explanation |
See message. |
Explanation |
See message. |
Explanation |
See message. |
Explanation |
See message. |
Explanation |
See message. |
Explanation |
The PolicyConfiguration and RoleConfiguration objects should get created in the Tivoli Access Manager protected object space at J2EE application install time. The objects that will get created in TAM should be of the form /Container/ProductId/ResourceContainer/CellName/AppName/ModuleName. |
Explanation |
Committing the configuration changes that were made during J2EE application deployment to the Tivoli Access Manager Policy Server failed. |
Explanation |
See message. |
Explanation |
See message. |
Explanation |
See message. |