Small
editing correction, the human readable explanation is never intended for
algorithmic processing, so the "or" should be an "and".
The <StatusReason> element is
intended to provide a human readable explanation of a Failure or
Error StatucCode and is not
intended for algorithmic processing.
-----Original Message-----
From: Charles Knouse
[mailto:]
Sent: Tuesday, November 20, 2001 6:14
PM
To: oasis sstc
Subject: [security-services]
StatusReason element
Here's my additions to core-20 for
the StatusReason we discussed at F2F#5. Following Simon's suggestion I made
the reason an element instead of an attribute, for more extensive reasons. I
borrowed most of the text from the SOAP faultstring discussion.
Regards,
Charles
2.6.2. Element <Response>
The <Response> element is extends the
ResponseAbstractType and specifies the status of the corresponding
SAML Request and a list of zero or more assertions that answer the request.
(NEW)
The <StatusReason> element is intended to provide
a human readable explanation of a Failure or Error
StatucCode or is not intended for algorithmic processing. It MAY be
present in a SAML Response; if present, it SHOULD provide at least some
information explaining the nature of the problem. Any localization of the text
of a <StatusReason> is outside of the scope of SAML.
(/NEW)
The following schema defines the <Response> element:
<element name="Response" type="samlp:ResponseType"/>
<complexType name="ResponseType">
<complexContent>
<extension base="samlp:ResponseAbstractType">
<choice minOccurs="0" maxOccurs="unbounded">
<element ref="saml:Assertion"/>
<element ref="saml:SingleAssertion"/>
<element ref="saml:MultipleAssertion"/>
</choice>
<element name="StatusReason" type="string" minOccurs="0"/>
(NEW)
<attribute name="StatusCode"
type="samlp:StatusCodeType" use="required"/>
</extension>
</complexContent>
</complexType>
</schema>