nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Pro/Portal Security Alert - Certificate does not match the name of site you are trying to view

GeoffreyWest4

I am connecting to a Portal with ArcGIS Pro and am receiving the alert below. I am able to access Portal with the cert appearing as valid and the site is trusted. I have added the intermediate, root, and private key certs to portaladmin. The only thing that seems to be a bit different than previous configs is that the certificate store is in WebHosting versus personal. Does this matter? How do I resolve the security alert in Pro with my portal URL. I am using a wildcard cert. This an ArcGIS Enterprise 10.8.1 Base Deployment as well.

Encontre mais publicações marcadas com

Accepted answers

JonathanQuinn

You could try to run Fiddler when starting Pro to see where the request is going. If the domain of any of the URLs being accessed does not match your certificate, that may explain the popup especially considering it's stating that the certificate does not match the name of the site.

All comments

JonathanQuinn

ArcGIS Pro is likely complaining about the certificate used for the Admin URL of the deployment. If you looked at the certificate, (clicking on the View Certificate button), is the CN the wildcard, or the FQDN of the machine? If it's the FQDN of the machine, you can do two things:

1) Import the certificate into the Trusted Root Certificate Authority store on any machine that will be connecting to the deployment

2) Import a new certificate to use for ArcGIS Server's web server

Configure ArcGIS Server with an existing CA-signed certificate—ArcGIS Server | Documentation for ArcGIS Enterprise

Going through the first suggestion is a bit burdensome because you need to do that on any machine running ArcGIS Pro. Going through the second suggestion is a better option because as long as the client machine trusts that signed certificate, you won't see the popup.

GeoffreyWest4

Thanks Jon,

The CN is the wildcard. Do you know how I can resolve it with this being the case?

Billy_0-1630005979541.png

JonathanQuinn

GeoffreyWest4

Good call Jon -

That was the issue - when authenicating a request was made to *.ssp.com instead of *sspinnovations.com.

JeffGarland

Same issue w/ wildcard as the CN and added detail of being an external cert. External cert FQDN is different from local AD domain. Thus cert is *.externaldomain.com, FQDN is box.externaldomain.com while FQDN for server PC is box.internaldomain.local. (Use of CName in the DNS directs the external FQDN to local FQDN. Utilize WebContextURL property on Server to facilitate.)

Did the client PC step above. No fix.

Fiddler shows initially hitting the external FQDN via the HTTP port 443, then querying for download.esri.com, then esrisoftware.esri.com, then it queries for the local AD domain FQDN and fails.

Workaround is to set AGOL portal as the active, but would like to fix if possible.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.