[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: ECP-related errata
Ran across another possible errata: In Conformance, Table 1’s ECP SSO row shows PAOS as
the binding for ECP to SP, SP to ECP to IDP, IDP to ECP to SP, and SP to ECP
communication. This doesn’t seem correct to me according to the
profile description.
Thus, we need to rework the rows a bit to make them correct.
Perhaps identifying the protocol messages as in browser web SSO? Row 1: HTTP Request from ECP to SP: Binding=PAOS Row 2: <AuthnRequest> from SP to ECP, <Response>
from ECP to SP: Binding=PAOS Row 3: <AuthnRequest> from ECP to IDP,
<Response> from IDP to ECP, Binding=SOAP I guess Rows 1 and 2 could be combined, since they’re
both PAOS bindings. However, the first uses no SOAP envelope/header
blocks; just HTTP header fields. Row 2 uses a SOAP envelope with SOAP header
blocks. I just couldn’t come up with a useful way to indicate this with
columns labeled “Message Flows” and “Binding”. Rob Philpott |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]