Is it okay to NOT run with Artifact resolution and 8443

[Nate Klingenstein]

Brad,

That's an entirely reasonable decision, and one many deployers have  
made.  At the end of the day, it comes down to the SP's you want to  
talk to, and fewer of those are requiring SAML 1.x.  A couple more are  
requiring artifact for reasons we don't understand, but if you're not  
speaking to any of them, then no matter.

You'll want to be sure that the metadata you publish doesn't advertise  
support for protocols that you don't, well, support.

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.

Take care,
Nate.

On Sep 7, 2012, at 17:26 , Brad Hannah wrote:

> I am deploying a new IDP and would like to only enable the required  
> protocols. I am not clustering on my application server (Tomcat) and  
> as such would prefer not to use Artifact resolution. As I understand  
> it, if I don't use Artifact then I don't need to host on port 8443.  
> Is this correct?
>
> Is it unreasonable to disable this? Is it unreasonable to disable  
> SAML1x as well? I understand I may have a future service that only  
> supports SAML1x, but hypothetically if I wanted to, would I only  
> have to edit my idp-metadata.xml and remove any mentions of  
> artifacts and SAML1?
>
> Has anyone else done this?
>
> Brad

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20120907/c9dcf246/attachment.html