This will:
1) make new crt and pem files under the right file names so that after the dns move they will be in the correct place and in theory just work
2) generate the sp xml metadata in the right shape. This is half working with the sp name but not the domain name bits in the xml
Fixed #615
Usage is go to the normal SP page and then enter an extra query param eg:
http://current.edu/auth/saml2/sp/metadata.php?baseurl=https://newdomain.com
It can also be useful to regenerate it (must be logged in as admin) while testing to make sure it is refreshed:
http://moodle.local/auth/saml2/sp/metadata.php?regenerate=1&baseurl=https://acme.com
This will: 1) make new crt and pem files under the right file names so that after the dns move they will be in the correct place and in theory just work 2) generate the sp xml metadata in the right shape. This is half working with the sp name but not the domain name bits in the xml
Rough test steps: 1) In your idp, ingest the new SP metadata such as http://moodle.local/auth/saml2/sp/metadata.php?regenerate=1&baseurl=https://acme.com 2) Allow what will be the new SP's entityid 2) Hack hosts or otherwise simulate a DNS change and voila login should continue to work