issue with Salesforce and memcache storageservice

[Liam Hoekenga]

Hey folks -

We're using IdP 2.4.3 and the memcache storageservice plugin
(unimr-memcached-idp-2.4-rev218.jar + spymemcached-2.7.jar).

We're running into an issue where the session key being issued is too long
for the spy memcache implementation:

11:53:07.995 - XXX.XXX.XXX.XXX - DEBUG
[unimr.shib2.UniMrMemcachedStorageService:133] - storageService.get(
replay,
https://example.my.salesforce.com_2yXH_BiHmM6_STHvAyHiYsM8z6yLR4HP_lA94lj5IXktcoEq2dWTsKnS6iaJCKk1MPWSgcGpKraOAuPiOeMwNFQ2Rqdcy3exaDZSZAj8DodV7BnAt6ea8PJaEjEdblkhtsOQjMfvBDEBreKjFb7I3bIBKPPKdhpVhu3kdzZlagX7BTxDFY0s2B8lJsULn6jgfBhj9cq9epgOSIookTzaKlADAZfCFow)
called.
11:53:08.012 - XXX.XXX.XXX.XXX - ERROR
[edu.internet2.middleware.shibboleth.common.profile.ProfileRequestDispatcherServlet:88]
- Error occurred while processing request
java.lang.IllegalArgumentException: Key is too long (maxlen = 250)

I'll poke the people at DFN-AAI, but I was wondering if anyone has run into
this before?  Can Salesforce be configured to use shorter keys?  Can the
keys be reduced in length (via hashing?) before they're sent to the storage
service?

Liam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20150127/386095c3/attachment.html