[JIRA] Moved: (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:all-tabpanel ]

Scott Cantor moved SIDP-507 to SSPCPP-387:
------------------------------------------

          Component/s:     (was: Attribute Resolution)
                       Session Cache
    Affects Version/s:     (was: 2.3.3)
                           (was: 2.3.2)
                           (was: 2.3.1)
                           (was: 2.3.0)
                       2.4
                       2.4.1
                       2.4.2
                       2.4.3
                  Key: SSPCPP-387  (was: SIDP-507)
              Project: Shibboleth SP - C++  (was: Shibboleth IdP 2 - Java)

> 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.3, 2.4.2, 2.4.1, 2.4
>         Environment: Any that uses cryptographic nameID for stateless load balancing
>            Reporter: nsroy at uiowa.edu
>            Assignee: Chad La Joie
>            Priority: Minor
>
> 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