Moodle

NTLM not working

Details

  • Type: Sub-task Sub-task
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Not a bug
  • Affects Version/s: 1.9
  • Fix Version/s: None
  • Component/s: Authentication
  • Labels:
    None
  • Environment:
    Operating system-windows xp, Moodle 1.9Beta
  • Affected Branches:
    MOODLE_19_STABLE

Description

I tried to implement single sign on for moodle.But i got some errors when i go to oncampuslogin page.The errors are shown as bellow.

"NTLM/Integrated Authentication on this page has not been enabled, please contact your server admin for details.
Click here to login via the offcampus login page"

When i on the debugging for moodle it says

"Navigation needs to be updated to use build_navigation()

  • line 3352 of lib\weblib.php: call to debugging()
  • line 37 of theme\standardwhite\header.html: call to print_navigation()
  • line 2506 of lib\weblib.php: call to include()
  • line 308 of auth\ntlm\oncampuslogin.php: call to print_header()"
    and some ather errors like this.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Iñaki Arenaza added a comment -

This bug report doesn't make much sense to me. On the one hand you talk about oncampuslogin.php, on the other the bug is marked as affecting version 1.9.

There is no auth/ntlm/oncampuslogin.php in version 1.9. The NTLM authentication method has been folded in the LDAP authentication plugin and you don't need the external contrib plugin any more. Are you sure your bug affects Moodle version 1.9?

Saludos. Iñaki.

Show
Iñaki Arenaza added a comment - This bug report doesn't make much sense to me. On the one hand you talk about oncampuslogin.php, on the other the bug is marked as affecting version 1.9. There is no auth/ntlm/oncampuslogin.php in version 1.9. The NTLM authentication method has been folded in the LDAP authentication plugin and you don't need the external contrib plugin any more. Are you sure your bug affects Moodle version 1.9? Saludos. Iñaki.
Hide
Permalink
Red Morris added a comment -

I think someone has got confused with moving to 1.9. It was a bit confusing for those of us who had used Dans add-ons for 1.7/1.8, especially as NTLM operates from the LDAP folder.

A check to see if the authentication method for the user is set to ntlm and changing it to ldap might help help with the transition. I had to do this manually or it would fall through and try to use CAS. If it was changed automatically this should point the authentication to ldap for previous ntlm users.

Show
Red Morris added a comment - I think someone has got confused with moving to 1.9. It was a bit confusing for those of us who had used Dans add-ons for 1.7/1.8, especially as NTLM operates from the LDAP folder. A check to see if the authentication method for the user is set to ntlm and changing it to ldap might help help with the transition. I had to do this manually or it would fall through and try to use CAS. If it was changed automatically this should point the authentication to ldap for previous ntlm users.
Hide
Permalink
Iñaki Arenaza added a comment -

This bug report clearly doesn't apply to 1.9 or above, as it doesn't use auth/ntlm/... at all. That directory was used by Dan Marsden's NTLM contrib plugin for 1.8 and below.

If we are running 1.9 or above, we need to remove the auth/ntlm directory completely and change the authentication type for all the users that previously used 'ntlm' to 'ldap', as Red Morris says.

If we are using 1.8 or below, the error message clearly states that this is a configuration issue.

So I'm closing this as 'not a bug'.

Saludos. Iñaki.

Show
Iñaki Arenaza added a comment - This bug report clearly doesn't apply to 1.9 or above, as it doesn't use auth/ntlm/... at all. That directory was used by Dan Marsden's NTLM contrib plugin for 1.8 and below. If we are running 1.9 or above, we need to remove the auth/ntlm directory completely and change the authentication type for all the users that previously used 'ntlm' to 'ldap', as Red Morris says. If we are using 1.8 or below, the error message clearly states that this is a configuration issue. So I'm closing this as 'not a bug'. Saludos. Iñaki.

People

Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Moodle. Try JIRA - bug tracking software for your team.