[JIRA] Moved: (CPPOST-74) metadata provider should check validity before replacing old metadata

[Scott Cantor (JIRA)]

     [ https://issues.shibboleth.net/jira/browse/CPPOST-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Cantor moved SSPCPP-428 to CPPOST-74:
-------------------------------------------

          Component/s:     (was: Error Handling)
                       Metadata
    Affects Version/s:     (was: 2.4.3)
                       2.4.3
                  Key: CPPOST-74  (was: SSPCPP-428)
              Project: OpenSAML 2 - C++  (was: Shibboleth SP - C++)

> metadata provider should check validity before replacing old metadata
> ---------------------------------------------------------------------
>
>                 Key: CPPOST-74
>                 URL: https://issues.shibboleth.net/jira/browse/CPPOST-74
>             Project: OpenSAML 2 - C++
>          Issue Type: Improvement
>          Components: Metadata
>    Affects Versions: 2.4.3
>            Reporter: Ian Young
>            Assignee: Scott Cantor
>
> The SP currently accepts metadata from a remote publisher for use prior to checking validUntil.  This means that if for some reason it is exposed to expired metadata then it will replace previously downloaded metadata even though it is still valid.
> It would be better to perform the validUntil check (and other similar checks which might cause an aggregate to be largely rejected) before replacing previously downloaded metadata.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira