** Changed in: mahara
Status: Triaged => Fix Committed
** Changed in: mahara
Milestone: None => 1.6.0
** Changed in: mahara
Assignee: (unassigned) => Simon Story (simon-story)
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/1003980
Title:
SAML user autocreation can become impossible
Status in Mahara ePortfolio:
Fix Committed
Bug description:
It is possible to put yourself in a situation where users having users
auto-created by an authentication plugin is impossible.
By design, for auto-creation to happen, all institutions must be
registerallowed = 0 .
By design, when an authentication plugin is added to an institution,
registerallowed is set to 0. But it is not set for all institutions,
if multiple exist.
Once an authentication plugin is added to an institution, via the web
interface the control to toggle registerallowed for an institution is
hidden.
To reproduce from a fresh installation of Mahara:
Create an institution
Set config item usersuniquebyusername = 1
Add and configure an authentication plugin
Attempt to login with with a new user that should autocreate, which will fail
because the 'mahara' institution will still have registerallowed = 1
To workaround:
Connect to the database and set registerallowed = 0 for all institutions, eg
'UPDATE institution set registerallowed = 0 ;'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1003980/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~mahara-contributors
Post to : mahara-contributors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mahara-contributors
More help : https://help.launchpad.net/ListHelp
