tag:blogger.com,1999:blog-12447072.post116135244039965078..comments2024-02-13T08:56:52.521-05:00Comments on ConnectID: SAML =/= SOAPPaul Madsenhttp://www.blogger.com/profile/08489111023182783403noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-12447072.post-14720521890322595312007-02-04T06:59:00.000-05:002007-02-04T06:59:00.000-05:00Could you in a future blog entry comment on WS-XAC...Could you in a future blog entry comment on WS-XACML and how it can help make user-centric identity better?James McGovernhttps://www.blogger.com/profile/10192703428650911093noreply@blogger.comtag:blogger.com,1999:blog-12447072.post-62345876679652425832007-02-02T20:52:00.000-05:002007-02-02T20:52:00.000-05:00You're right, Paul, SOAP is not required, but it's...You're right, Paul, SOAP is not <b>required</b>, but it's easy to see why Eric (and others) make that association. Most implementations of SAML V1.1 employ either Browser/Artifact or attribute query, both of which require SOAP. On the other hand, emerging implementations of SAML V2.0 seem to be focusing on Browser/POST, which does not require SOAP. It may be too late to undo the Tom Scavohttps://www.blogger.com/profile/09863361468172508607noreply@blogger.comtag:blogger.com,1999:blog-12447072.post-52597093219195370502007-02-02T08:01:00.000-05:002007-02-02T08:01:00.000-05:00Yes, I have never had an issue using SAML with my ...Yes, I have never had an issue using SAML with my HTTP connection management system and HTML rendering software. Oops, I mean Firefox.Anonymousnoreply@blogger.com