Hello, a user may want to register to multiple CAs. You have to modify these parameters in the dehydrated config file, which are only really necessary during the registration process. EAB_KID and EAB_HMAC_KEY are unique for each CA account. I think it makes more sense as a CLI argument. Other ACME clients like acme.sh pass EAB as CLI arguments.
Contact e-mail: A user may want to use a different e-mail address for a particular CA. For example for Google Trust Services you'll probably want to use your gmail address that is tied to your Google Cloud account, and for Let's Encrypt a different e-mail.
EAB_KID and EAB_HMAC_KEY: These are fine in the config file if you just use one CA, but they are only really necessary one time, during registration. As I'm aware? If a user wishes to register with additional CAs, they'll have to keep manually updating the config file to reflect the new keys.
Hello, a user may want to register to multiple CAs. You have to modify these parameters in the dehydrated config file, which are only really necessary during the registration process. EAB_KID and EAB_HMAC_KEY are unique for each CA account. I think it makes more sense as a CLI argument. Other ACME clients like acme.sh pass EAB as CLI arguments.
Contact e-mail: A user may want to use a different e-mail address for a particular CA. For example for Google Trust Services you'll probably want to use your gmail address that is tied to your Google Cloud account, and for Let's Encrypt a different e-mail.
EAB_KID and EAB_HMAC_KEY: These are fine in the config file if you just use one CA, but they are only really necessary one time, during registration. As I'm aware? If a user wishes to register with additional CAs, they'll have to keep manually updating the config file to reflect the new keys.