Can't login with Autodesk ID SSO on Linux

Can't login with Autodesk ID SSO on Linux

josewardMARP7
Explorer Explorer
15,665 Views
53 Replies
Message 1 of 54

Can't login with Autodesk ID SSO on Linux

josewardMARP7
Explorer
Explorer
As the title says, I can't log into Maya using SSO Autodesk ID on Linux. Everything has been installed correctly to my knowledge, but I'm happy to answer specific installation questions if someone more knowledgeable thinks it is relevant.

The program opens fine, but when I select, "Sign in with your Autodesk ID", the window just closes. Selecting" Enter a serial number" or "Use a network license" does not crash the app. Authentication services are running properly and are up to date. 

I have found this thread, but the solution provided is exclusive to Windows.

I am running Fedora Linux 39.

If anyone knows a solution to this problem or potential rabbit holes to explore, let me know!
15,666 Views
53 Replies
Replies (53)
Message 41 of 54

meepzh
Explorer
Explorer

Thank you for your efforts, jimmy_christensenMSURY. I was able to reproduce your success in the AUR. The software versions that I used were:

  • adlmapps 31.0.4
  • adsklicensing 15.1.0.12339 (15.4.0.13093 also works)
  • adskidentitymanager 1.15.3.5 (pre-1.15 crashes on Arch Linux)
  • maya 2026.0

It appears that the flow is that Maya interfaces with adsklicensing, which checks for any version of webkit2gtk3 through the rpm command. Once it determines that that requirement is satisfied, it will then search for /etc/pki/tls/certs/ca-bundle.crt or error out accordingly. I am not sure how this impacts systems that already have that file. Following that, it will launch the Identity Manager, which uses webkit2gtk, from where the user logs in. Upon a successful login, Maya will launch. On Arch Linux, the error logs are found in /tmp, which corroborate these workarounds.

Message 42 of 54

david.ostler2WSX9
Advocate
Advocate

I was able to get passed  "ERROR: Error Information: Maya 2026 : [IDSDK] 3073: The PC has not installed WebKitGTK yet, please install WebKitGTK." By doing the following, very similar solution to @jimmy_christensenMSURY.

sudo apt install rpm
cat > ~/mk_webkit2gtk3_dummy.sh <<'Bash'
#!/bin/bash
set -e
cat > webkit2gtk3.spec <<'SPEC'
Name:           webkit2gtk3
Version:        1
Release:        0
Summary:        Dummy Provides: webkit2gtk3 for Autodesk Licensing
License:        Public-Domain
Provides:       webkit2gtk3
%description
Empty placeholder so rpm -q webkit2gtk3 returns success.
%files
SPEC
rpmbuild -bb --define "_rpmdir $(pwd)" webkit2gtk3.spec
sudo rpm -i --nodeps --force x86_64/webkit2gtk3-1-0.x86_64.rpm
echo "Dummy RPM installed."
Bash
bash ~/mk_webkit2gtk3_dummy.sh

Now I'm getting the below window but no browser window opens up.  

Screenshot From 2025-04-29 22-32-34.png

 

At first I couldn't get a browser window to open.  I restarted my machine and it worked, I assume that there is an easier way but it worked and a browser opened and I was able to authenticate through Autodesk.  Then I ran into this issue:

Screenshot From 2025-04-29 23-13-00.png
In order to register AdskIdentityManager so that Ubuntu would recognize it as an app I did this:

/opt/Autodesk/AdskIdentityManager/Current/AdskIdentityManager --register

I noted that the file it created in ~/.local/share/applications/com.autodesk.AdskIdentityManager.desktop had the AdskIdentityManager's version number in the path instead of "Current" so I updated that file to future proof it.
Then I  updated the database and set adskidmgr as the default app:

# make sure the desktop database picks up the new entry
update-desktop-database ~/.local/share/applications

# set it as the default for this scheme
xdg-mime default com.autodesk.AdskIdentityManager.desktop x-scheme-handler/adskidmgr

And now Maya 2026 works on Ubuntu 24.10

Seems like there are still a few little quirks like complaining about not having access to the internet:
Screenshot From 2025-04-29 23-58-50.png

