Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login
    1. Home
    2. clsa
    3. Posts

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    C Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 4
    • Groups 0

    Posts

    Recent
    • RE: ProGet on Windows ignores intermediate CA certificate in PFX file

      Hi Steve,

      i would put a hint in two places on this page:

      "3. Use a Free, Automated Issuing Service, such as Let's Encrypt with a tool like win-acme to get short-term certificates"

      All such Let's Encrypt certificates are issued by intermediate CAs. PFX files generated by ACME clients and directly loaded into ProGet would therefore cause the issue initially described. This is probably also the easiest approach to reproduce the issue.

      "2. To use a ".pfx" file that was exported from your certificate store"

      Based on my observations this would still require potentially involved intermediate CA certificates to be present in Windows' certificate store, that ProGet sends those to clients allowing them to validate the full chain.

      Thank you for addressing the problem this way.

      posted in Support
      C
      clsa
    • RE: ProGet on Windows ignores intermediate CA certificate in PFX file

      Hi Steve,

      sorry for my late reply. I'm working around this problem meanwhile by importing the PFX file content into Windows' certificate store (incl. intermediate CA certificate, of course) through a post-issuance script in my ACME client and pointing ProGet to that imported certificate instead of the PFX file.

      However i want to stress again, that my point is not about self-verification of the certificate. When using a PFX file including an intermediate CA certificate in ProGet on Windows, clients actually see certificate warnings in browsers, because the web server (=ProGet) doesn't send the intermediate certificate during TLS handshakes as required by RFC 8446, although it is present in the PFX file.

      I would still love to see a fix in a future release or at least a hint in the documentation, that this kind of setup cannot follow internet standards and therefore should not be used in production.

      Thanks.

      posted in Support
      C
      clsa
    • RE: ProGet on Windows ignores intermediate CA certificate in PFX file

      Hi Steve,

      thank you for your quick reply and the hint regarding registry.

      However i couldn't identify potentially unsuitable registry settings within reasonable time, so instead i did a counter-check by importing the very same PFX file into Windows' certificate store.

      I had to grant read permissions to "NETWORK SERVICE" for the imported private key, but this way the intermediate CA certificate is served to the clients properly.

      Interestingly when switching back to the PFX file in ProGet's config afterwards (+ service restart), clients still receive the intermediate CA certificate. Only after deleting the intermediate CA certificate from Windows' certificate store, ProGet starts complaining about "Error PartialChain: A certificate chain could not be built to a trusted root authority." (root CA certificate is available in Windows' certificate store all the time).

      This makes me think, that the current implementation doesn't read intermediate CA certificates from PFX files.

      posted in Support
      C
      clsa
    • ProGet on Windows ignores intermediate CA certificate in PFX file

      Impact: Clients cannot verify the certificate chain, because the server should always send the intermediate certificates as well based on RFC 8446.

      PFX content has been verified with OpenSSL and contains the full chain.

      Version: 2026.12, installed through InedoHub.

      Known bug?

      posted in Support
      C
      clsa
    • 1 / 1