-
Type:
Hot Fix Request
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 3.4.7
-
Fix Version/s: 3.4.8 HF
-
Component/s: Repository Authentication and SSO
-
Labels:None
-
Environment:any with kerberos
-
Bug Priority:
Category 3
-
Hot Fix Version:Historic
-
ACT Numbers:
40218 40912
while fixing the inconsistency described in ALF-4599
where the CIFS class was creating kerberos users as
'user1@EXAMPLE.FOO'
and the web filter class was creting users as
'user1'
we decided to remove the inconsistency by storing then always as 'user1'
(if do not use the REALM part).
There are situations (like having several domains in a trust) where it is necessary to have the REALM appended to the sAMAccountName just as the userPrincipalName.
Could we make the choice of the username format a configurable option?
In the same way that we do for ldap sync where the paramter
ldap.synchronization.userIdAttributeName
can be any directory attribute like:
sAMAccountName
or
userPrincipalName
- is cloned by
-
MNT-7597
CLONE - Option to create users either as user1 or user1@domain.com after kerberos authentication
- Closed
- is duplicated by
-
MNT-2703
fix for ALF-4599 break JLAN kerberos multi-AD support (where ADs are in a trust relationship)
- Closed
- is related to by
-
MNT-7973
3.4.8.4 retests
- Closed
-
MNT-2703
fix for ALF-4599 break JLAN kerberos multi-AD support (where ADs are in a trust relationship)
- Closed
-
MNT-2756
Cannot create a Site with userPrincipalName
- Closed
- relates to
-
MNT-1697
CIFS access to alfresco with Kerberos authentication creates wrong users with domain suffix
- Closed