unsolicited sso

[Nate Klingenstein]

Chance,

It's definitely a general concept in SAML 2.0, most certainly not  
Shibboleth-specific.  Peter's message is generally right on.

You need the vendor to either:

A)  supply SAML 2.0 Metadata for their SP, in which case you can  
figure everything out on your own or with our help, or
B)  they need to supply an entityID(named providerId by Shibboleth, a  
name which might be slightly unique to us, but it's the same thing),  
an endpoint URL(as they've done), and optionally a target URL where  
they'd like your users to end up after authentication.

Odds are the company is not too familiar with the software they're  
using to offer SAML 2.0 support, but they should be able to find  
either A or B with (hopefully) any SAML 2.0 implementation in the world.

Take care,
Nate.

On Nov 1, 2011, at 18:35 , Chance Cox wrote:

> I may have mis-interpreted the whole concept here. Im sorry for  
> causing any confusion here but I have no idea what needs to happen  
> here. Basically this company said we don't use shibboleth we have a  
> SAML 2 endpoint. which is the url provided. That is all the gave me.  
> Am i mistaking in thinking that the ProviderId is a shibboleth  
> concept for shibboleth sp?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20111101/8ab0592a/attachment.html