aspnet/DataProtection

IXmlRepository contract to support removing elements

kosa-gyula-77 opened this issue · 1 comments

Currently in version 2.0.1 IXmlRepository implementers has to parse XElement and determine its expiration date in order to remove expired elements from the underlying storage. Elements otherwise just get added but not removed.

Proposal:

IXmlRepository - or a new interface - exposes an additional method that allows the XmlKeyManager to make regular house cleaning by removing expired and/or revoked elements, e.g.:

void RemoveElement(string friendlyName);

This issue was moved to dotnet/aspnetcore#2320