-
-
Notifications
You must be signed in to change notification settings - Fork 30
Acme account features #100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this! I think we'll want some tests for this in the pebble integration test. Please squash any fixup commits.
Would be helpful to add links to the specific RFC sections in the docstring/comments.
|
Documentation of the new API methods is added to the last commit with links into RFC 8555. You mentioned a pebble integration test. I need some guidance regarding pebble. Where should a testcase be placed in pebble.rs? Not shure if pebble supports contacts update or account key rollover. |
|
Just add new tests below the list existing test functions. Suggest just trying out whether Pebble supports these endpoints. |
|
Two pebble tests are added to this pull request. I tested locally on windows OS with the latest pebble release. |
djc
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! A few more small issues.
cpu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool :-)
|
Most review changes are fixed in this commit. I extended the readme to show the new features. |
I left a comment about the issue for the pebble test for contacts update. I think you just need to fix the contact you're using in the update. |
cpu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working through all the review feedback. Looks great.
|
@djc Thinking we should squash merge this one, oui? Do you want to do the honours? |
|
Fait accompli! |
That's awesome. Thanks for sharing :-) You did a great job. |
|
Thanks for your contribution! Hopefully this left you feeling motivated to contribute more in the future! |
This pull request adds account features and one fix to the instant-acme client:
The contact information that is part of the acme account is according to RFC 8555, section 7.3.2. The contact update payload includes a the contact information as for example an email address.
The account key rollover is according to RFC 8555, section 7.3.5. New credentials are created by the instant-acme client and updated on the acme server. The new credentials are returned to the caller for further usage.