Computed ID Data Connector

Cantor, Scott cantor.2 at osu.edu
Fri Mar 28 10:07:04 EDT 2014


On 3/28/14, 10:05 AM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

>On 3/28/14, 10:04 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:
>
>>> >> 1. Does the IdP entityID enter into the actual computation?
>>> >
>>> > Yes
>>> 
>>> I was afraid of that. May I ask why that is and/or why that has to be?
>>
>>Ummm, to render the Computed ID unique per user and per entityID?  Are
>>you
>>wanting a computed Id which is opaque, per user but not per entity?
>
>The SP entityID is what you need to make it unique per entity in the sense
>that its usually needed, not the IdP's.

....unless of course the seed/source attribute value isn't scoped/unique
in some way globally. Which is obviously why it's hashing in the IdP name,
duh. Sorry.

-- Scott




More information about the users mailing list