required friendlyName?

[David Langenberg]

Seems blackboard is not following the standard as they should be keying off
the name attribute rather than friendlyName.  Have you tried just adding
another encoder with a bogus name attribute & their required friendlyName?

Dave


On Mon, Jul 28, 2014 at 5:58 PM, David Bantz <dabantz at alaska.edu> wrote:

> I’m stumped by the following in the documentation for integration of
> BlackBoard Transact with Shibboleth:
>
> Blackboard Transact SP requires that the attributes required for mapping
> into the Blackboard Transact system be the following where the attribute
> friendly name cannot be changed as this is what Blackboard Transact SP uses
> to map the data returned:
>
> Then a bunch of  standard attributes are given, with
> unusual “friendlyName”s like:
>
> <resolver:AttributeDefinition xsi:type="ad:Simple" id="email"
> sourceAttributeID="mail">
> <resolver:Dependency ref="myLDAP" />
> <resolver:AttributeEncoder xsi:type="enc:SAML1String" name="
> urn:mace:dir:attribute-def:mail" />
> <resolver:AttributeEncoder xsi:type="enc:SAML2String" name="
> urn:oid:0.9.2342.19200300.100.1.3" friendlyName="BbSPEmailAddress" />
>
> </resolver:AttributeDefinition>
>
> Is there a way I can encode and release these standard attributes with the
> unusual friendlyNames short of creating a bunch of shadow attributes that
> differ from the norm only by id and friendlyName?
>
> Is it me, or does this represent a bizarre SAML implementation?
>
> David Bantz
> UAlaksa
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>



-- 
David Langenberg
Identity & Access Management
The University of Chicago
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140728/01722bb0/attachment.html