|
|
165.
|
|
|
``$cfg->externallogin = 'URL';``
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_php.rst:113
|
|
|
166.
|
|
|
You can overwrite the normal Mahara login page by providing an external one. This is useful if all people with access to the site shall log in via a different system and should be redirected there automatically.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_php.rst:115
|
|
|
167.
|
|
|
Be careful when you have multiple institutions turned on. If at least one institution does not log in via the same external login page, you cannot use this setting as people in that institution would not be able to log in to Mahara at all since they can never get to the login page that they need.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_php.rst:118
|
|
|
168.
|
|
|
:index:`If <single: Override external login>` you use the external login, you may need to override it at times, e.g. for troubleshooting the external authentication method or when it is not reachable. You can add a parameter at the end of the Mahara URL. You are then taken to the normal Mahara login screen.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_php.rst:120
|
|
|
169.
|
|
|
The parameter is ``?override=true``
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_php.rst:122
|
|
|
170.
|
|
|
For example, https://mahara.example.com/admin/users/search.php **?override=true**
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_php.rst:124
|
|
|
171.
|
|
|
It doesn't matter what value you add. You can use 'true' or '1' or anything else.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_php.rst:127
|
|
|
172.
|
|
|
insecuredataroot: Share the same dataroot with another Mahara
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_php.rst:136
|
|
|
173.
|
|
|
``$cfg->insecuredataroot = false;`` (default) or ``$cfg->insecuredataroot = true;``
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_php.rst:138
|
|
|
174.
|
|
|
You can enforce checking that files that are served have come from dataroot. You would only want to turn this on if you were running more than one Mahara against the same dataroot. If you are doing that, make sure you create separate dataroots for each installation, but symlink the artefact directory from all of them to one of them, and turn on 'insecuredataroot' on all the ones for which you created symlinks.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_php.rst:140
|
