<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Hi, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">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. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">If I do update to the v3 version of shibboleth2.xml, do I also now need to separate out the signing/encryption keys?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I’d really rather not right now since it will mean swapping metadata with our IdP.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Are the split keys a requirement of v3 or a best practice? I can’t tell from the wiki or the v3 file if it will work to use the old-style 1-key entry, or to use the same key name for the 2 different types
of key:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">For example, would this old-style entry work?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><!-- Simple file-based resolver for using a single keypair. --><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <CredentialResolver type="File" key="sp-key.pem" certificate="sp-cert.pem"/><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Or would this new-style entry work, using the same key in both places?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <!-- Simple file-based resolvers for separate signing/encryption keys. --><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <CredentialResolver type="File" use="signing"<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> key=" sp-cert.pem " certificate=" sp-key.pem "/><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <CredentialResolver type="File" use="encryption"<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> key=" sp-cert.pem " certificate=" sp-key.pem "/><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">_________________<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Ellen Meiselman<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">MLearning Team <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Michigan Medicine<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Arbor Lakes, B2F3, C#119<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Ann Arbor, MI<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">734-223-6206<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p>**********************************************************<br>
Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues </p></body>
</html>