Questions about upgrading SP v2 to SP v3

[Meiselman, Ellen]

Got it, and thank you for the speedy reply.

_________________
Ellen Meiselman
MLearning Team 
Michigan Medicine
Arbor Lakes, B2F3, C#119
Ann Arbor, MI
734-223-6206
 
 

On 3/25/19, 11:45 AM, "users on behalf of Peter Schober" <users-bounces at shibboleth.net on behalf of peter.schober at univie.ac.at> wrote:

    External Email - Use Caution
    
    * Meiselman, Ellen <emeiselm at med.umich.edu> [2019-03-25 16:32]:
    > I’m about to upgrade a couple of v2 SP’s to v3. It looks as if it is
    > possible to leave the old shibboleth2.xml configuration file in
    > place – is that a best practice? Or should I attempt to bring that
    > file up to date? I have a working example of one to use as a model.
    
    The project always recommends to upgrade the software and make sure
    your existing configuration continues to work -- any exceptions to
    that (things you would have to change prior to or during/after an
    upgrade) should be noted in the upgrading documentation.
    
    > If I do update to the v3 version of shibboleth2.xml, do I also now
    > need to separate out the signing/encryption keys?
    
    No.
    
    -peter
    -- 
    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

**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues