Closed cjen07 closed 6 years ago
That section of README needs to be more clear I guess.
When you are SAML enabling your application, you need to work with a SAML Identity Provider. Typically you would use a hosted service as your IdP. It is possible to have your own self-hosted SAML IdP as well if desired. Whichever IdP you choose to work with, you need to provide the metadata describing that IdP so that Samly
can communicate with that service.
In case you want to have your own IdP service during initial development, you could use the
samly_simplesaml
repo. The README instructions in that repo can be used to create a Docker based setup of SimpleSAMLphp IdP. The URL you mentioned would work with that Docker based SAML IdP setup.
If you are not using the IdP from samly_simplesamlphp
repo and working with some other IdP, get the required metadata from that Identity Provider.
Thanks a lot, I will try to follow samly_simplesaml
repo
My goal is to use the elixir/phoenix endpoint as IdP to integrate into Slack using saml 2.0 sso, I just succeed using SimpleSamlphp as IdP to integrate into Slack. I am going to dig more into samly. One question: can I use samly as a IdP host?
Sorry for the late response. Samly does not work as IdP. It is an SP library.
Looks like you are already able to use SimpleSAMLphp as IdP for your usage scenario.
Is there a technical limitation as to why Samly can't provide IDP endpoints for an authentication system written in Phoenix?
wget http://samly.idp:8082/simplesaml/saml2/idp/metadata.php -O idp_metadata.xml
in the tutorial the link is outdated, and I am stuck at this point