intercept/attribute-release flow with attribute queries in v3

Cantor, Scott cantor.2 at osu.edu
Fri Dec 12 10:04:56 EST 2014


On 12/12/14, 1:50 PM, "Kaspar Brand" <kaspar.brand at switch.ch> wrote:

>Meanwhile I've started playing with the postAuthenticationFlows in beta
>1, in particular intercept/attribute-release. Was mostly working as
>expected, a minor issue first: the DOCTYPE declaration was dropped with
>beta 1 [1], which leads to unintended font sizing effects (size of
>attribute names and values too large, at least in Firefox), due the
>browser falling back to quirks mode. Re-adding a suitable DOCTYPE line
>(xhtml1-transitional, or xhtml1-strict perhaps) fixes the issue.

Using XHTML seemed to be wrong, so that would maybe imply the style sheet 
is itself wrong. I guess we can put the doctype back for now, but please 
file a bug so the style sheet gets looked at by somebody who won't stab 
their eyes out trying (i.e. not me).

>The second thing I observed is that the rightmost column on the
>attribute release page, which allows selecting/deselecting the
>to-be-released attributes, is working fine as long as it is used with an
>SSO profile with includeAttributeStatement="true" - but it doesn't
>really do what I would expect when the attributes are only retrieved via
>a subsequent backchannel query (i.e. when
>includeAttributeStatement="false"). In this case, all attributes are
>released, irrespective of what the user has selected/deselected on the
>user consent page. AFAICT, the attribute-release intercept flow is
>currently not meant to used with attribute queries, is that correct? Is
>this something which could be added for v3, or am I just trying to
>configure a setting which isn't intended to be supported?

AFAIK, it's working the way uApprove did (meaning yes, it doesn't support 
queries yet). Is that not true?

Since the default mode is client storage, and databases are a non-starter 
for 90% of the deployment base, I don't know that it will ever work widely 
with queries but there's a plan to extend the support if there is 
server-side  storage.

-- Scott



More information about the dev mailing list