We’ve been getting the Autodesk sign-in wall on Flame 2027.1: Unable to authorize license Your system settings, firewall, or antivirus are likely preventing sign in. It’s not the license server, and it’s not Boris/Neat. It’s Autodesk’s IDSDK / SSO stack that 2027.1 uses to authorize Flame. What’s actually happening Flame now keeps an encrypted identity DB (idservices.db) and puts the AES key in the user’s gnome-keyring. If that keyring isn’t there, isn’t unlocked, or is on a filesystem that doesn’t do POSIX locks the way Autodesk expects, sign-in dies and you get the firewall story. Three things keep lining up for us: NFS home directories. Identity state and keyrings on shared homes are a bad fit. Locks and host-bound encrypted DBs written on one box don’t behave on the next one, or after a remount. PCoIP / Teradici sessions. GDM usually starts and unlocks gnome-keyring. A lot of PCoIP PAM stacks capture the password and never really do the session half, so you get a keyring with no secrets. After a reboot the DB is still on disk and the key is gone. Decrypt fails (we’ve been seeing error 3043). Crash leftovers. If Flame or AdskIdentityManager dies, POSIX semaphores can sit in /dev/shm forever. Next launch hangs on the lock (error 3211). Same thing if you try to “help” by pre-starting Identity Manager — it races Flame’s licensing agent for the SSO mutex and you reproduce the failure. There’s also a nasty footgun: a default → login pointer in ~/.local/share/keyrings with no login.keyring file. Identity Manager starts in NoUI (Did not find default collection) and PAM won’t create the missing file. Artist sees the same license modal. What we stopped doing Don’t start AdskIdentityManager for the user. Don’t invent a gnome-keyring collection from SSH. That pops a password dialog on their PCoIP session and hangs. Don’t write that default → login pointer unless login.keyring actually exists. What has been working Keep Autodesk identity state and the gnome-keyring on local disk, not NFS. Make sure PCoIP actually starts/unlocks gnome-keyring. After a crash, clear the leftover IDSDK locks in /dev/shm before the next launch. If the keyring is gone but idservices.db is still there, reset the identity DB and let them sign in once from the desktop. After that, one clean Flame launch + Autodesk SSO and they’re in.

This thread just saved my ass. Here is my token post saluting the braintrust.

Everyone needs to do this :backhand_index_pointing_up:

Please take a minute to open a support case @tomothyhondrox

Please do and then add your case number here so we can track. Thank you

Please try the following if this issue occurs again: Download the licensing support tool here. sudo ./AdskLicensingSupportTool --clean-cache Updated workaround: sudo pkill -9 -f AdskIdentityManager sudo rm -f /dev/shm/IDSDK* Please update us if it does not help.

That has consistently helped me in the last few weeks. Claude located it among support docs. [image] Best way for urgent ADSK support? Stupid licensing problems Flame Questions You may have tried those already, but just in case, two known current issues: Browser app database is outdated: Run sudo update-desktop-database /usr/share/applications (Linux only) The other one is an out-dated cache of the identity manager: Download: /opt/Autodesk/AdskLicensing//helper/AdskLicensingInstHelper from https://damassets.autodesk.net/content/dam/autodesk/external-assets/support-articles/licensing-support-tool/AdskLicensingSigninHelper-2.5.2.1579-linux.tar.gz Then run this (as s…

Autodesk Flame 2027.1 is failing to sign in because its new SSO system relies on local gnome-keyring and encrypted files that break on shared network drives (NFS), fail to unlock during remote PCoIP sessions, or hang due to leftover lock files in /dev/shm after a crash. Fix: Clear any leftover IDSDK locks inside /dev/shm and keep identity files on local disk storage rather than NFS.

We’re all grownups; what did the troll say?

Sometimes new users get flagged for typing fast. Troll free for sure.

Flame 2027.1 — “Unable to authorize license” (it's not your firewall) - #17 by allklier

Topic		Replies	Views	Activity
Flame 2025, ADSK Identity Manager and HPAnyware Flame Questions licensing , 2025	29	2366	December 17, 2024
Issue with Flame Licensing when installing 2025.1 Flame Questions installation	7	752	August 9, 2024
LIcense problem with Rocky Linux. Support concern Sysadmins	9	810	January 21, 2025
Licensing problems with multiple Flames Flame Questions jobs	21	533	May 9, 2026
2025: "Session expired" Flame Questions batch	26	763	September 5, 2024

Flame 2025, ADSK Identity Manager and HPAnyware

Flame Questions

licensing , 2025

29

2366

December 17, 2024

Issue with Flame Licensing when installing 2025.1

Flame Questions

installation

7

752

August 9, 2024

LIcense problem with Rocky Linux. Support concern

Sysadmins

9

810

January 21, 2025

Licensing problems with multiple Flames

Flame Questions

jobs

21

533

May 9, 2026

2025: "Session expired"

Flame Questions

batch

26

763

September 5, 2024

Flame 2027.1 — “Unable to authorize license” (it's not your firewall)

Related topics