Igloo Software

[Hugo Slavia]

Thanks. That was helpful, I set it up for IDP-initiated SSO (the entityID
is the home URL for the community).

There are the following fields to fill in the Igloo SAML webform for the
response...with the default values listed (changes depending on the IdP
selected -- Shibboleth not listed).

What can be the values to insert for Shibboleth? I tried a number of
combinations -- including changing to mail, givenName, sn -- but no dice.

Identifier Path
/samlp:Response/saml:Assertion/saml:Subject/saml:NameID

Session Index Path
/samlp:Response/saml:Assertion/saml:AuthnStatement

Email Path
/samlp:Response/saml:Assertion/saml:AttributeStatement/saml:Attribute[@Name="Email"]/saml:AttributeValue

First Name Path
/samlp:Response/saml:Assertion/saml:AttributeStatement/saml:Attribute[@Name="FName"]/saml:AttributeValue

Last Name Path
/samlp:Response/saml:Assertion/saml:AttributeStatement/saml:Attribute[@Name="LName"]/saml:AttributeValue

On Thu, Jan 4, 2018 at 4:10 PM, Tom Scavo <trscavo at gmail.com> wrote:

> On Thu, Jan 4, 2018 at 5:38 PM, Hugo Slavia <hugoslavia101 at gmail.com>
> wrote:
> >
> > Their instructions are at:
> > https://customercare.igloosoftware.com/support/
> knowledgebase/articles/sso_saml_authentication
> >
> > But what do I enter on the IdP side of the equation for the metadata?
>
> If the SP doesn't provide metadata, you'll have to provide it yourself.
>
> > Can an IdP-initiated SSO occur without entry in the IdP metadata?
>
> IdP-initiated, SP-initiated, it doesn't matter, the IdP needs metadata
> for every SP.
>
> > What about how to
> > list which attributes for release?
>
> The SP entityID is in the SP metadata. Presumably attribute release
> will be driven by the SP entityID.
>
> Tom
> --
> For Consortium Member technical support, see https://wiki.shibboleth.net/
> confluence/x/coFAAg
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20180104/c476f0e3/attachment.html>