Is it okay to NOT run with Artifact resolution and 8443

[Peter Schober]

* Nate Klingenstein <ndk at internet2.edu> [2012-09-07 19:46]:
> It's easy enough to retrofit 8443 support onto an existing IdP
> anyway.  If you don't need it now, I wouldn't fret about it for now.

For much the same reason I usually recommend doing it now, while
you're at it, changing config files, restarting containers, etc.
Doing it now isn't too difficult and then you're all set once the need
comes up.

I still have it on my list to bug IdP admins from our constituency who
advertise 8443 but don't (at least) have the port open, though.

@Brad: Fyi, I currently run with support for 8443 but still always
push attributes. Even for those SPs who can't be bothered to fix their
broken session initiation or discovery to /not/ force the use of
legacy protocols between entities supporting SAML2 perfectly fine.
(I do nag those SPs about it, though. With varying degrees of success,
as you might imagine.)
-peter