[JIRA] Commented: (SSPCPP-387) Cryptographic nameID is longer than key length that memcache can handle

[Scott Cantor (JIRA)]

    [ https://issues.shibboleth.net/jira/browse/SSPCPP-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631#comment-13631 ] 

Scott Cantor commented on SSPCPP-387:
-------------------------------------

The code in the cache was already bounding names at 255 and truncating them for storage. So there's a problem with the memcache implementation, it's not supporting the required key size.

Technically, it needs to handle 255, but practically speaking, it just needs to report the allowed key size (and other sizes) via the new Capabilities interface. I have a question to the list soliciting information on that.

> Cryptographic nameID is longer than key length that memcache can handle
> -----------------------------------------------------------------------
>
>                 Key: SSPCPP-387
>                 URL: https://issues.shibboleth.net/jira/browse/SSPCPP-387
>             Project: Shibboleth SP - C++
>          Issue Type: Bug
>          Components: Session Cache
>    Affects Versions: 2.4, 2.4.1, 2.4.2, 2.4.3
>         Environment: Any that uses cryptographic nameID for stateless load balancing
>            Reporter: Nicholas Roy
>            Assignee: Scott Cantor
>            Priority: Minor
>             Fix For: 2.5
>
>   Original Estimate: 2 days
>          Time Spent: 2 hours, 30 minutes
>  Remaining Estimate: 1 day, 5 hours, 30 minutes
>
> The crypto nameID is significantly longer than the previous nameID format.  If an SP uses memcached, the xmltooling memcached extension seems to put the nameID value in a key, which is limited to 250 characters in length.  The xmltooling library fails to be able to persist the nameID value to memcache and you get a Shibboleth SP error page.  Scott mentioned he'd look at using a hash to decrease the size of the nameID value.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira