Memory leak in SP 3.0.2?
Lukas Hämmerle
lukas.haemmerle at switch.ch
Fri Oct 12 02:54:36 EDT 2018
On 09.10.18 16:39, Cantor, Scott wrote:
> Lukas, are the affected SPs seeing routine signs in the log that
> there are failed attempts to resolve attributes in that handler?
Yes, for yesterday there are 16'900 lines in the SP's log like:
2018-10-12 08:09:51.147 INFO Shibboleth.AttributeResolver.Query [2695]
[default]: Conditional encryption of NameID in AttributeQuery failed: No
peer encryption credential found.
and 2'789 lines like:
2018-10-12 08:08:13.998 ERROR XMLTooling.SOAPTransport.CURL [2736]
[default]: supplied TrustEngine failed to validate SSL/TLS server
certificate
On 09.10.18 16:52, Cantor, Scott wrote:
> Also specifically interested in whether the configurations would be
> getting attributes out of metadata
Yes, we have configured a MetadataExtractor like this:
<AttributeExtractor type="Metadata"
errorURL="errorURL"
DisplayName="displayName"
InformationURL="informationURL"
PrivacyStatementURL="privacyStatementURL"
OrganizationURL="organizationURL">
<ContactPerson
id="technicalContactDisplayName"
contactType="technical"
formatter="$GivenName $SurName" />
<ContactPerson
id="technicalContactMailtoURI"
contactType="technical"
formatter="$EmailAddress" />
<ContactPerson
id="supportContactDisplayName"
contactType="support"
formatter="$GivenName $SurName" />
<ContactPerson
id="supportContactMailtoURI"
contactType="support"
formatter="$EmailAddress" />
<ContactPerson
id="administrativeContactDisplayName"
contactType="administrative"
formatter="$GivenName $SurName" />
<ContactPerson
id="administrativeContactMailtoURI"
contactType="administrative"
formatter="$EmailAddress" />
<Logo
id="smallLogo"
height="16"
width="16"
formatter="<img src='$_string' height='$height'
width='$width'/>"/>
<Logo
id="largeLogo"
height="60"
width="80"
formatter="<img src='$_string' height='$height'
width='$width'/>"/>
</AttributeExtractor>
> and/or the NameID being passed in
> for the subsequent query, per SSPCPP-739. I think the change I made
> at Etienne's request is leaking previously resolved attributes if
> the query fails. So it's all SWITCH's fault.
Mhh, yes the issue that Etienne reported in SSPCPP-739 was exactly
because of this SP :-)
Best Regards
Lukas
--
SWITCH
Lukas Hämmerle, Trust & Identity
GÉANT Project Task Leader of
eduGAIN Service Development - Research and Service Providers
Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland
phone +41 44 268 15 05, direct +41 44 268 15 64
lukas.haemmerle at switch.ch, http://www.switch.ch
More information about the dev
mailing list