MNet failing to set parent auth correctly when creating account via MNet
Bug #1987027 reported by
Robert Lyon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Mahara | ||||||
21.04 |
Fix Released
|
High
|
Unassigned | |||
21.10 |
Fix Released
|
High
|
Unassigned | |||
22.04 |
Fix Released
|
High
|
Unassigned | |||
22.10 |
Fix Released
|
High
|
Unassigned |
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
Changed in mahara: | |
milestone: | none → 22.10.0 |
importance: | Undecided → High |
status: | New → Fix Committed |
no longer affects: | mahara |
To post a comment you must log in.
Patch for "main" branch: https:/ /reviews. mahara. org/c/mahara/ +/13075