|
| Problem | Custom or third party JAAS Database Login modules can be implemented, but they will filter or pass through our ClientContainer or WSLogin built-in JAAS methods.
Also WebSphere requires a Custom Registry for a JDBC relational database backend. | | Cause | These are the current design specifications and not subject to change outside of submitting Feature Request through local marketing representative or SE. | | Solution | A Trust Association Interceptor can be implemented to have third party container managed security authentication passed to WebSphere (using for example custom built JAAS DBLogin module and jdbc Realm specification in an associated xml configuration file). Trust Association Interceptor is reliant upon class property values. | |
| | | Cross Reference information | Segment | Product | Component | Platform | Version | Edition |
---|
Application Servers | WebSphere Application Server Enterprise | Security | All Platforms | 5.x | All Editions | Application Servers | WebSphere Application Server for z/OS | Security | OS/390, z/OS | 5.0, 5.1, 5.3.0 | All Editions |
|
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Security Operating system(s): Multi-Platform Software version: 3.5, 4.0, 5.0, 5.1, 6.0 Software edition: Edition Independent Reference #: 1173051 IBM Group: Software Group Modified date: 2004-08-10
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|