WebSphere Application Server: Component vs Container Managed Authentication Alias
When defining the usage of an authentication alias in a resource in the administration console of WebSphere Application Server, there are two places the data can be specified:
Component Managed Authentication is used when the resource configured in the EJB’s deployment descriptor res-auth property is set to ‘Application’.
Container Managed Authentication is used when the resource configured in the EJB’s deployment descriptor res-auth property is set to ‘Container’.
The WebSphere v6 Administration Console notes that Container managed is deprecated and that component should be used.
EDIT #1: Thanks to David Currie for pointing out that it’s actually the specification of the authentication alias directly in the resource that is deprecated.
You should verify the res-auth setting of your jndi resources if you find that you configured an authentication aliasbut recieve an exception about null username at runtime.
Related Posts
- WebSphere 6.1 and Jakarta Commons Logging (JCL) using Log4J in an EJB
- IBM APAR PK49507: PROFILE RECREATION Required!
- WebSphere Application Server: Non-Deterministic Error when configuring Default Messaging Activation Specs
- System administration for WebSphere Application Server V7: Part 1 — An overview of administrative enhancements
- Adding pre-built JAR files to your EAR in Rational Application Developer
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
October 10th, 2008 at 8:22 am
The admin console deprecation warning is very misleading. The use of container managed authentication is actually preferred over component managed authentication! What is deprecated is specifying the alias for container managed authentication on the resource itself. It should instead be defined on the resource-reference. In this manner the credentials only apply to a particular usage of the resource rather than to any application in the cell that can retrieve the resource from JNDI.
October 10th, 2008 at 9:37 am
Thank you for your enlightenment on the topic David. It helps to put that deprecation message in context.