WeBWorK Main Forum

authentication modes, their files, and their order

authentication modes, their files, and their order

by Andras Balogh -
Number of replies: 1

I am confused about the organization of the authentication files

localOverrides.conf

LocalOverrides.conf:
First:
$authen{user_module} = {
       "*" => "WeBWorK::Authen::LTIAdvanced",
       "*" => "WeBWorK::Authen::LDAP"
       "*" => "WeBWorK::Authen::Basic_TheLastOption"
};

then later: include("conf/authen_LTI.conf"); include("conf/authen_ldap.conf");

Should not the authentication configuration files loaded before specifying their use with $authen{user_module?


Another thing: why does authen_LTI.conf also has a part with $authen{user_module} ?


In reply to Andras Balogh

Re: authentication modes, their files, and their order

by Glenn Rice -

The design is generally for ease of configuration in most use cases.  Usually only one authentication module is used aside from the basic the last option.  In those cases the $authen{user_module} should not be set at all in localOverrides.conf, and the default values in the included authentication module should be used and are set up to cover most use cases with those modules.

Things are more complicated when multiple optional authentication modules are used.  For example, if LTI authentication is used in combination with LDAP, Saml2, or Shibboleth.  In those cases you usually need to use the setting in localOverrides.conf, and not the settings in the optional module conf files.

So in short, the organization is so that most of the time system administrators don't even need to edit the $authen{user_module} variable.