|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Tom, The short answer is that you can't. The only way to do it is to run multiple WAS instances, the problem with this is that you have to have multiple HTTP servers and use multiple ports. Hopefully they will improve this in the next release. What bugs me, is that you can't use LDAP for one application and OS security for another. I went through all of this when I wanted to have unique LDAP databases for QA and Production. In that case going with multiple instrances solved it. Mark Tom Malin <tmalin@csc.com> Sent by: java400-l-admin@midrange.com 07/22/2002 09:50 AM Please respond to java400-l To: java400-l@midrange.com cc: Subject: WebSphere Security 4.03 To All, I have implemented WebSphere Security within WebSphere 4.03 and Secureway. This works well with one app server application, but I have another app server application that needs security setup under the same node. In the Security console there is a field for the base DN this is okay , but how do you keep the roles and users apart from each application, especially if I am an ASP, and the clients need to create their own users through a web interface. One client might create a user that already exist in LDAP. Any help would greatly be appreciated. Thanks, Tom _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.