Struct Revocations 

pub struct Revocations<'a> {
    pub database: &'a Arc<Database>,
    pub audit: &'a Auditor,
    pub notify: Option<&'a NotifyDispatcher>,
    pub revoker: Revoker<'a>,
}

Everything a revocation reaches.

Fields

database: &'a Arc<Database>

audit: &'a Auditor

notify: Option<&'a NotifyDispatcher>

The certificate’s profile’s dispatcher, when this process has one — a certificate_revoked notification is about the certificate, so it goes out however the revocation was asked for.

revoker: Revoker<'a>

Implementations

impl Revocations<'_>

pub async fn revoke_certificate( &self, profile: &str, cert_der: &[u8], reason: Option<u32>, pubkey: &[u8], account: Option<Account>, request: &RequestContext, ) -> Result<Order, RevokeError>

POST /revokeCert: revokes the certificate cert_der issued at profile, for a request signed by pubkey.

Authorized by either the order’s own account (RFC 8555 §7.6’s kid case, account being the one the JWS named) or the certificate’s key pair (the accountless jwk case). Every refusal past the point where a serial is known is an audit row.

pub async fn revoke_order( &self, id: &str, reason: Option<u32>, actor: Actor, client: ClientContext, ) -> Result<Order, RevokeError>

An operator’s revocation of order id’s certificate.

actor/client name the operator and where they asked from — not the certificate’s owner, since an administrative revocation attributed to the client would say the opposite of what happened. The refusals (NotFound, NotIssued, AlreadyRevoked, a bad reason) write no row: the operator is being told the state of things, unlike revokeCert’s refusals, which are a remote party being turned away.