Open l0rn opened 6 years ago
I've got exactly the same problem. Did you find a solution?
My "solution" was to use openconnect instead, which worked fine. this seems to be just broken.
I ended up with updating the file ruby-saml-1.6.1/lib/onelogin/ruby-saml/settings.rb (I really know that this is worst practice) and changing the defaults to my settings. This works flawlessly.
Cheers
So, as it seems this line
config = DEFAULTS.merge(overrides)
in
ruby-saml/lib/onelogin/ruby-saml/settings.rb
merges the configs but does not add settings from the settings yaml file.
Any update on this? Still seems to be an issue with the latest docker containers. End up having to update the ruby-saml/settings.rb default as @wexstorm suggested, or have constant SAML errors.
Sorry for the late reply, was not getting notifications for issues on this repository. This issue should only arise if your auth provider callback (/auth/:name) (which is the name
) attribute in your settings.yml does not match.
Our OmniAuth strategy will try to look up the given provider based on the name in the callback URL, which is why the name must be set in order to find the key.
With that in mind, I can successfully create a response flow with SAML.
Please note that this repository is being integrated into https://github.com/opf/openproject for the next release 8.3., which will include an updated RubySAML https://github.com/opf/openproject/pull/7014
Please create a ticket at https://community.openproject.com and assign it to us if you are continuing to have issues with SAML!
Best, Oliver
The current dev (the version shipped with the official docker distribution of openproject) does not work.
When trying to authenticate with a saml provider the following message occures in the log:
Already run pry debugger and indeed the settings object does not contain most of the relevant configurations:
probably the api of the weakly defined dependency ruby-saml or omniauth-saml changed.