Problem with OpenLdap with SSL and OpenMeetings 1_8_8_r4555

103 views
Skip to first unread message

Max León

unread,
Nov 22, 2011, 11:05:02 PM11/22/11
to openmeet...@googlegroups.com
Hello,
1st and foremost, CONGRATULATIONS ON A EXCEPTIONAL SOFTWARE.  Is truly awsome the level of maturity of the system, that being said....

I need a little bit of assistance, 
I have verson 1.8.8 (r4555) up and running on CentOS 6, I also integrated it with our OpenLdap with SSL, the ssl certificate has been imported in the trustore by running this command: "keytool -import -trustcacerts -alias openmeetings -file ~/SSL/certs/mycert.crt -keystore ~/mykeystore.jks" with success since after confirmation it claimed that it was imported successfully (the certificate is from digicert and I imported the ca.crt from them as well) .  Now the problem is that I keep getting this error: "Authentification on LDAP Server failed : ldap.server.com:636
ERROR 11-22 21:39:19.361 LdapAuthBase.java 151883 106 org.openmeetings.app.ldap.LdapAuthBase [NioProcessor-1] - [Authentification on LDAP Server failed]"
On the configuration file inside webapps/openmeetings/conf/ I called it myldap.cfg the I have the follwing:
ldap_server_type=OpenLDAP
ldap_conn_url=ldaps://ldap.server.com:636
ldap_admin_dn=UID:OM,OU:Users,OU:acl,DC:domain,DC:com
ldap_passwd=xyz
ldap_search_base=OU:Users,OU:axs,DC:domain,DC:com
field_user_principal=uid
ldap_auth_type=SIMPLE
ldap_sync_password_to_om=yes

I have tested the ldap_admin_dn with ldap-tools and it binds perfectly well.

Can someone through a little bit of light on what I'm doing wrong?, I'm running out of ideas.


Thank you very much.

seba....@gmail.com

unread,
Nov 23, 2011, 3:17:55 AM11/23/11
to openmeet...@googlegroups.com
Hm,

I have to review, I don't know if anybody tried yet openLDAP with SSL.

However, your error mesage actually says:
"Authentification on LDAP Server failed"
=> is there nothing more? Usually an error in the SSL cert leads to some different messages, "Authentification on LDAP Server failed" actually means everything is okay, but your PWD / admin user is wrong.

Sebastian

2011/11/23 Max León <ml...@wirewatchers.com>

--
You received this message because you are subscribed to the Google Groups "OpenMeetings User" group.
To view this discussion on the web visit https://groups.google.com/d/msg/openmeetings-user/-/0TRA0n1qB8kJ.
To post to this group, send email to openmeet...@googlegroups.com.
To unsubscribe from this group, send email to openmeetings-u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/openmeetings-user?hl=en.



--
Sebastian Wagner
http://www.openmeetings.de
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba....@gmail.com

Holger Rabbach (ICT)

unread,
Nov 23, 2011, 4:32:41 AM11/23/11
to openmeet...@googlegroups.com

Hi,

 

I’ve used ActiveDirectory with SSL successfully and have to concur that it looked different when the SSL handshake failed.

 

Holger

 

Description: holger-rabbach



OM International Limited - Unit B Clifford Court, Cooper Way - Carlisle CA3 0JG - United Kingdom
Charity reg no: 1112655 - Company reg no: 5649412 (England and Wales)

Max León

unread,
Nov 23, 2011, 7:48:13 PM11/23/11
to openmeet...@googlegroups.com
Hello guys,
Turns out it was a layer 8 problem....

This is what sent me in the right direction: Caused by: java.io.IOException: Invalid keystore format

I was calling the keytool built into the system and not the java one, so the format of the keystore was gks instead of jks and that was the problem, once I specify the whole path to the oracle keytool it went smooth.

Thank you again for your comments, actually those point me in the right direction.
Reply all
Reply to author
Forward
0 new messages