Herman Slatman 492256f2d7 Add first test cases for EAB and make provisioner unique per EAB ... Before this commit, EAB keys could be used CA-wide, meaning that an EAB credential could be used at any ACME provisioner. This commit changes that behavior, so that EAB credentials are now intended to be used with a specific ACME provisioner. I think that makes sense, because from the perspective of an ACME client the provisioner is like a distinct CA. Besides that this commit also includes the first tests for EAB. The logic for creating the EAB JWS as a client has been taken from github.com/mholt/acmez. This logic may be moved or otherwise sourced (i.e. from a vendor) as soon as the step client also (needs to) support(s) EAB with ACME.		2021-08-09 10:37:32 +02:00
..
acme.go	Add first test cases for EAB and make provisioner unique per EAB	2021-08-09 10:37:32 +02:00
admin.go	Addressing comments in PR review	2021-07-06 17:14:13 -07:00
handler.go	Change ACME EAB endpoint	2021-07-23 15:16:11 +02:00
middleware.go	Addressing comments in PR review	2021-07-06 17:14:13 -07:00
provisioner.go	Addressing comments in PR review	2021-07-06 17:14:13 -07:00