Réf. : RE: Réf. : RE: [saml-dev] Réf. : RE : [saml -dev ] AttributeQuery : why SOAP binding ?

[valerie.bauche@bull.net]

It is now clear that the needed attributes will be dynamic...
Why should I make an extension in AuthnRequest while the AttributeQuery has all the functionalities I need...
It seems more simple to authorize a POST binding for attributeQueries rather than to extend the authnRequest !

Valérie BAUCHE
Ingénieur en développement de solutions de sécurité
Bull, Architect of an Open World TM
Tél : 02 41 93 57 09
http://www.bull.com

Bull recrute : http://www.bull.fr/emploi 

Ce message contient des informations confidentielles, couvertes par le secret professionnel ou réservées exclusivement à leur destinataire. Toute lecture, utilisation, diffusion ou divulgation sans autorisation expresse est rigoureusement interdite.
Si vous n'en êtes pas le destinataire, merci de prendre contact avec l'expéditeur et de détruire ce message. 

This e-mail contains material that is confidential for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited.
If you are not the intended recipient, please contact the sender and delete all copies.

"Scott Cantor" <cantor.2@osu.edu> 04/11/2008 16:55

Pour :        <valerie.bauche@bull.net>         cc :        <saml-dev@lists.oasis-open.org>         Objet :        RE: Réf. : RE: [saml-dev] Réf. : RE: [saml-dev] AttributeQuery : why SOAP binding ?

> I'm not sure... I have to precise this point with my client. If it is
static
> the solution Metadata + an AttributeConsumingServiceIndex seems correct,
but
> if it is dynamic it won't work.

An extension for that (in an AuthnRequest) is trivial. Nobody has bothered
to write one up. That tells me people aren't serious about it.
 
-- Scott