Changing the display name of the site shouldn't break the SAML private key pass

[Robert Lyon]

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

[Dmitrii Metelkin (dmitriim)]

Moodle has a specific setting for that password and it invalidates certificates when you change it. Also there is a proper description for users. Looks like we should go the same way.

[Mahara Bot (dev-mahara)]

Patch for "master" branch: https://reviews.mahara.org/11038

[Mahara Bot (dev-mahara)]

Reviewed: https://reviews.mahara.org/11038
Committed: https://git.mahara.org/mahara/mahara/commit/a795d53266563f847eda2e4e09d9459cdaad5cf5
Submitter: Robert Lyon (<email address hidden>)
Branch: master

commit a795d53266563f847eda2e4e09d9459cdaad5cf5
Author: Robert Lyon <email address hidden>
Date: Tue Jun 23 17:30:58 2020 +1200

Bug 1829108: Allow saml auth admin to set private key passphrase

Rather than just relying on the site name

Change-Id: I06e007b5a0ebe6f4dc7159ae3d60f6050c981828
Signed-off-by: Robert Lyon <email address hidden>