-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revoking certificate fails when using different account than originally creating the certificate #398
Comments
Reading RFC8555 there are two cases where Account B can revoke a certificate created by Account A:
Pebble implements (2) and I'm able to successfully revoke that method using
What you're hitting, I think, is that Pebble does not implement (1): Lines 2561 to 2565 in 087582e
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I created a certificate with account A, but revoking the certificate with account B fails with the following error:
{
"type": "urn:ietf:params:acme:error:unauthorized",
"detail": "The certificate being revoked is not associated with account "1"",
"status": 403
}
(Of course, before trying to revoke all required identifiers are authorized in the account B)
I interpret the RFC8555 that using different account should be a permitted way to revoke a certificate.
Is my interpretation incorrect?
The text was updated successfully, but these errors were encountered: