Trust between Containers
Trust between Containers
Application Server if the given roles associate to more than one user principal. Mapping roles to
principals is described in
identity is used to call a target bean, the target bean will receive the propagated identity only; it
will not receive any authentication data.
However, because the security identity is used in authorization checks (for example, method
permissions or with the isCallerInRole() method), it is vitally important that the security
identity be authentic. Because there is no authentication data available to authenticate the
propagated identity, the target must trust that the calling container has propagated an
authenticated security identity.
different containers. Therefore, there are no special steps that you need to take to set up a trust
relationship.
aspects of the application. Specifying this information in annotations or in the deployment
descriptor helps the deployer set up the appropriate security policy for the enterprise bean
application.
annotations. If a value for a method has not been specified in the deployment descriptor, and a
value has been specified for that method by means of the use of annotations, the value specified
in annotations will apply. The granularity of overriding is on the per-method basis.
and are discussed in this tutorial:
this annotation is discussed in
permissions. Use of these annotations is discussed in
identity. Use of this annotation is discussed in