< Day Day Up > |
Much of EJB security is concerned with authorization. In general, access to a deployed enterprise bean is via an ORB, such as RMI-IIOP. EJB authorization is based on a simplified CORBA security model, through which it is possible to establish whether an authenticated principal is authorized to invoke a method accessible via the ORB. The only architected means for a calling client to call a method on an enterprise bean is by calling it through RMI-IIOP. As described in Section 5.2.2.1 on page 177 and Section 5.2.2.2 on page 178, the deployment descriptor defines security roles that are authorized to execute each of the EJB methods . If a method anywhere in the deployment descriptor is part of an exclude-list element, the method is not accessible from outside the bean itself, so requests from clients to call the method are rejected. Conversely, if a method name appears under the unchecked element, any client is authorized to call the method. When a method has more than one security role associated with it, any authenticated client that is a member of one or more of the security roles required for the method is authorized to call the method. The client need not be a member of all the security roles but must be a member of at least one security role. EJB clients are constrained in how they are allowed to manage their security contexts, as these affect authorization.
|
< Day Day Up > |