SubjectDerivedAttributeDefinition Generated no values

[Wessel, Keith]

Thanks, Scott.

I did see the example further up on the page. I had somehow missed it. I'm sorry about that. I added an example with that specific attribute further down in the midst of the example for the subject resolution. If you feel it's redundant, feel free to rip it out, or let me know, and I will.

Keith


-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: Tuesday, October 13, 2020 12:49 PM
To: Shib Users <users at shibboleth.net>
Subject: Re: SubjectDerivedAttributeDefinition Generated no values

On 10/13/20, 1:34 PM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:

>    Thanks, Steve. It is, in fact, the attribute filter piece that was 
> needed. I'll try and add that to the instructions on the wiki if the editor will cooperate for me.

It's already there, with an example. It's possible examples that are default-collapsed don't register with a screen reader, that might be an issue.

> Scott, if I understand correctly, the attribute filter config piece is 
> needed regardless of if I used a subject derived attribute definition or a subject data connector, is that correct?

It's the same as the SP. It doesn't accept any attributes unless you tell it to.

> So, the only advantage to the data connector route is it would let me bulk map attributes coming in from the proxy?

Yes. About the only use case for SubjectDerivedAttribute now is really just this one use case when there's only one attribute used. Otherwise it's about the same as Simple, no longer of much use.

-- Scott


--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net