Public bug reported:
If we change the site name for a site that uses SAML it breaks the
ability to login via SAML
We can roll the certificates and delete old ones to fix this problem but
it means the IdPs will need to update their info about the SP
certificate so no one can log in until this is done.
We should have a static SAML private key that is part of the saml auth
plugin rather than rely on site name
** Affects: mahara
Importance: High
Assignee: Robert Lyon (robertl-9)
Status: In Progress
** 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/1829108
Title:
Changing the display name of the site shouldn't break the SAML private
key pass
Status in Mahara:
In Progress
Bug description:
If we change the site name for a site that uses SAML it breaks the
ability to login via SAML
We can roll the certificates and delete old ones to fix this problem
but it means the IdPs will need to update their info about the SP
certificate so no one can log in until this is done.
We should have a static SAML private key that is part of the saml auth
plugin rather than rely on site name
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1829108/+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
