Using JForum with LDAP

[Sverre Moe]

I have read that JForum can be used with LDAP, but I find no information about how to set JForum up with authentication against LDAP.
Version 2.1.8 of JForum has a class file called LDAPAuthenticator, which again is missing from latest beta.

Could anyone tell me how to configure LDAP for JForum or direct me to some information about this?

The web.xml in JForum has the following addition which is unused. The only configuration I could find for additional authentication.
<!-- SSO --> <!-- Example of SSO configuration --> <!-- <security-role> <role-name>user</role-name> </security-role> <security-constraint> <web-resource-collection> <web-resource-name>Restricted Area</web-resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <auth-constraint> <role-name>user</role-name> </auth-constraint> </security-constraint> <login-config> <auth-method>BASIC</auth-method> <realm-name>REALM NAME HERE</realm-name> </login-config> -->

[Tom Battaglia]

In WEB-INF/config there is a properties file named SystemGlobal.properties . LDAP settings are in there. I'm still working on setting it up, and I'll try to make a post when I get it working.

[Sri mutyala]

I set up the jforum for my organisation. Only thing is pending with LDAP. Kindly please let me know the proces..I have configured "SystemGlobals.properties" file. Still it is not authenticating. Kindly please let me know. How to proceed further. These are the only configurations, i have updated. Kindly let me know, if i need to do any other configuration changes.You quick response is more appreciated.

ldap.security.protocol =

# Security authentication to use. Possible values: "none", "simple", "strong",
# "EXTERNAL" (SASL). Leave empty (default) to let the provider figure it out
ldap.authentication =

# Class that provides a LDAP factory
ldap.factory = com.sun.jndi.ldap.LdapCtxFactory

# The prefix your LDAP server requires. e.g 'uid='
# The username supplied gets inserted just after the prefix,
# e.g: 'uid=username' so adjust the prefix properly
ldap.login.prefix = uid=

# The suffix your LDAP server requires.
# e.g 'ou=Users,dc=department,dc=company,dc=com'
ldap.login.suffix = OU=Users,OU=KLC,OU=APAC,DC=Company,DC=ad

# The url of your LDAP server.
# Notice that if your LDAP server uses SSL you will need to configure your
# server certificate so that Java Secure Sockets Extension (JSSE) will accept it.
# Read http://java.sun.com/products/jndi/tutorial/ldap/security/ssl.html
ldap.server.url = ldap://xxx.xx.xx.xxx

[Sri mutyala]

Any suggestions are more useful for me. This is Microsoft AD server, which does not have ssl. These are the configuration details i have given. But still its easily logging into forum site with out validating.

Kindly please suggest me. any configuration changes or need to add any more properties..

# #######
# LDAP
# #######
# Security protocol to use, e.g: "ssl"
# Leave it empty (default) to let the provider figure it out
ldap.security.protocol =LDAP v3

# Security authentication to use. Possible values: "none", "simple", "strong",
# "EXTERNAL" (SASL). Leave empty (default) to let the provider figure it out
ldap.authentication =EXTERNAL

# Class that provides a LDAP factory
ldap.factory = com.sun.jndi.ldap.LdapCtxFactory

# The prefix your LDAP server requires. e.g 'uid='
# The username supplied gets inserted just after the prefix,
# e.g: 'uid=username' so adjust the prefix properly
ldap.login.prefix =CN=

# The suffix your LDAP server requires.
# e.g 'ou=Users,dc=department,dc=company,dc=com'
ldap.login.suffix =OU=Users,OU=HST,OU=HYY,OU=INDIA,DC=company,DC=ad

# The url of your LDAP server.
# Notice that if your LDAP server uses SSL you will need to configure your
# server certificate so that Java Secure Sockets Extension (JSSE) will accept it.
# Read http://java.sun.com/products/jndi/tutorial/ldap/security/ssl.html
ldap.server.url = ldap://xxx.xx.xx.xxx

# Field that holds the user's email
ldap.field.email = mail

# ActiveDirectory
# To configure LDAPAuthenticator integrating with Microsoft Active Directory. The following two keys should be necessary.
# They are similar to ldap.login.prefix and ldap.login.suffix , but it's used when looking up user infomation
# rather than authentication. It's used when the login Distinguished Name (DN) is formatted differently from the lookup
# DN on some LDAP servers, for example, Microsoft Active Directory. If it's the case, you should add these keys in additional
# to ldap.login.prefix and ldap.login.suffix .
#
# The following example is for configuring on Microsoft Active Directory:
# ===========================
# ldap.login.prefix=CN=
# ldap.login.suffix=CN=Users,DC=jform,DC=net
# ldap.lookup.suffix=CN=Users
# ===========================
ldap.lookup.prefix =CN=
ldap.lookup.suffix =OU=Users,OU=HST,OU=HYY,OU=INDIA,DC=company,DC=ad


Regards,
Veera