4 Commits (a1afbce50c182857d1ca2db0b4c00778bc3d6a46)

Author	SHA1	Message	Date
Herman Slatman	9d09f5e575	Add support for deleting ACME EAB keys	3 years ago
Herman Slatman	1dba8698e3	Use LinkedCA.EABKey type in ACME EAB API	3 years ago
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.	3 years ago
Herman Slatman	7dad7038c3	Fix missing ACME EAB API endpoints	3 years ago