Documentation Request - Multi-Environment SP Configuration In Database

[psuomc]

Hello,

First, a bit of background on our organization. We have over a dozen Wordpress applications deployed to Pantheon, each having a multidev / dev / test / live setup.

We host our own Identity Provider which the Wordpress applications will use for authentication. We will be forcing the use of SAML authentication on the dev / test / live environments, and because of this, we will have three service providers set up for each application.

• https://dev.application.tld/sp
• https://stage.application.tld/sp
• https://application.tld/sp

The SAML client that we are using is SimpleSAMLphp.

A requirement has arisen that certain wp-saml-auth settings must be controlled by a site administrator (without access to code pushes), while certain settings must be set dynamically through registering a filter.

As it stands, as soon as we define a filter, the settings form is disabled, so site administrators cannot change the settings that they'll need to. Likewise, if we were to utilize the wp-saml-auth settings exclusively, then backporting the database from live to test or dev would cause an incorrect service provider to be configured for the target environment.

After reaching out to Pantheon Support regarding this, we were directed here to file a feature request and for further support.

--
In the meantime, we are planning on creating a custom settings form whose options are read by a custom filter that configures the wp-saml-auth options. Obviously, all of the custom code isn't an ideal solution, but should be able to get us by. If you have any advice that we may be able to use, please let us know.

Thanks.

[danielbachhuber]

Hey @psuomc,

Thanks for the detailed issue!

What you've described seems accurate to me. You're correct in that, at the moment, the inclusion of the filter means the settings panel is disabled.

One idea that comes to mind: allow some settings to be modified when the filter is in place, through a secondary filter where you define those editable settings.

The custom settings form also seems like a fine approach to me, although I can understand your desire to minimize custom code.