Configuring Tiki to work with ClearOS's LDAP | |
If Tiki is installed on the ClearOS which has OpenLDAP | |
|
Works with 12.2: A user enters his own username/password (which are managed in ClearOS), and the user is logged in to Tiki.
For the other settings, no need to change when the Tiki is installed on the same machine as ClearOS unconfirmed bug with 12.0 and 12.1: http://dev.tiki.org/item4816 2014-07-30: old test server with latest 12.x and clearos-updates-testing (thus latest code of ClearOS 6.6) -> Activating "Use SSL (ldaps)" (auth_ldap_ssl) breaks the authentication for users. Latest 12.x from 2014-08-15: This config works for authentication, and the sync of Real name, country and email, but not groups
| |
If Tiki and ClearOS-LDAP are on different servers | |
|
tips from Peter 2014-02-25 Copy to clipboard
Old info (still valid?) "If the site is accessible via LDAPS, you need to use the port 636, otherwise the port 389. In this situation you can still access from the same server ldaps via 389 "Publish Policy" to "Local Network". This will set LDAP to listen for incoming requests on your LAN interface. See also:
Peter Baldwin (2014-03-04) wrote:
TLS on http://demo.tiki.org For some reason, I am unable to enable SSL support in the Tiki LDAP settings. I see a TLS error in the old test server LDAP logs, but I have no idea what's going on the client side. Any clues to what is happening on the client side? It has something to do with the client-side SSL/TLS settings (Ubuntu?). I can't duplicate this issue in my development environment (a ClearOS client). | |
Todos | |
|
| |
Solve binding | |
|
Advice from Peter (ClearOS) wrote:
It does not look like the LDAP connector in Tiki Wiki includes native support for the "LDAP Bind Type". It uses the following format for authenticating users: uid=test,ou=Users,ou=Accounts,dc=clear6,dc=lan But ClearOS uses: cn=test guy3,ou=Users,ou=Accounts,dc=clear6,dc=lan Why does ClearOS use a full name instead of a username? The gory technical details are explained by David in this bug report: http://tracker.clearfoundation.com/view.php?id=129 I can probably hack the code to add a new "LDAP Bind Type". I'll give it a try.
Here are some tests as per the script at: http://doc.tiki.org/LDAP+authentication#Debugging
| |
Sync user data from ClearOS-LDAP to Tiki upon login | |
|
According to http://doc.tiki.org/LDAP+authentication#How_it_works, all this should work if properly configured. Perhaps by solving the binding above, it will all work? 😊
Should there be a "create group if it doesn't exist" option? So Tiki wouldn't be polluted by unused groups from LDAP. | |
Sync OpenLDAP & Tracker data | |
| |
Solve TLS issue | |
| |
Forgot my password | |
| |
Prevent naming conflicts | |
|
In terms of sync of users/groups between ClearOS & Tiki, analyze & document any limitation to avoid future issues
| |
Self-registration via Tiki | |
|
A note from Peter (ClearOS) Copy to clipboard
| |
Make a Tiki Suite profile | |
|
With all the optional configuration at tiki-admin.php?page=login (LDAP tab), improve Tiki Suite profile. | |
FreeSWITCH | |
|
This is for later. Here are some notes | |
SabreDAV | |
|
SabreDAV could be interesting for ClearOS and Tiki (already in Kolab)
| |
Forums | |
Developer info | |
|
Any development should be done in trunk, and backported to 12.x LTS and/or 13.x if relevant. See Where to commit
| |
Related tools | |
|
https://www.fusiondirectory.org/
| |