Closed bbaumgartl closed 4 years ago
Fixed indentation.
:+1: It doesn't only affect TYPO3 v9 but the v8 as well.
I tested the fix with TYPO3 v8.7.26, and imported users are correctly enabled.
@xperseguers would you consider including the change in the extensions next patch (3.4.1
)?
For the sake of clearness: in TYPO3 v8.7.26, with disable=0
in be_users_mapping
:
ig_ldap_sso_auth:3.3.1
, the user gets created at import and stays disabled until an admin manually changes it.ig_ldap_sso_auth:3.4.0
, the user gets created at import, but the user account is disabled. The user needs to log-in again after its first failed attempt in order for its account to be activated.Fixed in your name with 94190eb99b606a11611bc247b9147724736fe49c
If a BE user does not yet exists in the DB it should be created after successful LDAP authentication. The user is first created with default values (
Authentication:195
) and afterwards updated with mapped LDAP values (Authentication:230
). In TYPO3 v9 the fielddisable
has the default value1
which means after first creating the user it cannot be found byTypo3UserRepository:184
since this field is one of theenablecolumns
(Restrictions
).This patch uses the
QueryBuilder
to remove allRestrictions
(disable
fields) from the select instead of using the$tableConnection
sselect
directly (which enables allRestrictions
by default).Since there was no restriction before
Typo3UserRepository:159
this should be back to the original behavior.