Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-58193

Ldap configuration not accessable when ldap server is not reachable

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Deferred
    • Icon: Major Major
    • None
    • 3.1.5, 3.2.2
    • Authentication
    • MOODLE_31_STABLE, MOODLE_32_STABLE
    • Hide

      Increase your web server's page request timeout

      Edit config.php to override the ldap server host url

      $CFG->forced_plugin_settings = ['auth_ldap' => ['host_url' => 'NEW HOST']];

      You can then open the page, remove the line from config.php and save it in the open page and it will work. Then you won't have to keep editing config.php

      Or upgrade to 3.3+

      Show
      Increase your web server's page request timeout Edit config.php to override the ldap server host url $CFG->forced_plugin_settings = ['auth_ldap' => ['host_url' => 'NEW HOST']]; You can then open the page, remove the line from config.php and save it in the open page and it will work. Then you won't have to keep editing config.php Or upgrade to 3.3+

      Hi there,
      I discovered a problem with ldap authentication.
      When the configured ldap server ist down/ not reachable you cannot access the ldap configuration to change the settings. Obviosly the connection to the ldap server is checked when clicking on the configuration and end in an internal server error because of an timeout.
      ( I used 'snoop' th check what happen when accessing the configuration)
      Could it be that the host_url is not checked on creating, but first checked on trying to reconfigure it?
      I think this has changed from 2.9 to 3.1 ?

      cheers
      Thorsten

            dobedobedoh Andrew Lyons
            macduke Thorsten Bieser
            Votes:
            4 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.