Stored Persistent Id and SAML1
Cantor, Scott
cantor.2 at osu.edu
Wed Jun 25 12:57:16 EDT 2014
On 6/25/14, 12:42 PM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:
>Quick: non urgent question
>
>I note that there is no
>
>StoredPersistentNameIdentifierDecoder
>
>Is this is because stored persistent names are not meaningful in SAML1?
No, it's because they aren't in the subject of an assertion there, so they
never get decoded by any logic in the IdP.
On that topic in general, I have no attempted to do anything special about
encoding NameIDs into AttributeValues, which is how eduPersonTargetedID
works in SAML 1. The existing AttributeEncoders from V2 should be there,
and my assumption is they'll work, but we haven't tested that.
>I need something to put into the legacy StoredId <PrincipalConnector> and
>I'm currently working on the assumption that since this is an error I
>should
>create a dummy decoder which just throws an error if it is invoked..
Is there a legacy one for SAML 1? Or did it just not see a difference?
-- Scott
More information about the dev
mailing list