** Changed in: mahara
Assignee: (unassigned) => Robert Lyon (robertl-9)
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask
on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1640308
Title:
Bad auth instance slows down login for all institutions
Status in Mahara:
Confirmed
Bug description:
If we have an auth instance in Mahara that needs to talk to a
thirdparty site and the connection can't be made then it slows down
the login for all institutions on the site.
Currently the only way to deal with this is to move users off the
badly functioning auth to another auth (like internal) and then delete
the bad auth.
What we really need to have is the ability to switch off an auth
instance to stop it causing problems and when the problems for it are
fixed then turn it back on again.
I'm envisaging that we add an 'active' column to the auth_instance
table so that every instance can be on/off (0/1).
Then for our db calls to auth things check that the auth_instance is
active as well as checking that auth is asctive.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1640308/+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
