RE: [saml-dev] asynchronous response on SAML over SOAP over HTTP

[Yuji Sakata <ysakata@rd.nttdata.co.jp>]

> Prateek pointed this out to me in person, regarding our thread about whether
> the notBefore/notOnOrAfter checks are necessary in the browser/artifact
> profile.  If a synchronous binding was used, and the responder could be
> trusted only to return timely assertions, then the requestor would not need
> to do validity-period checking.  This is probably true for any use of a SAML
> binding, not just the brower/artifact profile.
>  
> At the recent Interop, validity-period checking caused problems in parsing
> and time synchronization.  So maybe we should take advantage of synchronous
> bindings to avoid these.  A binding spec could say whether it's synchronou

I might be confused with the meanings of synchronous and asynchronous.

I think the usage is not impossible that "assertions are retrieved 
synchronously by means of SOAP binding and used synchronously".
For example, attribute assertion consumer is inclined to cache attribute 
assertions and re-use them as long as they are valid.
So, it might be good idea that we discuss separately with whether SOAP 
binding should be synchronous and whether validity-period checking isn’t 
required.

What do you think?

Best Regards,
----------------------------------------------
NTT Data Corporation
Yuji Sakata
Tel: +81-3-3523-8081
E-Mail: ysakata@rd.nttdata.co.jp
----------------------------------------------