[JIRA] (IDP-1997) metadata driven configuration based on a list rather than a single value?

[Scott Cantor (Jira)]

Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) *commented* on IDP-1997 ( https://shibboleth.atlassian.net/browse/IDP-1997?atlOrigin=eyJpIjoiNDM5MDZiZDQ0ZWQ0NDc3N2FiMmM0MzljNGM2YzhjOGUiLCJwIjoiaiJ9 )

Re: metadata driven configuration based on a list rather than a single value? ( https://shibboleth.atlassian.net/browse/IDP-1997?atlOrigin=eyJpIjoiNDM5MDZiZDQ0ZWQ0NDc3N2FiMmM0MzljNGM2YzhjOGUiLCJwIjoiaiJ9 )

SAML Attributes should always be expressed with multiple AttributeValue elements, and we do that pretty consistently in all of the metadata-driven hooks.

The custom schemas occasionanally favor XML lists because Attributes are often more concise then Elements, but XML lists are formally defined by XML Schema, they’re whitespace-delimited.

Most places in Spring we inject lists, they just happen to be alternatively expressed in SpEL as delimited lists, and the property layer introduces other complications at times. But we don’t usually take those shortcuts unless we have to.

> 
> 
> 
> I’ve seen examples metadata driven configuration looking at a single
> value, but I’m not sure how we’d evaluate a single value that is actually
> a list of values?
> 
> 

Settings that are collections rely on multiple AttributeValue elements. e.g. settings like postAuthenticationFlows look like:

<saml:Attribute Name="http://shibboleth.net/ns/profiles/saml2/sso/browser/postAuthenticationFlows"
 NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri">
 <saml:AttributeValue>terms-of-use</saml:AttributeValue>
 <saml:AttributeValue>attribute-release</saml:AttributeValue>
</saml:Attribute>

Conditions that know how to process EntityAttributes also support multiple values inherently.

Not sure what specific example you’re wondering about.

( https://shibboleth.atlassian.net/browse/IDP-1997#add-comment?atlOrigin=eyJpIjoiNDM5MDZiZDQ0ZWQ0NDc3N2FiMmM0MzljNGM2YzhjOGUiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-1997#add-comment?atlOrigin=eyJpIjoiNDM5MDZiZDQ0ZWQ0NDc3N2FiMmM0MzljNGM2YzhjOGUiLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100206- sha1:1c596f6 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220824/966e3131/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-9b1f5002-6e18-4a80-86af-32dddce155f6
Type: image/png
Size: 341 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220824/966e3131/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-f9555157-6f90-48ad-bba6-c7bb626d9839
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220824/966e3131/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-f44d53a7-c2a5-45a5-a127-20fac0cfd985
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220824/966e3131/attachment-0005.png>