Chris Reynolds
Chris Reynolds
We've addressed this issue in the latest (2.2.0) release. You can _still_ use the insecure version of SimpleSAMLphp. However, now, if you are, you get an admin error notice saying...
With updated styles: Without
@msalle Don't worry about the PHPCBF failing action -- the lint check is passing so that workflow would not change anything anyway. The CircleCI tests are matrixed against different versions...
Makes sense to me 👍
@RayHollister Can you share what failed when you tried to use the Terminus command? Was there an error that was visible in the Workflow Log? Did you previously or do...
## Todo: * [ ] Write a "manual" installation workflow * [ ] Suggest Pantheon Secrets as a method for storing and fetching the API key
@scottbuscemi Was a BUGS ticket created for this? If so, can you update the title? I'm assuming it hasn't been resolved based on @nicholsonjf's last update.
Initial failures were due to the fixture version being newer than the "tested up to" version of the plugin. Bumped "tested up to" version and created #424 to make that...
@mklasen IIRC `internal` is the default state (e.g. "use OneLogin SAML"), and for the purpose of using SimpleSAMLphp it should be changed from the default to `simplesamlphp`, so I think...
Agree with @pwtyler that it _feels bad_ to merge this without confirming that Behat tests are running, so I would tentatively agree that this is blocked by #431. That said,...