Azure function app custom domain TLS binding not working

Frank 5 Reputation points
2023-07-11T05:48:20.08+00:00

Hi,

I've a problem with uploading a .pfx certificate (with all the necessary requirements according the documentation) when trying to add a tls binding to a custom domain for a function app.

User's image

I've exported my keypair from keystore explorer as a .pfx format.

User's image

User's image

I tripled checked everything in the certificate & tried already different solutions.... root & intermediate are present, it's a global sign certificate.

Tried to do it with openssl pkcs12 -export command... nothing works.

This certificate is also used in the listener of the app gateway...

Does anyone have an idea?

Thanks & Kr!

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
5,911 questions
Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
8,936 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Frank 5 Reputation points
    2023-07-12T08:54:43.78+00:00

    Hi,

    Yes, we do meet all those requirements.
    I managed to upload the certificate by a different way now.

    I was able to import it in a keyvault and binding it to the app by the keyvault.

    Kr

    1 person found this answer helpful.
    0 comments No comments

  2. SnehaAgrawal-MSFT 22,706 Reputation points Moderator
    2023-07-12T08:36:36.2933333+00:00

    @Frank

    Thanks for reaching here!

    If you choose to upload or import a private certificate to App Service, your certificate must meet the following requirements:

    • Exported as a password-protected PFX file, encrypted using triple DES.
    • Contains private key at least 2048 bits long
    • Contains all intermediate certificates and the root certificate in the certificate chain.

    Further, to secure a custom domain in a TLS binding, the certificate has more requirements:

    • Contains an Extended Key Usage for server authentication (OID = 1.3.6.1.5.5.7.3.1)
    • Signed by a trusted certificate authority

    Could you please confirm above requirements, let us know if issue remains.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.