handnot2

What is the error/reason you see in the browser window? You will find something like: "access_denied ". https://github.com/handnot2/samly/blob/032281091ea933b925f86b537cacfbaa791bacc3/lib/samly/sp_handler.ex#L56 Check to make sure that the `base_url` and `entity_id` are setup correct...

Adding the following as a reference: #### Common Errors `access_denied {:error, :bad_recipient}` - Check the `base_url` in your `Samly` config setting under `indentity_providers`. `access_denied {:error, :bad_audience}` - Make sure that...

Do you have the need to add IdP provider dynamically? There is an issue related to that: #29.

I am planning to get to these PRs once the v1.0 release is out. Thanks for your patience.

The current config/metadata XML-in-files model may not be suitable in that dynamic world. I was thinking of addressing such a requirement after the 1.0 release. A PR that could move...

Edited title to change "error" to "warning". The entity descriptor XML you included shows that the "Single Logout" (SLO) endpoint is not included. This indicates that you cannot initiate a...

@hodak can you check the SAML requests sent to your IdP by using the SAML tracer firefox plugin? Do you see a SAML logout request going to your IdP even...

I am considering removing this warning when the SLO endpoints are not present in the IdP metadata XML file and instead do the following for local signout or SLO: +...

Sorry. Artifact resolution is not supported in `Samly`.

I don't know if there is enough interest for this. If there is, it might be possible to support SP initiated POST/REDIRECT followed by Artifact resolution from SP to IDP....