Java Certification Resources and Java Discussion Forum
https://enthuware.com/forum/
This means that the bean method itself runs as if it is run by the run-as role.17.3.4.1 Run-as
The Bean Provider can use the RunAs metadata annotation or the Bean Provider or Application Assembler can use the run-as deployment descriptor element to define a run-as identity for an enterprise bean in the deployment descriptor. The run-as identity applies to the enterprise bean as a whole, that is, to all methods of the enterprise bean’s business, home, and component interfaces, no-interface view, and/or web service endpoint; to the message listener methods of a message-driven bean; and to the timeout callback methods of an enterprise bean; and all internal methods of the bean that they might in turn call.
admin wrote:As per Section 17.4.3.1:This means that the bean method itself runs as if it is run by the run-as role.17.3.4.1 Run-as
The Bean Provider can use the RunAs metadata annotation or the Bean Provider or Application Assembler can use the run-as deployment descriptor element to define a run-as identity for an enterprise bean in the deployment descriptor. The run-as identity applies to the enterprise bean as a whole, that is, to all methods of the enterprise bean’s business, home, and component interfaces, no-interface view, and/or web service endpoint; to the message listener methods of a message-driven bean; and to the timeout callback methods of an enterprise bean; and all internal methods of the bean that they might in turn call.
HTH,
Paul.
This means the execution of the method itself runs as the "run-as" identity. So getCallerPrincipal should return the run-as identity.The security principal under which a method invocation is performed is typically that of the component’s caller. By specifying a run-as identity, however, it is possible to specify that a different principal be substituted for the execution of the methods of the bean’s business interface, no-interface view, homeinterface, component interface, and/or web service endpoint and any methods of other enterprise beans that the bean may call.
admin wrote:I do not agree with that. It applies to the execution of that method itself as well. Section 17.1 says this:This means the execution of the method itself runs as the "run-as" identity. So getCallerPrincipal should return the run-as identity.The security principal under which a method invocation is performed is typically that of the component’s caller. By specifying a run-as identity, however, it is possible to specify that a different principal be substituted for the execution of the methods of the bean’s business interface, no-interface view, homeinterface, component interface, and/or web service endpoint and any methods of other enterprise beans that the bean may call.
HTH,
Paul.
this has now been fixed.Note that getCallerPrincipal returns the principal that represents the caller of the enterprise bean, not the principal that corresponds to the run-as security identity for the bean, if any.