Interesting issue with crytpographic nameID and memcached on an SP

[Cantor, Scott E.]

On 8/5/11 5:53 PM, "Roy, Nicholas S" <nicholas-roy at uiowa.edu> wrote:
>The crypto nameID is significantly longer than the previous nameID
>format.  This is where the problem arises.  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.

Using AES128 generally keeps them to 255 or so, but it's true that the
storage contract does assume the key size is 255 or less, and using larger
AES probably would break it.

Can you file a bug on that? I can take a look at using some kind of hash
to shrink the storage key requirements down.

-- Scott