Thanks, for your fastest assistance.
As stated at the JBoss documentation,
http://docs.jboss.org/admin-devel/Chap8.html#0_pgfId-920186
a login and password can be configured to bind to ldap.
| * java.naming.security.principal, The principal for authenticating the
caller to the service. This is
| built from other properties as described below.
| * java.naming.security.credentials, The value of the property depends on
the authentication scheme.
| For example, it could be a hashed password, clear-text password, key,
certificate, and so on.
|
At our project the users under ou=people cannot have permissions to do a BIND
on LDAP.
Anyway, what do you think in the following fix:
If a Context.PRINCIPAL is supplied, use the way I specified above and let the
Context.PRINCIPAL do a BIND to LDAP.
If Context.PRINCIPAL is not specified the use the actual code.
| String _principal = env.getProperty(Context.SECURITY_PRINCIPAL);
| if (_principal == null) {
| env.setProperty(Context.SECURITY_PRINCIPAL, userDN);
| env.put(Context.SECURITY_CREDENTIALS, credential);
| }
|
And the question about role-group mapping ?
Thank you
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3854364#3854364
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3854364
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
