Active Directory authentication is case insensitive

  • This topic is empty.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #813
    AvatarVern
    Member
    • Total Post: 3
    • Newbie

    Hi…and help!

    I am trying to use Active Directory authentication on our V50s (build 6.5.2).

    This seems to work, except that users authenticate whatever case they enter they password. (e.g. password, PASSWORD and PaSsWoRd would all be allowed). This is causing problems as the screensaver lock requires users to unlock their device with exactly the same case password as they used to log onto the device with.

    AD is case sensitive, so I am confused how passwords with different cases are being allowed. If I try a different password the account is denied access so authentication of some form is happening with the AD.

    My WLX.INI contains:

    AUTH= glogin
    auth [ default=ignore ] /lib/security/pam_setpw.so
    auth [ success=2 default=ignore ] /lib/security/pam_guest.so
    auth [ success=1 new_authtok_reqd=1 default=ignore ] /lib/security/inifile.so try_first_pass
    auth [ success=ok new_authtok_reqd=ok default=die ] /lib/security/pam_smb_auth.so use_first_pass nolocal
    auth [ default=ok ] /lib/security/pam_putregistry.so save_ini=/tmp/user.ini
    AUTH_SMB.conf=domain=test.com server=191.56.251.138 backupserver=191.56.251.139

    Any ideas on what I am doing wrong? Is anyone else successfully using Active Directory authentication and not having this problem?

    Vern

    #11106
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hmm, sounds like a PAM issue to me. I have not tested this but the case should stick with the passwords. Definitely contact Wyse support unless one of the other Monkeys has tested this?

    Cheers,
    -TT

    #11110
    ConfGenConfGen
    Keymaster
    • Total Post: 11116
    • Jedi Master
    • ★★★★★★★

    Hi Vern,

    I’ve played with this some months ago and everything worked for at this time. But honestly I have never tested that far.
    That’s why I have tested different firmware builds and Auth_Domain addons.
    All show the same buggy behaviour you’ve described.
    So, you should go to Wyse and ask them to fix it.

    Cheers
    ConfGen

    #11112
    AvatarVern
    Member
    • Total Post: 3
    • Newbie

    Many thanks for the responses to this. The Wyse Support guys have confirmed that this is a problem and are investigating a solution. I’ll post back here when they get this cracked.

    Best regards

    Vern

    #11113
    ConfGenConfGen
    Keymaster
    • Total Post: 11116
    • Jedi Master
    • ★★★★★★★

    That would be great. Keep us all updated.

    Merry christmas
    CG

    #11155
    AvatarVern
    Member
    • Total Post: 3
    • Newbie

    Good news.

    Wyse support have come back with a new AUTH_DOMAIN-2.0.0-3.5.pak which fixes this issue.

    Best regards

    Vern

    #11157
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Thanks Vern for the update, I am sure others will be glad to know this. I will post the updated .pak int he Linux downloads section shortly,

    Cheers,
    -TT

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.