go-acme icon indicating copy to clipboard operation
go-acme copied to clipboard

Contact submission workflow?

Open jtolio opened this issue 9 years ago • 2 comments

I'm a bit confused how the contact flow works here. The ACME RFC protocol overview says that the ACME client should send along human contact information in the initial new registration request (https://letsencrypt.github.io/acme-spec/#rfc.section.4) but it seems like the only way to get the ACME server contact information with this library is to register a new key, then set the contact information on the returned Registration object, then update the registration.

I assume I'm more likely to be wrong about this than right, so what am I missing?

Thanks!

jtolio avatar Feb 07 '16 04:02 jtolio

So it looks like the spec allows you to send contact information initially (which it doesn't look like this client supports) or update it after the fact. You should be able to call UpdateRegistration with an updated registration object with the contact slice having some URI forms of contact. So what you had originally mentioned seems to be the way to go about it.

jameshartig avatar Feb 19 '16 23:02 jameshartig

it'd be nice to send in the initial request but it's great to know I'm not crazy. thanks!

jtolio avatar Feb 20 '16 01:02 jtolio