* Oliver G <
o3.wes...@gmail.com> [2021-02-04 16:19]:
> The problem is my IdP send me back to my SP without asking for my
> credentials if ForceAuthn is not set and
> isAuthenticated false and getAttributes empty. If ForceAuthn is set, my IdP
> ask me to login but when it send
> me back to my SP isAuthenticated still false and getAttributes empty.
That's not "a problem" (that your IDP doesn't ask your for credentials
when you don't set ForceAuthn), that's called SSO and usually what
people want.
Also it has nothing to do with isPassive nor should any of that affect
what data the IDP will return or how SSP handles a resulting new session.
> When I try with SSP's built in web page. I see this behaviour:
> - On Edge & Chrome I got : ERR_TOO_MANY_REDIRECTS
No idea how you would manage to achieve that with only these browsers
(SameSite?) but (only) you can check those redirects, e.g. using the
SAMLtracer browser extension (though none of its SAML-decoding
features are required here).
> With the ohter browser I get the ERR_TOO_MANY_REDIRECTS page when I
> want to connect SSP as admin.
Only using admin auth, not even an external IDP?
That sounds like a server misconfiguration then.
> But don't know how to use it in my IdP configuration. All I did is
> set an entityID and a replyURL.
By definition that depends on the IDP implementation.
Some IDPs simply don't support SAML 2.0 Metadata for configuration,
they force you to understand and "parse" the SP's configuration
details and enter them into some GUI or web UI on the IDP side, often
with made-up/proprietary/abitrary terminology (so you'll have to guess
what they're actually asking for, when there's a standardized,
machine-readable format that avoids all that).
Case in point "replyURL" is not a technical term with a definition in
SAML. It's probably one of the ACS URL for the SP but then with what
protocol binding? (Being nit-picky here, for WebSSO the binding will
always be HTTP-POST.)
> Also seems like the replyURL is taken from the SP request and not
> from the IdP else SSP's built in web page should not work since on
> my IdP the replyURL is set to my index.php and not on SSP folder?
Per the SAML spec (profiles, 4.1.4.1, lines 594-597 in "merged":
https://www.oasis-open.org/committees/download.php/56782/sstc-saml-profiles-errata-2.0-wd-07.pdf)
the IDP must verify the URL it recieved as part of the authn request
(sent by the SP, or by some other, possibly nefarious, party).
Provisioning that URL to the IDP out-of-band (whether manually or
automatically via SAML 2.0 Metadata) allows the IDP to do that.
For continued discussion I'd recommend to limit your questions to one
speific thing and then open another thread about all the other things
in SAML you're wondering about.
-peter