There are also some new errors I don't recall seeing on Maya 2024, here's my startup output:

Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
[2025-04-29 23:57:20.156] [warning] cannot create Service Data folder at path /var/lib/Autodesk/CER, Access to file denied: /var/lib/Autodesk
Warning: Setting a new default format with a different version or profile after the global shared context is created may cause issues with context sharing.
Initialized VP2.0 renderer {
  Version : 2016.11.62.12. Feature Level 5.
  Adapter : NVIDIA GeForce RTX 4090/PCIe/SSE2
  Vendor ID: 4318. Device ID : 
  Driver : 4.6.0 NVIDIA 560.35.03.
  API : OpenGL V.4.6.
  Max texture size : 16384 * 16384.
  Max texture coords : 32
  Shader versions supported (Vertex: 5, Geometry: 5, Pixel 5).
  Shader compiler profile : (Best card profile)
  Active stereo support available : 0
  GPU Memory Limit : 24564 MB.
  CPU Memory Limit : 119992 MB.
  MultiDraw consolidation : enabled
}
OpenCL evaluator is attempting to initialize OpenCL.
Detected 1 OpenCL Platforms: 
 0: NVIDIA Corporation. NVIDIA CUDA. OpenCL 3.0 CUDA 12.6.65.
 Supported extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_nv_create_buffer cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_device_uuid cl_khr_pci_bus_info cl_khr_external_semaphore cl_khr_external_memory cl_khr_external_semaphore_opaque_fd cl_khr_external_memory_opaque_fd 
 Selected matching OpenCL Platform: NVIDIA Corporation NVIDIA CUDA OpenCL 3.0 CUDA 12.6.65.
OpenCL evaluator choosing OpenCL platform NVIDIA Corporation.
Choosing OpenCL Device NVIDIA GeForce RTX 4090.  Device Type: GPU  Device is available.

Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.

Running these two lines fixed the permissions issue, it's just me on this machine:

sudo mkdir -p /var/lib/Autodesk/CER
sudo chown -R $USER:$USER /var/lib/Autodesk

And I removed "LC_ALL=C" from my Maya.env and that fixed the "UTF-8" issues.

I then created a fresh account to be to see what the default Maya.env looked like and it was empty.  I removed everything from my Maya.env and Maya starts fine without any extra complaints.  The entries must have been carried over from a previous Maya version.

Message 43 of 54

blendernoob64
Enthusiast
Enthusiast

I tried david's tutorial above on Fedora 41 for Maya 2024 and it worked perfectly. I had to make a fake RPM and then update my desktop entries, then Maya would launch perfectly. Now I no longer have to keep uninstalling 2024's identity manager just to use Maya for a day. I wonder if Fedora 42 will still work. We will see.

0 Likes
Message 44 of 54

david.ostler2WSX9
Advocate
Advocate

After using Maya for a few weeks now it seems pretty solid.  The only issue I've run across is that the Arnold Render View will not open back up once it has been closed.  The only way to get it to open again is to restart Maya as far as I can tell.  Not a huge deal, I just minimize the window instead of closing it but still a bit tedious as I often make the mistake of closing the window.  Just wondering if others are seeing the same issue on the non-approved linux flavors?

0 Likes
Message 45 of 54

blendernoob64
Enthusiast
Enthusiast

I just tried the fix on Fedora 42 and it worked! You will have to reinstall the dummy rpm after updating, but everything should be good afterwards. Also you will need to run on an X11 DE so no Wayland sessions until Autodesk adds proper wayland support. 

0 Likes
Message 46 of 54

blendernoob64
Enthusiast
Enthusiast

Another update, on Fedora 42, I was able to launch Maya 2024 in the KDE and GNOME wayland session, and with the Identity Manager fix. I do not know if Autodesk Updated something in the background, or XWayland fixed something, but it would be nice to have this confirmed with other setups. My only other guess is that maybe the Identity Manager checked me in when I was running an X11 session and just never bothered to check in again? 

0 Likes
Message 47 of 54

blendernoob64
Enthusiast
Enthusiast

Update for Fedora 43. The fix does not work anymore. The Identity Manager requires libwebkit2gtk-4.0.so.37 which fedora 43 doesn't provide anymore, as it upgraded to webkit2gtk4.1. Until this awesome community finds a fix, do not upgrade yet!

 

That and the fact that RPM 6 requires GPG signatures that Maya doesn't provide make is one heck of an installation process. The Setup app doesnt work and you will have to install manually.

0 Likes
Message 48 of 54

blendernoob64
Enthusiast
Enthusiast

I found a fix for the above problem. After installing each of Maya's packages with sudo rpm -ivh --nodigest --nofiledigest and following the guides above you will have to grab webkit2gtk4 and javascriptcoregtk from the Fedora 42 repositories. This can be done with the following commands 

