topic Re: ArcGIS Pro Named Users via Web Server in ArcGIS Enterprise Questions

ArcGIS Pro Named Users via Web Server

babarsac — Wed, 19 Jul 2023 16:36:34 GMT

I'm currently working with Esri and our IT to set up a new Enterprise (v11.1) stack and move away from concurrent licensing. We've hit a snag with serving up ArcGIS Pro licenses via Portal. The LM (license manager) is deployed and authorized fir named users.

When a user opens Pro they pass their Enterprise/Portal credentials to verify if they have been assigned a license. They way I understand it is that Pro then makes a second call to grab the actual license from the LM. This is where we hit a snag. The LM host defined in the license and in Portal is 'websrv.corp.local' however the only URL the users can access is 'gis.corp.com'. As a result when a user successfully authenticates in Pro they then get an error saying that a license cannot be found.

Here are my questions:

When Pro makes a request to the LM is that request proxied through Portal or is it trying to hit the LM directly?

Has anyone had any experience serving up Pro Named User licenses via Enterprise NOT behind a VPN?

Re: ArcGIS Pro Named Users via Web Server

ChristopherPawlyszyn — Fri, 21 Jul 2023 13:26:32 GMT

This topic in the documentation goes into more detail, but essentially the client is first connected to Portal for ArcGIS to get a confirmation that an ArcGIS Pro license is assigned to the user, then redirected to the License Manager instance for borrowing/checking-out the associated named user license. With that in mind, the LM should be referenced using a DNS record that is resolvable outside your internal network and the appropriate ports should be opened in your firewall (reference link).

The LM host can be updated directly in Portal Admin -> Licenses, but the changes to the firewall and LM configuration will require changes on the instance itself and potentially IT team involvement.

Re: ArcGIS Pro Named Users via Web Server

babarsac — Tue, 15 Aug 2023 03:58:34 GMT

Thanks for the info! We ended up deploying the LM on to the web server itself, opening up ports as necessary, and we are up and running.