http://blog.danzrobok.com/2008/10/09/websphere-application-server-component-vs-container-managed-authentication-alias/ Business Integration and SOA with an IBM WebSphere slant Fri, 09 Jan 2009 21:52:38 +0000 http://wordpress.org/?v=2.6.3 http://blog.danzrobok.com/2008/10/09/websphere-application-server-component-vs-container-managed-authentication-alias/#comment-2437 dan Fri, 10 Oct 2008 14:37:50 +0000 http://blog.danzrobok.com/2008/10/09/websphere-application-server-component-vs-container-managed-authentication-alias/#comment-2437 Thank you for your enlightenment on the topic David. It helps to put that deprecation message in context. Thank you for your enlightenment on the topic David. It helps to put that deprecation message in context.

]]> http://blog.danzrobok.com/2008/10/09/websphere-application-server-component-vs-container-managed-authentication-alias/#comment-2435 David Currie Fri, 10 Oct 2008 13:22:52 +0000 http://blog.danzrobok.com/2008/10/09/websphere-application-server-component-vs-container-managed-authentication-alias/#comment-2435 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. 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.

]]>