On 03/10/2010 09:42 PM, Devan Goodwin wrote:
On Wed, Mar 10, 2010 at 9:51 PM, Adam Youngayoung@redhat.com wrote:
I should have posted to this list insted of imanage. Sorry for the dup postings, but I realized that I wouldn't get responses from the other list.
Right now there is a one to one relationship between consumer and certificate. THe id for the ConsumerIdentityCertificate is the same as the ID for the consumer. Thus, if we delete the consumer, we should delete the certificate.
Is this sufficient for revoke?
I would like to make sure we call the service so that if there is some future revocation, that we actually do it.
Part of me thinks that we should never throw away data: once we record a consumer, we should keep that information and just transform it into a "inactive" state, but I realize that complicates the logic, and potentially has an impact on Database size and performance.
So.. would deactivate be a POST to /consumers/uuid
?
and delete be a real delete?
--b k