auth saml config form does not work
Bug #670546 reported by
Rich Trott
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
High
|
Rich Trott |
Bug Description
Trying to use the config form for the auth:saml plugin/extension results in the form submission hanging and this appears in the error log:
PHP Fatal error: Cannot use object of type Pieform as array in /web/mahara/
I'm using a checkout of the current Master branch, 1.4.0dev. This problem does not appear to be in the release branches. I'm running Linux (RedHat CentOS 5) + Postgres.
description: | updated |
Changed in mahara: | |
status: | New → Confirmed |
Changed in mahara: | |
milestone: | none → 1.4.0 |
importance: | Undecided → High |
Changed in mahara: | |
status: | Confirmed → Fix Committed |
Changed in mahara: | |
assignee: | nobody → Rich Trott (richard-trott) |
Changed in mahara: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This seems like a bad bug. It looks like Mahara forces auth plugins to use the same function names (validate_ config_ options, save_config_ options) for plugin configuration and instance configuration, and then passes different parameters to the function depending on whether it's doing plugin or instance config. It only affects saml, because that's the only auth plugin that has plugin configuration.
To fix it without breaking any contributed plugins out ther, maybe we should make the auth instance config stuff in htdocs/ admin/users/ addauthority. php check for the existence of validate_ instance_ config_ options, save_instance_ config_ options functions and if they exist, use those instead of validate_ config_ options, save_config_ options.
Or else just change the names of all auth plugins to use validate_ instance_ config_ options etc., and just let any contrib auth plugins break.