First question is, do you need JAAS? Most app servers allow you to set
the default security mechanism (like LDAP) and you can use form based
authentication, which should also pick up the groups.
I'm doing it that way with Glassfish for declaratiive determination of
authorized pages and programmatic determination of available menus and
options. AFAIK, the same applies to WebSphere with Global Security
w/LDAP. Certainly user/password authentication is, and normally
groups/roles should be picked up when configured properly.
If JAAS is necessary, you're probably better off just writing it
yourself with a LoginModule implementation instead of trying to get
something with built-in restrictions (like JndiLoginModule) to work.
There's plenty of LDAP access code around. You can also look at something
like jGuard, but third party add-ons often use additional application
filters. App filters are great, but you can be surprised when and how often
Joe Sam Shirah - http://www.conceptgo.com
conceptGO - Consulting/Development/Outsourcing
Java Filter Forum: http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International? http://www.jguru.com/faq/I18N
Que Java400? http://www.jguru.com/faq/Java400
----- Original Message -----
From: "Brian Leathem" <bleathem@xxxxxxxxx>
To: "Java Programming on and around the iSeries / AS400"
Sent: Thursday, November 15, 2007 8:33 PM
Subject: JAAS, LdapLoginModule - no groups
Anyone out there using JAAS?
It seems the LdapLoginModule cannot be configured to return a list of
groups. The JndiLoginModule does have this feature, but it requires the
LDAP password to be publicly readable (not an option for us).
It seems I'm stuck implementing my own LoginModule, or extending the
LdapLoginModule to provide group info. This is a bit over my head right
now, can anyone suggest any alternatives? Or provide some pointers on
how to extend the LdapLoginModule?
As an Amazon Associate we earn from qualifying purchases.