Closed natewallis closed 6 years ago
Are you using the latest samly_simplesaml? If so, there is no need to modify the saml20-sp-remote.php
directly. The setup/params/params.yml
should be modified appropriately and docker-compose restarted.
Check the logs:
docker-compose logs setup
docker-compose exec idp sh
cat /tmp/simplesamlphp.log
BTW, not related to this issue, SimpleSAMLPhp released a new version. If you want to move to that, you might want to run ./build.sh
to create a new docker image (after removing the current images).
Thanks..
All worked as soon as I used the YAML config file. Not sure what I did to blow it up, but I'll stick with that for now.
Updated the migration instructions with an item covering samly_simplesaml
.
The templates in the samly_simplesaml
are setup to how samlly_howto
expects
the configuration to be.
Closing this.
The default multi IDP config for 0.8 works fine, however, when I modify to my custom server names, I am still using the docker image specified in samly_howto which uses SimpleSaml.
The host I am trying to run from is: federation.mannequin.localhost
I have modified the saml20-sp-remote.php to contain the following:
Here are the development certificates I am using. Please note, that while the zip contains a file title mannequin_localhost.crt, I am renaming it when moving it to the SimpleSaml /setup/sp/federation_mannequin_localhost/ folder as sp.crt
certs_and_idp_metadata.zip
Here is my config in my phoenix project:
Any ideas what might be going on? Here is the error received in SimpleSaml..
I have debugged this to make sure its picking up my SP metadata in SimpleSaml. But couldn't quite figure out where the unhandled exception was being thrown. I haven't changed any other SimpleSaml config.