[JIRA] (IDP-1939) shibboleth.MemcachedStorageService broken after 4.2.0 upgrade

[Matt Borja (Jira)]

Matt Borja ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=6246cc2ea629c30068a5aea7 ) *created* an issue

Identity Provider ( https://shibboleth.atlassian.net/browse/IDP?atlOrigin=eyJpIjoiYWJkYTc3M2UwODg4NGQ1MmE3ZDhiYWZkN2JkYzY1NWIiLCJwIjoiaiJ9 ) / Bug ( https://shibboleth.atlassian.net/browse/IDP-1939?atlOrigin=eyJpIjoiYWJkYTc3M2UwODg4NGQ1MmE3ZDhiYWZkN2JkYzY1NWIiLCJwIjoiaiJ9 ) IDP-1939 ( https://shibboleth.atlassian.net/browse/IDP-1939?atlOrigin=eyJpIjoiYWJkYTc3M2UwODg4NGQ1MmE3ZDhiYWZkN2JkYzY1NWIiLCJwIjoiaiJ9 ) shibboleth.MemcachedStorageService broken after 4.2.0 upgrade ( https://shibboleth.atlassian.net/browse/IDP-1939?atlOrigin=eyJpIjoiYWJkYTc3M2UwODg4NGQ1MmE3ZDhiYWZkN2JkYzY1NWIiLCJwIjoiaiJ9 )

Issue Type: Bug Affects Versions: 4.2.0 Assignee: Unassigned Attachments: Screen Shot 2022-04-15 at 7.56.40 PM.png Components: Clustering Created: 15/Apr/22 10:59 PM Environment:

Servlet container is actually *Jetty 10.0.9*

Priority: Trivial Reporter: Matt Borja ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=6246cc2ea629c30068a5aea7 )

Hi,

After upgrading from IDP 4.1.6 to V4.2.0, I noticed that the application was no longer being loaded: servlet was returning a HTTP 503 error trying to access the metadata URL at /idp/shibboleth.

*jetty-base\logs\jetty.log:*
 {{ 
...
2022-04-15 19:40:36,667 - WARN [net.shibboleth.ext.spring.context.DelimiterAwareApplicationContext:591] - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'shibboleth.MemcachedStorageService': Lookup method resolution failed; nested exception is java.lang.IllegalStateException: Failed to introspect Class [org.opensaml.storage.impl.memcached.MemcachedStorageService] from ClassLoader [WebAppClassLoader

{Shibboleth Identity Provider}

@332796d3]
 }} 

Only after reverting the previously working production configuration back to shibboleth.StorageService (as shown below) was the application able to service SAML requests again:

*global.xml*
 {{ 
...
<!--
<bean id="shibboleth.MemcachedStorageService"
class="org.opensaml.storage.impl.memcached.MemcachedStorageService"
c:timeout="2">
<constructor-arg name="client">
<bean class="net.spy.memcached.spring.MemcachedClientFactoryBean"
p:servers="127.0.0.1:11211"
p:protocol="BINARY"
p:locatorType="CONSISTENT"
p:failureMode="Redistribute">
<property name="hashAlg">
<util:constant static-field="net.spy.memcached.DefaultHashAlgorithm.FNV1_64_HASH" />
</property>
<property name="transcoder">
<bean class="org.opensaml.storage.impl.memcached.StorageRecordTranscoder" />
</property>
</bean>
</constructor-arg>
</bean>
--->
...
 }} 

*idp.properties:*
 {{ 
...

* idp.session.StorageService = shibboleth.MemcachedStorageService
idp.session.StorageService = shibboleth.StorageService
...
 }} 

*jetty-base\logs\jetty.log:*
 {{ 
...
2022-04-15 19:41:52,413 - INFO [net.shibboleth.utilities.java.support.service.AbstractReloadableService:173] - Service 'shibboleth.LoggingService': Performing initial load
...
 }} 

Note: It was not enough to merely switch back to shibboleth.StorageService in idp.properties. I had to physically comment out the bean reference in global.xml before the IdP would load inside the servlet.

( https://shibboleth.atlassian.net/browse/IDP-1939#add-comment?atlOrigin=eyJpIjoiYWJkYTc3M2UwODg4NGQ1MmE3ZDhiYWZkN2JkYzY1NWIiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-1939#add-comment?atlOrigin=eyJpIjoiYWJkYTc3M2UwODg4NGQ1MmE3ZDhiYWZkN2JkYzY1NWIiLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100198- sha1:943baf4 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220416/13783c4b/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-7e1852a4-5e27-41d8-b2ea-49839a542d9d
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220416/13783c4b/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-trivial-0a1c6bfb-8a4f-4d29-88c2-309ddba00611
Type: image/png
Size: 563 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220416/13783c4b/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-01c89dab-fe51-44ba-967a-d28f40207541
Type: image/png
Size: 425 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220416/13783c4b/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-bb461cd6-8388-4b93-820c-ae655febdab6
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220416/13783c4b/attachment-0007.png>