Ad Widget

Collapse

authentication failed

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • xs-
    Senior Member
    Zabbix Certified Specialist
    • Dec 2007
    • 393

    #1

    authentication failed

    Hi,

    Im currently testing 1.6 to use ldap as default authentication method.
    There are some users which arent available in ldap, so i created a seperate group with the 'gui access internal' option. Allas, the user cannot login.
    But after some testing, it seems that regardless of the default system auth method (either ldap or internal), the users with 'gui access internal' set via the group cannot login.

    Anyone else experiencing this?
  • Aly
    ZABBIX developer
    • May 2007
    • 1126

    #2
    Hmm in testings with ldap auth, internal login group users may login with no problem. FYI, empty passwords are not allowed, may be that is the case?!
    Zabbix | ex GUI developer

    Comment

    • xs-
      Senior Member
      Zabbix Certified Specialist
      • Dec 2007
      • 393

      #3
      Nop, even change the password multiple times to rule out weird character stuff.
      Users set to non-'system default' authentication cannot log in.

      Comment

      • Aly
        ZABBIX developer
        • May 2007
        • 1126

        #4
        Could you please tell us the steps you are doing to set ZABBIX auth and users group auth, for better testing.
        Zabbix | ex GUI developer

        Comment

        • xs-
          Senior Member
          Zabbix Certified Specialist
          • Dec 2007
          • 393

          #5
          sorry, i should have done this in my first post

          These are the steps i took in the beginning. I already have users configured. Some users are available in ldap, some users are not and should be authenticated locally.
          UserX is available in ldap.
          UserY is not available in ldap
          Both users have a password set internally.

          - admin -> auth -> configure and enable ldap support
          - Test UserX login (ldap auth, system default), it works
          - Test UserY login (ldap auth, system default), does not work (correctly!)
          - Create new usergroup
          - Set usergroup gui access to internal
          - Add UserY to new usergroup. In the userlist UserY shows 'GUI access: internal'
          - Test UserY login (internal auth?) does not work.

          After this, for debugging purposes, i set the system authentication back to internal
          - admin -> auth -> disable ldap support. (internal auth is default again)
          - Test UserX login (via internal pass), it works
          - Test UserY login (via internal pass), does not work
          - Remove UserY from new usergroup. In userlist UserY shows 'GUI access: System default'
          - Test UserY login (via internal pass), it works.

          I am using firefox for configuration and IE for login tests, so there is no chance of session conflicts / re-used sessions.

          Tom

          Comment

          • Aly
            ZABBIX developer
            • May 2007
            • 1126

            #6
            Found the bug If ZABBIX auth is set different from internal it by default on user update sets user password to "zabbix".

            Here is a patch.
            Attached Files
            Zabbix | ex GUI developer

            Comment

            • xs-
              Senior Member
              Zabbix Certified Specialist
              • Dec 2007
              • 393

              #7
              Super, patch works.

              Thanks!

              Comment

              Working...