Reviewed: https://reviews.mahara.org/c/mahara/+/13075 Committed: https://git.mahara.org/mahara/mahara/commit/38c8c5d04f06dafd1e0466a81ffc51aef66d5e64 Submitter: "Gold <[email protected]>" Branch: main
commit 38c8c5d04f06dafd1e0466a81ffc51aef66d5e64 Author: Robert Lyon <[email protected]> Date: Fri Aug 19 16:37:37 2022 +1200 Bug 1987027: Correctly save MNet parent auth on account creation Change-Id: I666a76e14ba84a4a1c036aff448c480039203ddb Signed-off-by: Robert Lyon <[email protected]> -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Matching subscriptions: mahara-contributors https://bugs.launchpad.net/bugs/1987027 Title: MNet failing to set parent auth correctly when creating account via MNet Status in Mahara: New Bug description: MNet has the ability to set a parent authentication instance so that when an account is created that is the value saved as 'authinstance' instead. However, there is a bug in the code where 'internal' gets saved every time. This is very old bug which has caused much head-scratching over the years. To test 1 Have a Mahara site that one can MNet into from something like a Moodle site 2 Have the MNet instance set up to have a parent auth that is not internal, say SAML 3 Have a person that doesn't have a mahara account log in via MNet jump link Expected new account created with their 'authinstance' being SAML option Actual new account created with their 'authinstance' being internal option To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1987027/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
