Freshdesk SSO

Nate Klingenstein ndk at
Sat Aug 8 19:21:43 EDT 2015


You’ll probably want to mock up a metadata entry on their behalf and load it into your SP.  Changes to the anonymous relying party behavior can result in an extremely promiscuous IdP.

You might find the annotated example SP here to be useful as a starting point:

Hope this helps,

On Aug 8, 2015, at 4:59 PM, Martin, Brandon L <martinb at<mailto:martinb at>> wrote:

Hello again Shibboleth users,

I am working with Freshdesk<> as an SSO party. They don't provide a metadata file, so I am under the impression they need to be setup as an AnonymousRelyingParty. I found the following code to setup an anonymous party, but it looks to be Shibboleth V2. I've read through UpgradingFromV2<> but I still do not understand the conversion and am having a hard time finding examples.

<AnonymousRelyingParty provider=""
                           defaultSigningCredentialRef="IdPCredential" />

<security:Credential id="IdPCredential" xsi:type="security:X509Filesystem">


Is this possible in Shibboleth V3?

Thank you

Brandon Martin
martinb at<mailto:martinb at>
Peninsula School District
Data Integration Analyst

Ext: 3712
To unsubscribe from this list send an email to users-unsubscribe at<mailto:users-unsubscribe at>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list