Uploaded image for project: 'Service Packs and Hot Fixes'
  1. Service Packs and Hot Fixes
  2. MNT-8004

Option to create users either as user1 or user1@domain.com after kerberos authentication

    Details

    • Bug Priority:
      Category 3
    • Hot Fix Version:
      Historic
    • ACT Numbers:

      40218 40912

      Description

      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

        Attachments

          Issue Links

            Structure

              Activity

                People

                • Assignee:
                  closedbugs Closed Bugs (Inactive)
                  Reporter:
                  amadon Alex Madon [X] (Inactive)
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel