the vendor's SP inplementation is PingFederate

[Paul Hethmon]

Have you asked them to use SAML2 instead? I've got a vendor I work with
regularly that uses Ping and don't have any problems.

Paul


On 6/22/12 6:05 PM, "Mark K. Miller" <max at psu.edu> wrote:

>
>If I knew anything about a PingFederate users list, I'd try that first.
>
>Oh well, here goes anyway...  I'm trying to federate with a vendor who
>has 
>a Ping Federate SP inplementation.  When they redirect to my Shibboleth
>IdP for AuthN, I log these entries in my idp-process.log:
>
>17:21:20.299 - WARN
>[edu.internet2.middleware.shibboleth.idp.profile.saml1.ShibbolethSSODecode
>r:72]
>              - No providerId parameter given in Shibboleth SSO
>authentication request.
>17:21:20.299 - WARN
>[edu.internet2.middleware.shibboleth.idp.profile.saml1.ShibbolethSSOProfil
>eHandler:222]
>              - Error decoding Shibboleth SSO request
>              org.opensaml.ws.message.decoder.MessageDecodingException:
>              No providerId parameter given in Shibboleth SSO
>authentication request.
>
>Of course there's no providerId parameter given in the Shibboleth SSO
>authentication request; it's a Ping Federate SSO authentication request.
>;-)
>
>Seriously though, my contact at this vendor has tried a few things, but
>still no providerId parameter is given.  Does anyone here have any clue
>what it takes in a Ping Federate SP config to make the SSO authentication
>request have a providerId parameter?
>
>Thanks!
>
>Max
>--
>To unsubscribe from this list send an email to
>users-unsubscribe at shibboleth.net