Conversation
This commit adds support for syncing ACME accounts with majordomo.
maraino
force-pushed
the
mariano/acme-accounts
branch
from
7795a6e to
65dfe01
Compare
| message CreateACMEAccountRequest { | ||
| string preferred_id = 1; | ||
| bytes jwk = 2; | ||
| ACMEAccount.Status status = 3; | ||
| repeated string contact = 4; | ||
| bool terms_of_service_agreed = 5; | ||
| } |
There was a problem hiding this comment.
Should there be a property to link this to a specific provisioner? I remember we used to allow an ACME account to be used with any ACME provisioner in the past, but I believe we changed that at some point?
There was a problem hiding this comment.
Not in this case, the intention is to sync accounts between different authorities, and those will have different provisioners.
There was a problem hiding this comment.
So the goal is to have linked authority X sync ACME accounts from provisioner Y to majordomo, so that linked authority Z get the accounts too, and for those to be active for all provisioners? And those authorities are totally independent; not clustered?
There was a problem hiding this comment.
Yes, they can be two different environments.
There was a problem hiding this comment.
I'm OK with this if it is a functional requirement, but it could result in surprising results to the end users.
3 participants
This commit adds support for syncing ACME accounts with majordomo.