sudo dnf install 'https://dl.fedoraproject.org/pub/fedora/linux/releases/42/Everything/x86_64/os/Packages/j/javascriptcoregtk4.0-2.47.2-3.fc42.x86_64.rpm'

sudo dnf install 'https://dl.fedoraproject.org/pub/fedora/linux/releases/42/Everything/x86_64/os/Packages/w/webkit2gtk4.0-2.47.2-3.fc42.x86_64.rpm'

 

I am not sure if this will conflict with the proper webkit2gtk4.1 which Fedora 43 ships with, but its something to get the Identity manager working again

 

Screenshot_20251109_192459.png

 

Message 49 of 54

jericho_d1019
Observer
Observer

I just installed Maya 2026 on Fedora 43 (KDE) successfully. I tried David Ostler and Blendernoob's strats above and nothing completely worked, but this helped me get farther in the process to the point where it would at least try to start loading something after I clicked to sign in, instead of immediately sending me to the Qualtrics form. I finally got an actual error message-- ADLSDK_STATUS_LICENSE_CHECKOUT_ERROR.

After that, I went into my Autodesk account and tried installing the most recent updated rpms for the Licensing Service and Identity Manager. There was a recent update released on October 27th(?)  and after I installed this Maya's login was able to open with my browser.

 

I don't know if there was a recent fix released that took care of this problem entirely or if it was a combination of the strategies above and the update, but I hope this helps somebody.

 

Message 50 of 54

elijahE5M9H
Explorer
Explorer

This worked for me as well on fedora 43 installing Maya 2025.3.  I use the Gnome spin but I installed a kde X11 session just install maya ha

 

But it wasn't easy at first, I had to make sure any older version of the identity manager were removed before reinstalling the latest version then maya was able to open.

I also had to install the RPM packages with --nodigest

 

0 Likes
Message 51 of 54

blendernoob64
Enthusiast
Enthusiast

A new update to the licensing service is here. It now requires WebkitGTK 2.46.0 or later. I wonder if that means that the webkitgtk4.1 package included in Fedora will work now. I also wonder what that means for the Identity Manager.

0 Likes
Message 52 of 54

blendernoob64
Enthusiast
Enthusiast

Maya 2027 is now out! Once Fedora 44 comes out I want to try this version out. Wayland is still a big question as there was no mention of it in the release notes. Yes, you can use Maya in Wayland, but there are some limitations (as of Maya 2026) including having to launch it first in an X11 window manager for the Identity Manager to work, having to use environment variables to see the viewport, some windows not working at all like the graph editor, and not being able to dock windows. I remember talking to someone on the Renderman Discord that the word is that Pixar isn't planning to support Rocky 10 (the Wayland only version of Rocky) until around 3 or more years later, and God forbid Autodesk plans to hold out for that long. If anyone at Autodesk can clarify how Wayland is doing over there, we would like to know.

Message 53 of 54

blendernoob64
Enthusiast
Enthusiast

Good news! Maya 2024 launches in Fedora 44 beta on GNOME! After installing manually using the RPM packages, and being sure to install the latest identity manager first, Maya launched just as I remember. As for differences, GDM and the Plasma-Login-Manager cannot launch X11 sessions anymore. So you will need to use LightDM or SDDM to launch your desktops, as you will need to launch Maya in X11 at least once for the Identity Manager to check you in. I would recommend installing a window manager like WindowMaker for this as it is super light and wont cause a ruckus in your system. Also for the newer licensing services you will need openssl1 installed. Here is the link to the RPM you will need 

 

https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/36/Everything/x86_64/os/Package...

 

Screenshot From 2026-04-01 02-15-25.png

Message 54 of 54

blendernoob64
Enthusiast
Enthusiast

I tried this process again in a Virtual Machine in preparation to make a guide on installing Maya on Fedora 44, but all my attempts did not work for Maya 2027. Maybe something is different since the last time I updated before the first freeze. GDM also has a strange bug where upon installing a different X11 desktop, it has $XDG_SESSION_TYPE return wayland which makes the identity manager not launch at all. I bet that is a bug as desktop portals for different desktops are also broken. I will try installing 2027 on Fedora 44 again once the official release comes out, but for now, stick with Fedora 43 and if you want to try the Fedora 44 beta, try using Maya 2024 instead. Fedora 44 looks like a pretty great version with Gnome 50 fixing issues I have had with the desktop for a while now.