Attribute consent flow activation based on relying party and user attribute

[Wessel, Keith]

As the page suggests, complex activation conditions are more readable in Javascript. I'm planning to do this; it also makes it easy to read in a flat file of entityIDs that aren't in groups or tags that we're lumping into requiring user consent but that we want to make special cases.

Question is this: what's the easiest way to get access to an attribute from inside a Javascript block in my custom activation condition bean? I've been spoiled writing Javascript inside the attribute resolver where my attributes are already pulled in for me.

Thanks,
Keith


-----Original Message-----
From: Wessel, Keith 
Sent: Thursday, July 21, 2016 8:59 AM
To: 'Shib Users' <users at shibboleth.net>
Subject: RE: Attribute consent flow activation based on relying party and user attribute

Duh. Missed this page yesterday when I was reading the section on the consent page about activation conditions. Had I seen it, I probably wouldn't have had to ask in the first place.

Thanks, Scott. This should get me on my way. If I come up with anything new and exciting, I'll add to the examples.

Keith


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Thursday, July 21, 2016 8:29 AM
To: Shib Users <users at shibboleth.net>
Subject: RE: Attribute consent flow activation based on relying party and user attribute

> So, sounds like the starting point, as I suspected, is going to be in the profile-
> intercept.xml. There are some good samples out there, but what kind of
> code would I use if I wanted to, say, match a given entity tag or (I know this
> isn't advisable long-term) entity group in the activation conditions?

https://wiki.shibboleth.net/confluence/display/IDP30/ActivationConditions

-- Scott

-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net