OIDC embeddedAttributes

[Wessel, Keith]

Thanks, Scott, that was my hunch, but I wanted to make sure. Ot sure, since that's the implied standard, if it's worth clarifying that in the documentation. I'd be happy to add it, but if there are many other properties that use a similar format that don't' currently clarify that, I'm not sure it's worth it. I was trying to think of another property with a comma-spearated list to compare against, but I can't think of any other than the additional property files to load which, I'm almost positive, says comma-separated in the docs.

One other question about the OIDC claim properties: I presume the values in those properties should be IDs in the attribute resolver configuration, not the OIDC clain names that they'l resolve to. So, if my attribute definition with id="mail" is encoded to the OIDC claim "email", I should list mail and not email in the property. Correct?

Thanks,
Keith


-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: Wednesday, July 21, 2021 5:10 PM
To: Shib Users <users at shibboleth.net>
Subject: Re: OIDC embeddedAttributes

On 7/21/21, 6:04 PM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:

>    Should the format of a value of this attribute along with its two related attributes about always including the
> IDToken and never including the userinfo, be a space-separated or comma-separated list of attributes?

Comma delimited. Space delimited is rare in a property, that's mostly only XML lists.

-- Scott


-- 
For Consortium Member technical support, see https://urldefense.com/v3/__https://shibboleth.atlassian.net/wiki/x/ZYEpPw__;!!DZ3fjg!vX-BDuroQzgIR07En2-0kd_SDc-WT8qRUH7LmHq9R_4T7NIvVvwOy8H1zp8_-qYasQ$ 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net