<html xmlns:v="urn:schemas-microsoft-com:vml" 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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I know I’m not Scott, but I had a v3 config working with ssl defined as disabled. That worked fine (barring the SAML1 bit, which is why I carried on tinkering,
without taking a snapshot, and broke it – waiting for a support response on what I’ve done to Jetty).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Dave<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#1F497D">_________________________________________________<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#1F497D">Dave Perry<br>
eLearning Technologist, Hull College Group<br>
<br>
Room L34 - Queens Gardens Library<br>
Wilberforce Drive, Queen's Gardens, Hull, HU1 3DG<br>
Extension 2230 / Direct Dial 01482 381930<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#1F497D">* Need a fast reply? Try
<a href="mailto:elearning@hull-college.ac.uk"><span style="color:blue">elearning@hull-college.ac.uk</span></a> *<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> users [mailto:users-bounces@shibboleth.net]
<b>On Behalf Of </b>NPTabunakawai<br>
<b>Sent:</b> 12 May 2015 07:45<br>
<b>To:</b> Shib Users<br>
<b>Subject:</b> Re: idp.authn.LDAP.sslConfig set to jvmTrust odity<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt">
Hi Scott, I'm facing similar issues with ldap.properties and would like to ask, is it possible to retrieve attributes without any TLS/SSL configuration?(and without ldap-server.crt) Or should idp.authn.LDAP.sslConfig and trustCertificates always be defined?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt">On Tue, May 12, 2015 at 6:08 AM, Cantor, Scott <<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">On 5/11/15, 1:57 PM, "Cantor, Scott" <<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>> wrote:<br>
<br>
>On 5/11/15, 1:09 PM, "Jeffrey Crawford" <<a href="mailto:jeffreyc@ucsc.edu">jeffreyc@ucsc.edu</a>> wrote:<br>
><br>
>>The first scenario is sort of hit or miss so let me figure that one out, but the second issue trying to use the resolver is pretty consistent:<br>
>><br>
>>In ldap.properties<br>
>>idp.authn.LDAP.sslConfig = jvmTrust<br>
>>idp.authn.LDAP.trustCertificates = %{idp.home}/credentials/ldap-server.crt<br>
>><br>
>>However ldap-server.crt file doesn't exist:, then excecute:<br>
>>shibboleth-idp/bin/reload-service.sh -id shibboleth.AttributeResolverService<br>
><br>
>That should happen on start up anyway, it shouldn't take a reload.<br>
<br>
I just tested with a resolver connector using that property with the property set to a non-existent file, and the IdP starts but with a failed resolver service, no reload involved.<br>
<br>
If you want to fail outright, change the failFast property on that service.<br>
<br>
It's behaving as designed as far as I can see, modulo the question of whether we can accomodate comment it out, which is much harder.<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><br>
-- Scott<br>
<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">
users-unsubscribe@shibboleth.net</a><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
</div>
<div><hr /></div><div><font color="#999999" size="2"><font face="Arial">This message is sent in confidence for the addressee </font><span style="font-family: Arial;">only. It may contain confidential or sensitive </span><span style="font-family: Arial;">information. The contents are not to be disclosed </span><span style="font-family: Arial;">to anyone other than the addressee. Unauthorised </span><span style="font-family: Arial;">recipients are requested to preserve this </span><span style="font-family: Arial;">confidentiality and to advise us of any errors in </span><span style="font-family: Arial;">transmission. Any views expressed in this message </span><span style="font-family: Arial;">are solely the views of the individual and do not </span><span style="font-family: Arial;">represent the views of the College. Nothing in this </span><span style="font-family: Arial;">message should be construed as creating a contract.</span></font></div><div><font face="Arial" color="#999999" size="2"><br /></font></div><div><font face="Arial" color="#999999" size="2">Hull College owns the email infrastructure, including the contents.</font></div><div><font face="Arial" color="#999999" size="2"><br /></font></div><div><font face="Arial" size="2" color="#00cc33">Hull College is committed to sustainability, please reflect before printing this email.</font></div><div><hr /></div>
</body>
</html>