Select to view content in your preferred language

Support Non-Interactive Authentication for ArcGIS Pro in Batch Processing Environments

197
5
Tuesday
Status: Closed
Labels (1)
MelanieWawryk
Frequent Contributor
Enable Non-Interactive ArcGIS Pro Authentication for Service Accounts and Automated Workflows

As more organizations are forced to move from Concurrent Use and Single Use licensing to Named User licensing, there is a growing need for a supported method to run ArcGIS Pro-dependent automation without requiring an interactive user session.

Many enterprise GIS environments rely on:

  • Scheduled ArcPy scripts
  • FME Form automated workflows
  • Windows Task Scheduler jobs
  • Enterprise ETL processes
  • Overnight geoprocessing tasks
  • Data synchronization and maintenance jobs

Today, these workflows often depend on ArcGIS Pro being previously opened and signed in by a user. Organizations have reported situations where automated processes fail until ArcGIS Pro is launched interactively and the Named User license is refreshed. [support.esri.com], [support.safe.com]

The current model creates challenges for:

  • Servers located in data centers
  • Service accounts with interactive logon disabled
  • Cybersecurity policies that prohibit user logins on servers
  • High availability and disaster recovery environments
  • FME and Python batch processing platforms

Suggested Enhancement

Provide a supported mechanism that allows ArcGIS Pro licensing and authentication to operate in a fully unattended manner.

Possible approaches could include:

  • Service Principal authentication
  • Application identities
  • Managed Service Account (gMSA) support
  • OAuth client credentials flow
  • Command-line licensing/authentication tools
  • Named User token refresh APIs
  • Machine-based licensing for automation workloads
  • Headless ArcGIS Pro authentication

For example: arcgispro.exe /signin service_account or proauth.exe --login service_account or an API that allows a scheduled process to securely refresh authentication without launching the ArcGIS Pro user interface.

Many organizations use ArcGIS Pro as a dependency for:

  • FME Esri Geodatabase readers/writers
  • ArcPy automation
  • Enterprise geodatabase maintenance
  • Data replication
  • Nightly GIS processing
  • Asset management integrations

Without a supported unattended authentication mechanism, organizations risk:

  • Failed overnight jobs
  • Manual intervention by GIS administrators
  • Reduced reliability of enterprise automation
  • Increased operational costs
  • Barriers to adopting Named User licensing

Benefits

A supported non-interactive licensing model would:

  • Improve reliability of enterprise automation
  • Support modern DevOps and server environments
  • Eliminate the need to periodically open ArcGIS Pro
  • Enable secure service account usage
  • Simplify migration away from Concurrent Use licensing
  • Improve support for FME, Python, Task Scheduler, and enterprise ETL platforms

As ArcGIS Pro becomes the primary desktop GIS platform and Concurrent Use licensing is phased out, unattended processing should be a first-class and supported deployment scenario for enterprise organizations.

5 Comments
ValeriaChavez
Status changed to: Closed

Hi @MelanieWawryk

I will be closing this thread as what you're describing here is a violation of the licensing agreement.

ArcGIS Pro allows users to sign-in across multiple machines to reduce friction when switching devices or forgetting to sign out after each session. For example, if someone is still signed in on their work laptop and needs to sign in elsewhere, that convenience is within the intent of the policy.


Using a single user type to actively run ArcGIS Pro in parallel on multiple machines (e.g., virtual desktop running a ModelBuilder job while the same user edits data on a laptop) is not permitted, nor is using ArcGIS Pro for automated background tasks. 

If you and your organization require running workflows in parallel or as nightly scheduled tasks, I encourage you to get in touch with your account team to explore alternative ways to license ArcGIS capabilities such as ArcGIS Server via ArcGIS Enterprise.

Thank you for being an active member of Esri Community!

MelanieWawryk

How do you expect people to run geoprocessing scripts overnight? We have been scripting jobs for the last 25 years and now they all fail because ArcPro isn't signed in?

JoshKalov

@ValeriaChavez That is a confusing response to say that Pro can't be used to run nightly scheduled tasks. That has been a standard part of the ESRI Desktop world since ArcMap. ESRI even built a whole UI in Pro to make it easier to do! Schedule geoprocessing tools | ArcGIS Pro documentation

Please reopen this idea.

BillFox

why kill the idea?

isn't that what the ideas place if for? to ask/answer/suggest/work-rounds, etc.?

would something like this official esri support knowledge base article help?

Running scheduled Python task under a group managed service account throws an ArcGIS Pro License err... 

MelanieWawryk

We have a separate ArcPro license for the service account, so I don't see how it is breaking the license as @ValeriaChavez  states. Thanks @Bill I will try the work around. I have also put it into Esri support. I think that solution might have worked when you could still have a stand-alone license. I will report back once we test. Thanks