You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like the strategy is for ADFS and either SAML or WSFed.
I am just curious if there is some reason to have those combined here and more specifically, since it is based on passport-saml, is there some benefit or reason I would use this repo (besides the fact that it's on the auth0) repo?
passport-saml is able to handle configuration for many different SAML IDP (including Shibboleth and ADFS). That would be my primary concern in switching up my proof of concept to use this version of a saml 2 passport strategy.
Thanks in advance (I'll probably switch anyways) just was hoping to keep my dependencies from crossing over. Would rather have my wsfed strategy if needed separate from my saml.
The text was updated successfully, but these errors were encountered:
It seems like the strategy is for ADFS and either SAML or WSFed.
I am just curious if there is some reason to have those combined here and more specifically, since it is based on passport-saml, is there some benefit or reason I would use this repo (besides the fact that it's on the auth0) repo?
passport-saml is able to handle configuration for many different SAML IDP (including Shibboleth and ADFS). That would be my primary concern in switching up my proof of concept to use this version of a saml 2 passport strategy.
Thanks in advance (I'll probably switch anyways) just was hoping to keep my dependencies from crossing over. Would rather have my wsfed strategy if needed separate from my saml.
The text was updated successfully, but these errors were encountered: