-
Notifications
You must be signed in to change notification settings - Fork 4
Metadata route does not work #3
Comments
@rnubel - Sorry for the delay in following up on this. It looks like omniauth/omniauth-saml#92 would allow us to monkey patch Perhaps we could instead make def on_metadata_path?
if options[:metadata_path].respond_to?(:call)
options[:metadata_path].call(env)
else
metadata_path = options[:metadata_path] || "#{request_path}/metadata"
on_path?(metadata_path)
end
end What do you think? |
@jturkel that looks like a good approach to me, as it's consistent with the other path matchers. |
@rnubel - Any interest in putting together a PR against omniauth-saml for the |
Is there any update on this issue? I need to show metadata for each provider. |
@rimshakhalid - This gem is deprecated in favor of the more generic https://github.com/salsify/omniauth-multi-provider gem. Checkout salsify/omniauth-multi-provider#4 for more details on this issue. |
The implementation of
other_phase
withinomniauth-saml
(see here) prevents this gem from having any sane way to modify that functionality and get the service-provider metadata generation feature to work. However, I've opened a PR (omniauth/omniauth-saml#92) which should let us override just that path-comparison logic to work as expected. Any thoughts?In the meantime, this very hacky monkeypatch in an initializer gets around the issue:
Coupled with a new route, to actually hit the "other" phase of Omniauth:
The text was updated successfully, but these errors were encountered: