This documentation is not using the current rendering mechanism and will be deleted by December 31st, 2020. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.
Frequently Asked Questions¶
Is it possible to have both users manually defined (thus authenticated with a TYPO3 password) and users authenticated with LDAP?
Yes. Both for frontend and backend authentication it is possible to manually define users unrelated to your LDAP
server(s). When a user is manually defined, the record's column
tx_igldapssoauth_dn is empty and thus, since the
LDAP authentication will fail, it will automatically fall back to the standard TYPO3 authentication service. This
behaviour may be enabled/disabled globally for backend and/or frontend within Extension Manager.
I have a local user with the same username as a LDAP user but which has been manually created in TYPO3. Which password will be taken into account?
When you manually create a user in TYPO3, it is not related to LDAP. This local user may authenticate with the password you set. However is the user matches a LDAP user and the password provided results into a successful LDAP authentication, the manually created user will be automatically linked to the LDAP user. Afterwards, only the LDAP password will be valid.
I would like to silently and automatically authenticate my users in frontend (Single Sign On / SSO). Since Apache is configured to restrict access using Kerberos, no login form should be needed in my website. Is this possible with this extension?
Yes. You have to activate this option in Extension Manager and ensure you have properly configured mod_ntlm or
Kerberos with Apache (or any other supported web server). This extension will look for a username
$_SERVER['REMOTE_USER'] (without any domain part) to silently create the session in TYPO3.
I would like to do SSO in backend just like I do in frontend. Is this possible with this extension?
Yes. This is possible since version 3.2.0. Please keep in mind though that enabling SSO for the backend means it is then impossible for a user to log out. And TYPO3 may behave differently if you show the frontend while having a backend session active (e.g., frontend editing).
Can I import user groups automatically?
Yes you can.
May I manually tweak the name or configuration of imported user groups?
Yes. To do so, you should enable the global option in Extension Manager preventing the automatic synchronization of groups (may be configured separately for backend and frontend). In order to import new groups manually, use the LDAP / SSO backend module. Once imported, you may change their name to fit your needs and conventions.
My server is providing a hierarchy of groups. Is it possible to automatically mirror this structure in TYPO3?
Yes. You should provide a be_groups and/or fe_groups mapping instruction for the LDAP attribute holding the reference to the parent group. E.g.,
parentGroup = <memberof>
Which servers support the "memberOf" / "groupMembership" attribute?
Windows 2000 and above Active Directory definitely supports this attribute.
My infrastructure provides 2 LDAP servers, one containing group records, the second containing only users but with "memberOf" attributes corresponding to groups found on the other server. Is it possible to map those groups to the users?
Yes. In order to do that, you will need to manually import the LDAP user groups into your TYPO3 website and then configure the global option in Extension Manager that disables the synchronization of user groups. This way, only the configured baseDN for groups will be compared with the groups assigned as "memberOf" attributes, without actively retrieving corresponding group records from the LDAP server.
Is the effective user's password ever stored in TYPO3?
No. The password provided in the login form is sent directly to the LDAP server and never stored in TYPO3. However, since TYPO3 requires a password to be set for frontend and backend user records, this extension generates and saves a random 16 byte password for the sole purpose of making TYPO3 happy.
Can I encrypt my connection to the LDAP server?
Yes. This extension is supporting SSL-encrypted connection to the LDAP server as well as TLS-based connection.
Which port number is my LDAP server listening on?
It is not possible to answer without knowing your infrastructure but it is worth to mention that
- 389 is the industry standard port for LDAP connections over TCP/IP, and
- 636 is the industry standard port for LDAP connections over SSL.
I am currently using another LDAP extension to authenticate my users, namely :ter:`eu_ldap`. Does this extension at least provide the same feature set?
Yes. And in order to ease the migration, this extension is able to migrate your legacy eu_ldap configuration records to be compatible with ig_ldap_sso_auth using the "UPDATE!" script in Extension Manager (EM). You should first configure global options for ig_ldap_sso_auth in EM and only then migrate your legacy eu_ldap configuration records. This will ensure possible configuration issues to be detected.
The migration wizard does not require extension eu_ldap to be loaded but only expects the corresponding database table to be present.