Feature: Deleting an Account #109

Closed
opened 2025-12-29 00:25:06 +01:00 by adam · 3 comments
Owner

Originally created by @lukas2511 on GitHub (May 30, 2016).

ACME allows deletion of accounts, this may be implemented in letsencrypt.sh in the future

Originally created by @lukas2511 on GitHub (May 30, 2016). ACME allows deletion of accounts, this may be implemented in letsencrypt.sh in the future
adam added the enhancement label 2025-12-29 00:25:06 +01:00
adam closed this issue 2025-12-29 00:25:06 +01:00
Author
Owner

@Exagone313 commented on GitHub (Jan 30, 2018):

As the spec for Account Deactivation says that the server should not revoke certificates, should dehydrated ask for that action to the user?

EDIT: It seems that what I linked is the draft for ACME v2 protocol and the v1 currently used does not include a way for deleting an account.

@Exagone313 commented on GitHub (Jan 30, 2018): As the spec for [Account Deactivation](https://ietf-wg-acme.github.io/acme/draft-ietf-acme-acme.html#rfc.section.7.3.7) says that the server *should not* revoke certificates, should dehydrated ask for that action to the user? EDIT: It seems that what I linked is the draft for ACME v2 protocol and the v1 currently used does not include a way for deleting an account.
Author
Owner

@ChliHug commented on GitHub (Dec 4, 2018):

I needed to deactivate some accounts and added a command to my dehydrated script. Here's the diff for anyone who also just needs a quick solution. And it really is minimal. It's ACME v2 only (v1 really does not have the option?), just sends the command to the server and does not change the status or check for it in the local json file. I'm not familiar enough with the script to add that.

@ChliHug commented on GitHub (Dec 4, 2018): I needed to deactivate some accounts and added a command to my dehydrated script. Here's the [diff](https://github.com/lukas2511/dehydrated/files/2641548/dehydrated_add_deactivate_command.diff.txt) for anyone who also just needs a quick solution. And it really is minimal. It's ACME v2 only (v1 really does not have the option?), just sends the command to the server and does not change the status or check for it in the local json file. I'm not familiar enough with the script to add that.
Author
Owner

@cpu commented on GitHub (Dec 4, 2018):

ACME v1 allows account deactivation. There's no way to delete an account in ACME v1 or ACME v2, only deactivation.

ACME v1 account deactivation works the same way as in ACME v2: Send an authenticated POST with the JWS body{"status":"deactivated"} to the account's URL.

@cpu commented on GitHub (Dec 4, 2018): ACME v1 allows account deactivation. There's no way to delete an account in ACME v1 or ACME v2, only deactivation. ACME v1 account deactivation works the same way as in ACME v2: Send an authenticated POST with the JWS body`{"status":"deactivated"}` to the account's URL.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#109