SP Metadata cannot be generated without a config XML file in place

[shadyvb]

The module expects a config file to exist, and falls back to the default file in .sso/config from the skeleton project, which doesn't necessarily exist on all installations.

Steps to reproduce:

1. Remove the .config/sso/saml-idp-metadata.xml file
2. Try to generate the SP metadata XML by visiting https://site/sso/metadata

You should see the SP metadata XML file generated, but right now it errors out with Invalid SSO settings. Contact your administrator.

The solution would be to move the default file to the module directory to ensure it always exists, and load it from there, and remove it from the skeleton project.

Related to support request: https://humanmade.zendesk.com/agent/tickets/5673

[roborourke]

I'm a bit lost, the skeleton project doesn't contain any sample metadata file at all, you have to create it as far as I knew - you get the file from your SAML provider and add it to your project. When I set this up locally and tested I had to spin up the local docker container, get the file contents and create it, then I could proceed from there.

Is this about using the site itself as the SAML provider? I didn't think the plugin had that ability.

[shadyvb]

You're correct, see #88 (comment), previously I was asked to provide the SP metadata in order to get the IdP one, apparently there was a misunderstanding there or a different process maybe, can't remember the details.

I closed the PR and the next steps would be:

• Update the plugin to provide a way for admins to view the integration values ( redirect, acs urls, etc ), and update docs to reference that.
• Remove references to the testing file and instructions, should already exist within the plugin

[roborourke]

I think I'm with you now, browsing to /sso/metadata gives me the right info though but agree we could maybe expose some means of directly downloading that via the admin. This module I think hides the UI as you noted so we can look at just showing that again - where possible what we've done is hide parts of the UI that have configured through code, but otherwise show them.

[roborourke]

Closing out as the docs were updated in #89 - it seems it's intended behaviour to require the config XML in order to generate the metadata.