intercept/attribute-release flow with attribute queries in v3

[Kaspar Brand]

On 12.12.14 16:04, Cantor, Scott wrote:
> 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).

Ok, done - https://issues.shibboleth.net/jira/browse/IDP-537

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

It's not an issue with the standard uApprove version, since it doesn't
support an individual selection of the to-be-released attributes. As
long as the user doesn't approve the release at least once, there's no
chance for an SP to query the IdP (even for queries based on targeted
IDs). uApprove JP (which supports per-attribute selection) apparently
uses a custom query handler for v2, as I just learned from
https://issues.shibboleth.net/jira/browse/IDP-465.

> 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.

Ah yes, forgot to mention that I'm using server-side storage
(JPAStorageService, to be precise). I'm not sure that client-side
storage for user consent settings is really useful.

Kaspar