Moodle
  1. Moodle
  2. MDL-29431

When using LDAP auth, mandantory fields prevent user from applying user detail settings

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.1.1
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      Debian squeeze, Linux WEB 2.6.32-5-amd64 #1 SMP Fri Sep 9 20:23:16 UTC 2011 x86_64 GNU/Linux, Apache/2.2.16 (Debian) DAV/2 mod_ssl/2.2.16 OpenSSL/0.9.8o mod_chroot/0.5, php 5.3.8
    • Database:
      MySQL
    • Testing Instructions:
      Hide

      For example if I look at the country field on the profile update form just after a login try, I cannot fill it, but select from a dropdown list. Even if the selection is made the message is the same. I've uploaded some pics to prove this. 1: Képernyőkép.png the working configuration. 2: Képernyőkép-1.png an unworking config 3: képernyőkép-2.png the results. The profile update page continously appears after pressing the submit button. I've tried to reselect or refill the fields, but nothing helps.

      Show
      For example if I look at the country field on the profile update form just after a login try, I cannot fill it, but select from a dropdown list. Even if the selection is made the message is the same. I've uploaded some pics to prove this. 1: Képernyőkép.png the working configuration. 2: Képernyőkép-1.png an unworking config 3: képernyőkép-2.png the results. The profile update page continously appears after pressing the submit button. I've tried to reselect or refill the fields, but nothing helps.
    • Workaround:
      Hide

      while I was testing, it got clear, that when I set auth ldap on, users cannot leave the profile update form. However, users that already been a member of the site (old users), are authenticating and using the site happily. I suppose new users would do it also, but they cannot leave the profile update page. (even if there are no more mandantory fields)

      Show
      while I was testing, it got clear, that when I set auth ldap on, users cannot leave the profile update form. However, users that already been a member of the site (old users), are authenticating and using the site happily. I suppose new users would do it also, but they cannot leave the profile update page. (even if there are no more mandantory fields)
    • Affected Branches:
      MOODLE_21_STABLE
    • Rank:
      18937

      Description

      Auth LDAP module has a strange behaviour. In my configuration, there is an LDAP direcotry with mail,cn,userPassword attributes (and that'd all). When I set any user profiel fields, for example country to anything else then "locked", then on next login, when the user first synced with the server it cannot update it's profile data, since after pressing the submit button, the form always says, that "there are unfilled mandantory fields on the form".

      This then prevents the user from logging in!!!

      Thank you!

      1. Képernyőkép.png
        264 kB
      2. Képernyőkép-1.png
        266 kB
      3. Képernyőkép-2.png
        220 kB

        Activity

        Hide
        Éliás Tamás added a comment -

        I've noticed, that this was a completely different problem. It was not the signed fields were the problem, but the surname and lastname fields. Since we do not have these, I leave them empty. However if I check this, http://moodle.org/mod/forum/discuss.php?d=99071 it seems that moodle doesn't allow this. So I put the email attribute to the surname and lastname field too. This makes the portal look odd, but I think this is the only fast and non-hack solution. (the solution that was provided in the thread would require modifying the database by hand, wich I belive would break upgrades, and could lead to other inconsitencies.) So the bug report now narrowed to the surname-firstname problem.

        1: why moodle doesn't indicate them as mandantory on the useredit form?
        2: if they cannot be disabled, why allows moodle the field to be left empty witout a valid ldap attribute?
        3: is it possible to make moodle surname-firstname independant? (in our environment where everyone uses it's email to authenticate and has an own numeric ID, these name fields simply has no manner.

        Show
        Éliás Tamás added a comment - I've noticed, that this was a completely different problem. It was not the signed fields were the problem, but the surname and lastname fields. Since we do not have these, I leave them empty. However if I check this, http://moodle.org/mod/forum/discuss.php?d=99071 it seems that moodle doesn't allow this. So I put the email attribute to the surname and lastname field too. This makes the portal look odd, but I think this is the only fast and non-hack solution. (the solution that was provided in the thread would require modifying the database by hand, wich I belive would break upgrades, and could lead to other inconsitencies.) So the bug report now narrowed to the surname-firstname problem. 1: why moodle doesn't indicate them as mandantory on the useredit form? 2: if they cannot be disabled, why allows moodle the field to be left empty witout a valid ldap attribute? 3: is it possible to make moodle surname-firstname independant? (in our environment where everyone uses it's email to authenticate and has an own numeric ID, these name fields simply has no manner.
        Hide
        Michael de Raadt added a comment -

        Your problem seems very similar to one that has recently been fixed. Could you please look at MDL-28402 and see if the fix for this will resolve your problem?

        Show
        Michael de Raadt added a comment - Your problem seems very similar to one that has recently been fixed. Could you please look at MDL-28402 and see if the fix for this will resolve your problem?
        Hide
        Michael de Raadt added a comment -

        I'm assuming that this was fixed by MDL-28402. If that is not the case, please launch a new issue.

        Show
        Michael de Raadt added a comment - I'm assuming that this was fixed by MDL-28402 . If that is not the case, please launch a new issue.

          People

          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: