Originally created by @tzim-fr on GitHub (Jun 19, 2020).
Certigo service support ACME, but it requires support for "external account binding" (see section 7.3.4 in acme specs) at registration.
If I understand the specs correctly, only the newAccount request needs to be modified.
Is there plans to implement this feature ?
Originally created by @tzim-fr on GitHub (Jun 19, 2020).
Certigo service support ACME, but it requires support for "external account binding" (see section 7.3.4 in acme specs) at registration.
If I understand the specs correctly, only the newAccount request needs to be modified.
Is there plans to implement this feature ?
@lukas2511 commented on GitHub (Jul 5, 2020):
Looks easy to implement, but I have nowhere to actually test this...
Note to self: https://tools.ietf.org/html/rfc8555#section-7.3.4
@cpu commented on GitHub (Jul 6, 2020):
> I have nowhere to actually test this...
Pebble [supports external account binding](https://github.com/letsencrypt/pebble/pull/288).
Was going to set up Pebble anyway for automatic testing, will work on this feature when my test environment is back up! 👍
@lukas2511 commented on GitHub (Jul 6, 2020):
> > I have nowhere to actually test this...
>
> Pebble [supports external account binding](https://github.com/letsencrypt/pebble/pull/288).
Ah, @cpu to the rescue ;)
Was going to set up Pebble anyway for automatic testing, will work on this feature when my test environment is back up! :+1:
{"type":"urn:ietf:params:acme:error:externalAccountRequired","status":400,"detail":"The request must include a value for the "externalAccountBinding" field"}
@sigio commented on GitHub (Nov 23, 2020):
Zerossl is now live, which is sectigo's ssl service
CA ACME endpoint is at https://acme.zerossl.com/v2/DV90
Trying to use it returns:
{"type":"urn:ietf:params:acme:error:externalAccountRequired","status":400,"detail":"The request must include a value for the \"externalAccountBinding\" field"}
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @tzim-fr on GitHub (Jun 19, 2020).
Certigo service support ACME, but it requires support for "external account binding" (see section 7.3.4 in acme specs) at registration.
If I understand the specs correctly, only the newAccount request needs to be modified.
Is there plans to implement this feature ?
@lukas2511 commented on GitHub (Jul 5, 2020):
Looks easy to implement, but I have nowhere to actually test this...
Note to self: https://tools.ietf.org/html/rfc8555#section-7.3.4
@cpu commented on GitHub (Jul 6, 2020):
Pebble supports external account binding.
@lukas2511 commented on GitHub (Jul 6, 2020):
Ah, @cpu to the rescue ;)
Was going to set up Pebble anyway for automatic testing, will work on this feature when my test environment is back up! 👍
@sigio commented on GitHub (Nov 23, 2020):
Zerossl is now live, which is sectigo's ssl service
CA ACME endpoint is at https://acme.zerossl.com/v2/DV90
Trying to use it returns:
{"type":"urn:ietf:params:acme:error:externalAccountRequired","status":400,"detail":"The request must include a value for the "externalAccountBinding" field"}
@saz commented on GitHub (Nov 23, 2020):
You should set EAB_KID/EAB_HMAC_KEY in your config
@sigio commented on GitHub (Nov 24, 2020):
Thanks... that worked (as soon as I upgraded to latest version :P )
@lukas2511 commented on GitHub (Dec 10, 2020):
This is now implemented.