Scoped attributes available to other definitions?

[Baron Fujimoto]

On Fri, Jan 10, 2014 at 08:33:59PM +0000, Cantor, Scott wrote:
>On 1/10/14, 3:27 PM, "Baron Fujimoto" <baron at hawaii.edu> wrote:
>>
>>I've attempting to construct an email attribute from a previously defined
>>scoped attribute, but the resulting email attribute value only contains
>>the unscoped value.
>
>Most of the plugins only operate on "simple" values, they don't know about
>the scope. You would probably have to use a Script attribute and have it
>explicitly use the APIs to create and access values as
>ScopedAttributeValue objects.

Ok, mahalo for the confirmation/explanation.

Rather than the Script attribute route (since my javascript-fu is weak),
I think I've accomplished my goal with a Mapped attribute kludge. AFAICT
though, I can't directly encode the resulting attribute, so I do that in
a seperate definition.

===
    <!-- aacli_kludge_principal_to_email -->
    <resolver:AttributeDefinition xsi:type="ad:Mapped"
            id="aacli_kludge_principal_to_email"
            sourceAttributeID="principal">

        <resolver:Dependency ref="principal" />

        <ad:ValueMap>
            <ad:ReturnValue>$1 at hawaii.edu</ad:ReturnValue>
            <ad:SourceValue>(.+)</ad:SourceValue>
        </ad:ValueMap>

    </resolver:AttributeDefinition>
    <!-- /aacli_kludge_principal_to_email -->

    <!-- aacli_kludge_email -->
    <resolver:AttributeDefinition xsi:type="ad:Simple"
            id="aacli_kludge_email"
            sourceAttributeID="aacli_kludge_principal_to_email">

        <resolver:Dependency ref="aacli_kludge_principal_to_email" />

        <resolver:AttributeEncoder xsi:type="enc:SAML2String"
                name="urn:oid:0.9.2342.19200300.100.1.3" friendlyName="kludge_mail" />

    </resolver:AttributeDefinition>
    <!-- /aacli_kludge_email -->
===

-baron
-- 
Baron Fujimoto <baron at hawaii.edu> :: UH Information Technology Services
minutas cantorum, minutas balorum, minutas carboratum desendus pantorum