Azure Functions
An Azure service that provides an event-driven serverless compute platform.
The remote certificate is invalid according to the validation procedure: RemoteCertificateNameMismatch
Sarish Tabish Sayyed
60
Reputation points
I am getting this error in a function app: The remote certificate is invalid according to the validation procedure: RemoteCertificateNameMismatch
These are the certificate details:
subjectName: permissionsgatewayapi.trafficmanager.net
hostNames: permissionsgatewayapi.trafficmanager.net
The DNS actually has http in it so will the subjectName and hostName require http as well?
Azure Functions
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 24%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENM%3C/text%3E%3C/svg%3E)
navba-MSFT 27,605 Reputation points Microsoft Employee Moderator2024-07-22T06:25:18.8333333+00:00 @Sarish Tabish Sayyed Welcome to Microsoft Q&A Forum, Thank you for posting your query here!
.
I directly tried accessing the URL from browser and it worked fine without any warning.
http://permissionsgatewayapi.trafficmanager.net/
.
Where are you encountering this error? Is it in your local dev environment or on Azure deployed function app?
.
Do you have any proxy or firewall within your enviornment ?
.
The error you’re encountering,
RemoteCertificateNameMismatch, typically occurs when the certificate’s subject name or one of the values in the Subject Alternative Name (SAN) field does not match the hostname of the server you’re trying to connect to.In other words, seems like this app is trying to reach out to an endpoint but which does not own a valid certificate.
.
In your case, the
subjectNameandhostNamesshould match the hostname of the server exactly, without including the protocol (http://). So,permissionsgatewayapi.trafficmanager.netshould be correct as long as it matches the hostname you’re connecting to..
Action Plan:
- Verify the Certificate: Ensure that the certificate’s subjectName and hostNames match the exact hostname of the server you’re connecting to.
- Check the SAN Field: Make sure the DNS name is included in the SAN field of the certificate.
3.Trust the Certificate: Ensure that the certificate is trusted by the client. This might involve installing the certificate in the trusted root certificate store on the client machine.
4.If the issue persists, you might want to check if there are any intermediate certificates that need to be installed or if there are any issues with the certificate chain.
.
.
Workaround (not recommended ):
Please check if the below sample code also helps to suppress the error:
private bool ValidateClientCertificate(System.Security.Cryptography.X509Certificates.X509Certificate cert, System.Security.Cryptography.X509Certificates.X509Chain chain, System.Net.Security.SslPolicyErrors sslPolicyErrors) { _certificateValid = sslPolicyErrors == System.Net.Security.SslPolicyErrors.None ? true : false; return true; }.
Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.
-
navba-MSFT 27,605 Reputation points Microsoft Employee Moderator
2024-07-24T03:03:21.3266667+00:00 @Sarish Tabish Sayyed Just following up to check if my suggestion helped. Please let me know if you have any further queries. I would be happy to help.
Sign in to comment
Sign in to answer