uApprove -- Change Attribute Name Listed

[Joshua Brodie]

Example --- when DisplayName DisplayDescrption added to an attribute in
attribute-resolver.xml --- the attribute subsequently does not appear in
attribute-release.vm.

<resolver:AttributeDefinition id="uid" xsi:type="Simple"
xmlns="urn:mace:shibboleth:2.0:resolver:ad" sourceAttributeID="loginName">
               <resolver:Dependency ref="myLDP" />
               <resolver:DisplayName
xml:lang="en">Foo</resolver:DisplayName>
            <resolver:DisplayDescription
xml:lang="en">BAR</resolver:DisplayDescription>
            <resolver:AttributeEncoder xsi:type="SAML2String"

xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
                                 name="urn:oid:0.9.2342.19200300.100.1.1"
                                    friendlyName="uid" />
        </resolver:AttributeDefinition>

In 'attribute-release.vm' --- which is the function which triggers the
display of DisplayName & DisplayDescription above......

## attributeReleaseContext - context holding consentable attributes
## attributeReleaseFlowDescriptor - attribute consent flow descriptor
## attributeDisplayNameFunction - function to display attribute name
## consentContext - context representing the state of a consent flow
## encoder - HTMLEncoder class
## flowExecutionKey - SWF execution key (this is built into the
flowExecutionUrl)
## flowExecutionUrl - form action location
## flowRequestContext - Spring Web Flow RequestContext
## profileRequestContext - OpenSAML profile request context
## request - HttpServletRequest
## response - HttpServletResponse
## rpUIContext - context with SP UI information from the metadata
## environment - Spring Environment object for property resolution
#set ($serviceName = $rpUIContext.serviceName)
#set ($serviceDescription = $rpUIContext.serviceDescription)
#set ($informationURL = $rpUIContext.informationURL)
#set ($privacyStatementURL = $rpUIContext.privacyStatementURL)
#set ($rpOrganizationLogo = $rpUIContext.getLogo())
#set ($rpOrganizationName = $rpUIContext.organizationName)
#set ($replaceDollarWithNewline = true)

                   <tbody>
                            #foreach ($attribute in
$attributeReleaseContext.getConsentableAttributes().values())
                                <tr>

<td>$encoder.encodeForHTML($attributeDisplayNameFunction.apply($attribute))</td>
                                    <td>
                                        #foreach ($value in
$attribute.values)
                                            #if ($replaceDollarWithNewline)
                                                #set ($encodedValue =
$encoder.encodeForHTML($value.getDisplayValue()).replaceAll($encoder.encodeForHTML("$"),"<br>"))
                                            #else
                                                #set ($encodedValue =
$encoder.encodeForHTML($value.getDisplayValue()))
                                            #end
                                            #if
($attributeReleaseFlowDescriptor.perAttributeConsentEnabled)
                                                <label for="$attribute.id
">$encodedValue</label>
                                            #else
                                                $encodedValue
                                            #end
                                            <br>
                                        #end
                                    </td>


On 2 August 2017 at 10:37, Joshua Brodie <josbrodie at gmail.com> wrote:

> Thank you.....very good to have this.
>
> Is there a trigger in idp.properties -- or elsewhere -- to enable the
> human readable names to appear?
>
> We are using 3.3.1 and added the DisplayName & DisplayDescription (english
> only) -- after doing so the attribute itself also does not show up on the
> attribute consent page.
>
>
> On 28 July 2017 at 04:31, Daniel Lutz <daniel.lutz at switch.ch> wrote:
>
>> Joshua Brodie [28.07.17 05:18]:
>> > We have had it running for over a year -- but have been getting
>> feedback that the attribute names are too cryptic: cn,
>> > eduPersonEntitlement etc
>> >
>> > We have a link where users can bounced away to read what the attribute
>> names signify but the masses are still not happy.
>> >
>> > Is there any other potential to map the attribute names top something
>> more non-techie friendly -- without too much
>> > development?
>>
>> Note that uApprove is for IdP V2 and is not supported anymore.
>> IdP V3 has built-in support for user consent.
>>
>> For both, V2 and V3, you can configure human readable names per attribute
>> in the AttributeResolver configuration.
>> You need to add <DisplayName> and <DisplayDescription> elements to each
>> <AttributeDefinition>.
>>
>> In the uApprove manual [1], this is documented at "Customizations /
>> Attribute Names and Descriptions".
>> The uApprove distribution contains an example attributer-resolver.xml
>> file.
>>
>> If you use IdP V3, please refer to the documentation at [2] and [3].
>>
>> You can find examples for various attributes on the following page:
>>
>>   https://wiki.shibboleth.net/confluence/display/IDP30/Human+
>> Readable+Attribute+Names
>>
>> If you need the names in English only, you just need those <DisplayName>
>> and <DisplayDescription>
>> elements specifying 'xml:lang="en"'.
>>
>> - Daniel
>>
>>
>>
>> [1] https://www.switch.ch/aai/downloads/uApprove-manual/
>> [2] https://wiki.shibboleth.net/confluence/display/IDP30/Consent
>> Configuration
>> [3] https://wiki.shibboleth.net/confluence/display/IDP30/Attribu
>> teDefinitionConfiguration
>> --
>> To unsubscribe from this list send an email to
>> users-unsubscribe at shibboleth.net
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170802/dc4e64f6/attachment.html>