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

Location header in FinalizeOrder response #40

Open
ramonschriks opened this issue Jul 14, 2023 · 2 comments
Open

Location header in FinalizeOrder response #40

ramonschriks opened this issue Jul 14, 2023 · 2 comments

Comments

@ramonschriks
Copy link
Contributor

ramonschriks commented Jul 14, 2023

Issue mentioned in: https://community.letsencrypt.org/t/breaking-changes-in-asynchronous-order-finalization-api/195882

Our client implementation was relying on the finalizeOrder response, which should return the Order object.
However, it looks like the finalizeOrder response does not longer contain the location uri for the order as of today.

Therefor, we needed to update our implementation to resolve the order once again after finalising the order.


AcmeService.php -> finalizeOrder

      if ($response->getStatus() === 200) {
            return Order::fromResponse($response->getHeader('location'), $response->getBody()->buffer());
        }
@kelunik
Copy link
Owner

kelunik commented Jul 14, 2023

@ramonschriks Thanks for reporting! Do you have time for a PR?

@ramonschriks
Copy link
Contributor Author

Not sure if its not working under certain conditions, since the RFC 8555 tells us that the finalize order response (in case of valid) still gives us the location header containing the order URI

In our case, we resolve the order once again using the known order uri after finalising. So we ignore the response of the finalize order request.
Im currently not able to test the boulder API at this point to check the actual response in case of a valid finalisation of the order.

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

2 participants