Uploaded image for project: 'XWiki Platform'
  1. XWiki Platform
  2. XWIKI-2517

Login with existing user in different case generate new user profile with LDAP

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.4.1, 1.5 M2
    • Fix Version/s: 1.7 M1
    • Labels:
      None
    • Environment:
      case-sensitive database engine
    • keywords:
      ldap duplicate case sensitive
    • Tests:
      Unit
    • Similar issues:

      Description

      Hello,

      So I have LDAP authentication working now because of the awesome documentation provided. I have noticed a small problem however. When a user logs in with their active directory logon information for example, it will create the Xwiki user account, firstname.lastname, which is fine. However if they enter Firstname.lastname the second time they logon (notice the capital letter), it will create another entry which is a duplicate because of the capital letter. It seems as though the logon username box is case sensitive, is there a way to prevent this?

      Maybe I have something setup in my LDAP configuration wrong?

      I think you can even get the same effect with manually creating the accounts in xwiki, however. For example the default administrative account is Admin, but you could also create a user account called admin since it seems to care about the username being case sensitive. So maybe it doesn't have anything to do with LDAP. However, it would be cool to have xwiki know that Firstname.lastname is the same as firstname.lastname when logging in with ldap authentication to avoid it from creating duplicate accounts.

      Thanks!
      -Brent

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              tmortagne Thomas Mortagne
              Reporter:
              bbroge Brent Broge
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response: