Details

    • Type: New Feature
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 5.1.0
    • Fix Version/s: 5.2.0
    • Component/s: None
    • Labels:
      None

      Description

      Issue LEP-5374 doesn't seem to be solved. So here is a possible solution. My solution is only tested with LDAP import where the LDAP login attribute is numeric, eg.g I didn't touch the code fore manual user creation

      The refactoring in LEP-6952 make it now easier to implement a new login method I called loginName as opposed to screenName.

      • the User_ table is extended with a column loginName of type String.
      • the User service gets a new finder method <finder return-type="UserExt" name="LoginName"><finder-column name="loginName"></finder-column> </finder>
      • the screen name generator is used for both addUser and updateUser (the fact that it is not used in updateUser is a bug in my opinion)
      • screen names are always validated, even if they were auto-generated
      • NtlmAutoLogin uses only the screenName for authentication. In issue LEP-5374 a user commented that he had problems with numeric usernames in AD.

      If there is any interest in implementing this I can help with patches, otherwise I keep my changes in the EXT invironment.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              support-lep@liferay.com SE Support
              Reporter:
              maddin Martin Goldhahn (Inactive)
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  5.2.0