Upgrade from V2 to V3 - how to change to SHA1

[Ramaiah, Vanna G.]

I tried that. We have another issue of using 2 certs and not just one. That made it impossible of changing to the new relying party format.



-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Andrew Morgan
Sent: Wednesday, July 19, 2017 3:39 PM
To: Shib Users <users at shibboleth.net>
Subject: RE: Upgrade from V2 to V3 - how to change to SHA1 



Vanna,

How about updating your relying-party.xml file to the new format?  It's pretty easy to do.  You're not stuck on the legacy format just because you upgraded.

        Andy


On Wed, 19 Jul 2017, Ramaiah, Vanna G. wrote:

> Can you tell me how to change it globally?
>
>
> -----Original Message-----
> From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, 
> Scott
> Sent: Wednesday, July 19, 2017 3:04 PM
> To: Shib Users <users at shibboleth.net>
> Subject: Re: Upgrade from V2 to V3 - how to change to SHA1
>
>
>
> On 7/19/17, 2:54 PM, "users on behalf of Ramaiah, Vanna G." <users-bounces at shibboleth.net on behalf of ramaiah at musc.edu> wrote:
>
>> We upgraded from V2 to V3.3. We have one SP that cannot use SHA256.
>> How to change the signing configuration just for one SP? Shib wiki has document for the installation not for upgraded files. Please help.
>
> There is no support for changing it in the legacy relying-party format. Globally changing it back is undoubtedly possible, but I don't think I have ever worked out any particular way to do it.
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to 
> users-unsubscribe at shibboleth.net
>
>
>
>
>
> --
> To unsubscribe from this list send an email to 
> users-unsubscribe at shibboleth.net
>
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net