[OASIS Issue Tracker] Updated: (SECURITY-18) PE: Discussion of metadata caching mixes in validity and is overly strict

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/SECURITY-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Cantor updated SECURITY-18:
---------------------------------

    Resolution: Proposal accepted by TC on 2/21/12 conference call.

> PE: Discussion of metadata caching mixes in validity and is overly strict
> -------------------------------------------------------------------------
>
>                 Key: SECURITY-18
>                 URL: http://tools.oasis-open.org/issues/browse/SECURITY-18
>             Project: OASIS Security Services (SAML) TC
>          Issue Type: Bug
>          Components: Metadata
>    Affects Versions: Version 2.0
>            Reporter: Scott Cantor
>             Fix For: 2.0 incorporating Approved Errata
>
>
> Section 4.3.1 of SAMLMeta includes text that mixes notions of validity with caching, and equates validUntil with cacheDuration in an overly strict way. This is reinforced by the language referencing HTTP 1.1 caching, which implies a more typical caching model that doesn't overlap with expiration of documents.
> I suggest we split the caching discussion into two sections, one on validity and the other on caching, so we properly address each with appropriate language.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira