

Write debug information to Tiki logs (Admin -> Tiki Logs, Tiki Logs have to be enabled).ĭo not enable this option for production sites.

Write LDAP debug Information in Tiki Logs The port number your LDAP server uses (389 is the default, 636 if you check SSL). Example: “localhost ldaps://:63636” will try to connect to localhost unencrypted and if if fails it will try the master LDAP server at a special port with SSL. If you use URIs, then the settings for Port number and SSL are ignored. Separate multiple entries with Whitespace or ‘,’. The hostnames, ip addresses or URIs of your LDAP servers. This can be useful to let external users (ex.: partners or consultants) access Tiki, without being in your main user list in LDAP.

If this option is set, users that are created using Tiki are not authenticated via LDAP.

Use Tiki authentication for users created in Tiki This option has no effect on users other than “admin”. If this option is set, the user “admin” will be authenticated by only using Tiki’s user database and not via LDAP. If a user was authenticated by Tiki’s user database, but not found on the LDAP server, Tiki will create an LDAP entry for this user.Īs of this writing, this is not yet implemented, and this option will probably not be offered in future. If this option is disabled, this user wouldn’t be able to log in. # these two attributes are not defined in Apache Directory Serverĭn: ou=attributetypes, cn=microsoft, ou=schemaĭn: m-oid=1.2.840.113556.1.4.221, ou=attributetypes, cn=microsoft, ou=schemaĭn: m-oid=1.2.840.113556.1.4.222, ou=attributetypes, cn=microsoft, ou=schemaĭn: ou=objectclasses, cn=microsoft, ou=schemaĭn: m-oid=1.2.840.113556.1.5.If a user was externally authenticated, but not found in the Tiki user database, Tiki will create an entry in its user database. # MICROSOFT SCHEMA for sAMAccountName and memberOf For my integration test cases on top of embedded Apache Directory Server I've added both memberOf and sAMAccountName attributes defined in Microsoft Active Directory server.
