[JIRA] Resolved: (SSPCPP-376) Add a post-filtering hashing feature to shorten long attributes, namely ePTIDs

[Scott Cantor (JIRA)]

     [ https://issues.shibboleth.net/jira/browse/SSPCPP-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Cantor resolved SSPCPP-376.
---------------------------------

    Resolution: Fixed

Not an easy problem to address with current APIs. Not sure how useful this is, but for now, I adjusted the existing hash support so that NameID attribute objects can be filtered properly while still producing the hashed serialization (by remoting the hash operation to shibd).

Just not sure how useful it is to produce ugly, 40-byte hex identifiers or if they'll even fit such apps.

> Add a post-filtering hashing feature to shorten long attributes, namely ePTIDs 
> -------------------------------------------------------------------------------
>
>                 Key: SSPCPP-376
>                 URL: https://issues.shibboleth.net/jira/browse/SSPCPP-376
>             Project: Shibboleth SP - C++
>          Issue Type: Improvement
>          Components: Attribute Resolution / Filtering
>            Reporter: Thomas Lenggenhager
>            Assignee: Scott Cantor
>             Fix For: 2.5
>
>   Original Estimate: 1 day
>          Time Spent: 5 hours
>  Remaining Estimate: 3 hours
>
> Longish attribute values like the ones for eduPersonTargetedID can lead to problems within applications, which do not expect that long values and are not able to store them in their internal storage. A good example is JIRA itself.
> If the SP could generate a hash for such long attributes, the problem would disappear, without having to wait for a fix of the application itself.
> In order to still be able to track back user activity, it will be necessary that the SP logs (or stores?) enough details about hashes it generated.

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