405 Method not allowed on staging

Which version of python are you using?

Python 3.7.6

What operating system and version of operating system are you using?

MacOS 10.14.6

What version of sewer are you using?

0.7.9

What did you do? (be as detailed as you can)

Using sewer as a library, when I try to generate certificates on the staging server I get a 405 Method not allowed error at get_identifier_authorization. When I use the production endpoint, the code executes normally.

I see #128 but that doesn’t seem to have been resolved using the staging endpoint.

Could this potentially be related to this deprecation?

What did you expect to see/happen/not happen?

A certificate to be generated.

What did you actually see/happen?

get_acme_endpoints
get_acme_endpoints_response. status_code=200
create_certificate_key
create_csr
create_account_key
intialise_success, sewer_version=0.7.9, domain_names=['x.com'], acme_server=https://acme-staging...
get_certificate
acme_register
make_signed_acme_request
get_acme_header
get_nonce
sign_message
acme_register_response. status_code=201. response={'key': {'kty': 'RSA', 'n': 'x', 'e': 'AQAB'}, 'contact': [], 'initialIp': 'x', 'createdAt': '2020-01-23T16:25:17.443639603Z', 'status': 'valid'}
acme_register_success
apply_for_cert_issuance
make_signed_acme_request
get_acme_header
get_nonce
sign_message
apply_for_cert_issuance_response. status_code=201. response={'status': 'pending', 'expires': '2020-01-30T16:25:19.34873624Z', 'identifiers': [{'type': 'dns', 'value': 'domain.com'}], 'authorizations': ['https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/...'], 'finalize': 'https://acme-staging-v02.api.letsencrypt.org/acme/finalize/.../...'}
apply_for_cert_issuance_success
get_identifier_authorization
get_identifier_authorization_response. status_code=405. response={'type': 'urn:ietf:params:acme:error:malformed', 'detail': 'Method not allowed', 'status': 405}
Error: Unable to issue certificate. error=Error getting identifier authorization: status_code=405 response={'type': 'urn:ietf:params:acme:error:malformed', 'detail': 'Method not allowed', 'status': 405}

Thanks for any help.

[mmaney]

I don’t consider it ready to pull yet. One issue is that I’m still trying to sort out what that empty payload for post-as-get is really supposed to be. I found an errata comment that makes me think what I have there now works only because of luck. Too much design by trial & error. 😦

[mmaney]

@devshane @kylejohnson I forgot to reference this in PR #174, which finally closes this.