SP Metadata Cert Expiration

[Craig Pluchinsky]

That's what I figured. The vendor is using ping federate and the Metadata they gave me had a cert in it. Had to munge it around to work with encrypt assertions after they enabled it on their end. Looking at the cert it appears to be the cert for their website. When we originally started configuring I had to disable encrypt assertions and it worked. Maybe I'll go back to that since it may be less hassle if they change the cert. And the transport is encrypted. 

On August 3, 2016 5:19:49 PM EDT, IAM David Bantz <dabantz at alaska.edu> wrote:
>On Wed, Aug 3, 2016 at 12:34 PM, Tom Scavo <trscavo at gmail.com> wrote:
>
>> If you're an IdP running Shibboleth, then no, an expired cert in SP
>> will not affect you....
>>
>
>unless the SP starts using a different cert to sign requests or expects
>you
>to
>use a newer cert to encrypt your response. It's not the expired date
>per
>se, but
>the SP's reliance on a newer cert that can bite. That's happened to
>my IdP when I let an SP's certificate expire instead of replacing it on
>time.
>
>
>------------------------------------------------------------------------
>
>-- 
>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/20160803/ea6eff13/attachment.html>