Proposed text - Security Considerations - DoNotCacheCondition

["Hal Lockhart" <hlockhar@bea.com>]

This is in response to item 4e. on today's (5/20) agenda.

Current:

At the level of the SAML assertion itself, there is little to be said about
security concerns—most concerns arise during communications in the
request/response protocol, or during the attempt to use SAML by means of one
of the bindings. However, one issue at the assertion level bears analysis:
An assertion, once issued, is out of the control of the issuer.

This fact has a number of ramifications. For example, the issuer has no
control over how long the assertion will be persisted in the systems of the
consumer; nor does the issuer have control over the parties with whom the
consumer will share the assertion information. ...

Proposed:

At the level of the SAML assertion itself, there is little to be said about
security concerns—most concerns arise during communications in the
request/response protocol, or during the attempt to use SAML by means of one
of the bindings. The consumer is of course, expected to honor the validity
interval and the DoNotCacheCondition element if present.

However, one issue at the assertion level bears analysis: An assertion, once
issued, is out of the control of the issuer. This fact has a number of
ramifications. For example, the issuer has no control over how long the
assertion will be persisted in the systems of the consumer; nor does the
issuer have control over the parties with whom the consumer will share the
assertion information. ...

Hal