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; } } }

Unable to Sign in ArcGIS Pro

DevinGriffith

Software: ArcGIS Pro 3.2, 3.3, 3.4
License: Named User
Environment: Linux - Wine 10.0

Preface: ArcGIS Pro is not supported in this environment. Neither is Office 365 nor many other Windows applications, but compatibility through Wine is maturing, and being able to use ArcGIS Pro on another platform, even if it requires workarounds, would surely be beneficial to some users.

Issue: All versions of the software are able to complete installation, but further usage is halted upon being prompted to sign in. The sign-in window is blank, except for a few options:

Sign in automatically
Configure Licensing
Sign In Using Browser

At first, it seemed that this was an issue with WebView2, but upon being able to install 3.2, which does not depend on WV2, the same issue persists (with occasional crashes). It may be that a security component is not implemented. Until I get more details on what may be causing this, I am trying to circumvent by signing in using browser instead. This option opens an oAuth2 request in a Linux-native browser with no issue. Entering sign in credentials yields an xdg-open request for an app to handle 'arcgis-pro'. Passing this into a script shows a URL scheme of this format:

arcgis-pro://auth/####/?code=. . .

It seemed like all I had to do was associate this url scheme with and xdg MIME type:

x-scheme-handler/arcgis-pro

and make it the default. The behavior does not seem to change however. Selecting the Wine-installed ArcGIS Pro (a .desktop entry) after signing in through a browser only opens the application again. Same thing happens if I copy the response uri through the script and pass it as an argument to the exe. If Pro was already open, the new process terminates. If not, a new process is started with no difference: I still need to sign in.

The response token is obtained, but I do not know how to pass that to the running Pro process.

ArcGISSignIn.png

num_likes.png

Vind meer berichten getagd met

Desktop

Accepted answers

DevinGriffith

Here's the solution. I decided to take some time to look through the registry of a fresh install, since I have learned that uri handlers are added as registry keys in this format:

uri-handler (ex. arcgis-pro)
-> shell
--> open
---> command

That command has a default value pointing to the executable with an argument (%1). Turns out, I had assumed that executable would be ArcGISPro. This is what needs to be launched with the oauth code:

"C:\Program Files\ArcGIS\Pro\bin\ArcGISSignOnHandler.exe" \"%1\"

A simple test is to pass the redirect-uri into this via:

wine $WINEPREFIX/Program\ Files/ArcGIS/Pro/bin/ArcGISSignOnHandler.exe arcgis-pro://auth/ . . .

And for the first time I was able to use Sign In Using Browser. Now I have got to fix my mime types . . .

All comments

DevinGriffith

So, I did reinstall 3.4, and of course there are the same issues, and I have no DLL overrides. Compatibility set to Win10. Installed Edge in Win7 compatibility, and it seems this time around the Pro installer did not complain about WebView2, as I have tried this before to no avail. I started messing around on the blank sign in window again, and I managed to open up a github sign in page. Using a Windows-native instance as reference, I used tab selection to expand ArcGIS Login and enter my credentials. This approach did work. Although, I am not entirely sure why the page did not render, even when experimenting with many different graphics settings (including --disable-gpu).

Of course, this is a terrible workaround, but this at least means that other sections of ArcGIS Pro can be tested.

DevinGriffith

Attempted to apply the new patches. It looks like it updated to 3.4.1, but could not update to 3.4.2 for some reason . . .

Log attached.

ArcGISUpdateError.txt

DevinGriffith

Here's the solution. I decided to take some time to look through the registry of a fresh install, since I have learned that uri handlers are added as registry keys in this format:

uri-handler (ex. arcgis-pro)
-> shell
--> open
---> command

That command has a default value pointing to the executable with an argument (%1). Turns out, I had assumed that executable would be ArcGISPro. This is what needs to be launched with the oauth code:

"C:\Program Files\ArcGIS\Pro\bin\ArcGISSignOnHandler.exe" \"%1\"

A simple test is to pass the redirect-uri into this via:

wine $WINEPREFIX/Program\ Files/ArcGIS/Pro/bin/ArcGISSignOnHandler.exe arcgis-pro://auth/ . . .

And for the first time I was able to use Sign In Using Browser. Now I have got to fix my mime types . . .

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

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