scripted attribute definition produces a null attribute
Sean McHugh
sean8sean at gmail.com
Thu Oct 11 10:50:43 EDT 2012
On Thu, Oct 11, 2012 at 10:36 AM, Peter Schober
<peter.schober at univie.ac.at>wrote:
> * Peter Schober <peter.schober at univie.ac.at> [2012-10-11 16:29]:
> [..]
>
> You could simply rename the AttributeDefinition's id attribute and
> fix up the rest of your attribute-resolver.xml (dependencies, I
> assume) and your attribute-filter.xml for releasing it based on the
> new internal name.
> Or change the variable name, if the scriping language employed
> supports variable with dashes in them, I don't know.
I still don't have all the terminology straight, but i think we're
expressing the same thing. What I've done is:
a.) change the Scripted Attribute Definition code and ID to match, and
changed it such that the variable name is a valid javascript var name
b.) added the following attribute, using the scripted attribute definition
as the sourceattribute and just releasing it under a new name
<resolver:AttributeDefinition id="zonza-groups" xsi:type="ad:Simple"
xmlns="urn:mace:shibboleth:2.0:resolver:ad"
sourceAttributeID="zonzagroups">
<resolver:Dependency ref="zonzagroups" />
<resolver:AttributeEncoder xsi:type="SAML1String"
xmlns="urn:mace:shibboleth:2.0:attribute:encoder" name="
http://grey.com/identity/zonza/zonza-groups" />
<resolver:AttributeEncoder xsi:type="SAML2String"
xmlns="urn:mace:shibboleth:2.0:attribute:encoder" name="
http://grey.com/identity/zonza/zonza-groups" friendlyName="zonza-groups" />
</resolver:AttributeDefinition>
So, does this make sense or is there a more elegant or efficient way to
achieve this ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20121011/8d03ba17/attachment-0001.html
More information about the users
mailing list