RE: [security-services] Minutes for Telecon,Tuesday 23 July 2002 <KS> Re. JSR 155 </KS>

> 	What does this mean ? The question of WSDL for SAML 
> itself is a challenging proposition. SAML by nature would be 
> embedded in a higher level interaction. So what would WSDL 
> for SAML describe ? 

At this point, SAML by nature is only the SAML binding, which is a web
service interface. WSDL would describe the interface (SAMLRequest in a
SOAP envelope in, literal encoding, SAMLResponse back out).

Personally, I didn't see the value of using a SOAP tool and generating
that code; the overhead in "grokking" SOAP libraries was such that I
preferred to hand-crank it. But that was the point of the statement
about WSDL.

> 	No comments ;o) If so, what value could WSDL bring and 
> how would one translate the exchange to Java ? </KS>

See above. It doesn't have much to do with Java, apart from using Axis,
or Apache SOAP, or whatever, and using WSDL to generate code for the
binding.

-- Scott