AttributeQuery : why SOAP binding ?

[valerie.bauche@bull.net]

In the SAML profile spec, I see an attributeQuery must be sent with a synchronous binding, such as the SOAP binding.
Why ?
I have a case where it should be useful to use a POST or Redirect Binding :
The user authenticate to the IDP with a smartcard. User attributes are in the smartcard, and we want the IDP to ask the user the permission to read the attributes in its smartcard and send it to the SP. So if we want the IDP to interact with the user, we need to send the attribute query with an asynchronous binding like POST or Redirect....
Is my use case not compatible with SAML2 spec ?

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.