Skip to content
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

order state before submitting to finalize #26

Open
dolphinsd opened this issue Sep 3, 2019 · 4 comments
Open

order state before submitting to finalize #26

dolphinsd opened this issue Sep 3, 2019 · 4 comments

Comments

@dolphinsd
Copy link

Per the docs, order should be in Ready state before finalization.
See https://tools.ietf.org/html/draft-ietf-acme-acme-12#section-7.1.3

The code in AcmeHostedServices checks for PendingState, not readystate.

if (AcmeState.PendingStatus == _state.Order.Payload.Status)
{
_logger.LogInformation("Generating CSR");

@WouterTinus
Copy link
Member

I'm not familiar with the section of code that you are referring to, but "Generating CSR" suggests that that the order cannot possibly be "ready" yet, because the CSR has to be submitted before the certificate can be generated.

@dolphinsd
Copy link
Author

@WouterTinus , the code is from AcmeHostedServices sample, search for "Generating CSR"
We traced the steps, and in our case, order is in ReadyState before generating csr. Check the states in the docs for explanation.

@WouterTinus
Copy link
Member

You are right, this looks like a bug. Probably it works fine as long as the locally cached order object is not updated after submitting the authorization response(s), except when all host names just happened to have valid authorizations already (i.e. from a previous run) and so the new order immediately gets to the ready state.

@omnibasissupport
Copy link

Maybe related
#34

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants