v3 consent to attribute release : model terms-of-use as attribute ?
Cantor, Scott
cantor.2 at osu.edu
Tue Sep 30 14:25:19 EDT 2014
On 9/30/14, 2:22 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>
>Omitting the encoders from the attribute definition is what I started
>doing, but wasn't sure if that was a good idea.
I do this in production, it's a common trick.
>Like my response above, I figured it would be okay to resolve a single
>attribute in the TOU flow, but again wasn't sure if that would be
>confusing or conflating down-the-road.
No, I used it in at least two spots, in the canonicalication flow that can
use the resolver, and in the authentication process to resolve an
attribute that's used to filter the login flows to offer.
-- Scott
More information about the dev
mailing list