v3 consent to attribute release : attribute hash function ?

[Cantor, Scott]

On 9/8/14, 1:37 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>
>Let me try to ask a better question. Given client-side storage for
>attribute consent which includes the DataSealer, how should an
>IdPAttribute be represented for values comparison ? The current way is
>hex encoding the SHA-256 hash of String values concatenated with a
>semicolon. I thought Base64 would be better than hex to reduce size.

Probably so.

>The current v3 code for consent does the same thing as v2, hex of the
>SHA-256 hash, but as written it does not work right now because
>IdPAttributeValues are not Serializable. So, wondering what to do, in
>light of the DataSealer.

You don't have to worry about that piece, it's done for you inside the
storage service impl. You just try and create reasonably sized records in
the storage service, basically. So if base64'ing improves that, that works
fine.

-- Scott