0

Error: "Certificate format requested not supported"

Hello,

Any idea what might cause the following error when requesting a new certificate on the staging server ( https://api.test4.buypass.no/acme/directory ) ?

 

{
 "code":400,
 "message":"MALFORMED_BAD_REQUEST",
 "details":"HTTP 400 Bad Request",
 "type":"urn:ietf:params:acme:error:malformed",
 "detail":"Certificate format requested not supported"
}

 

I am working on a custom client and up until that point everything works
fine: "new-reg" and "new-authz" for the domain is performed successfully.
But when I request a new certificate ("new-cert") I get the mentioned error message.

The same process and CSR format works without issues on Let's Encrypt, where a certificate is issued after the request.
The CSR format I use (PKCS #10) validates properly using OpenSSL

The certificate request is for a single domain with CN and subjectAltName set to the same value.

Any ideas what might be the issue?

Thank you.

6 replies

    • Andreea_Ramstadt
    • 6 yrs ago
    • Reported - view

    Any thoughts? Any help would be greatly appreciated 🙂

      • Andriy_Mahats
      • 6 yrs ago
      • Reported - view

      Hi Andreea Ramstadt 

       

      We have now added more logging to see what might cause the error.

      Please make request again on that environment.

       

      Regards,

      Andriy

    • Andreea_Ramstadt
    • 6 yrs ago
    • Reported - view

    Hi Andriy Mahats

    Thank you.

    I performed a request right now.

    Regards,

    Andreea

      • Andriy_Mahats
      • 6 yrs ago
      • Official response
      • Reported - view

      Hi Andreea Ramstadt 

       

      We have identified a bug in content negotiation on the new-cert endpoint
      and are working to fix this. Alternatively, you can specify "application/pkix-cert" as value of Accept Http header on request. This will allow you to proceed.
       

      Regards,

      Andriy

    • Andreea_Ramstadt
    • 6 yrs ago
    • Reported - view

    Hi Andriy Mahats

    Awesome. It works perfectly now.

    Many, many thanks!

     

    Regards,

    Andreea

    • Andriy_Mahats
    • 5 yrs ago
    • Answer
    • Reported - view

    Hi Andreea Ramstadt

     

    This bug was fixed.

     

    Regards,

    Andriy

Content aside

  • Status Answered
  • 5 yrs agoLast active
  • 6Replies closed
  • 276Views
  • 2 Following