3ds Max 2025 named‑user license token refresh after refresh token expiry

Immediate fallback on refresh‑token failure

When the short‑lived access token (≈1 hour) needs renewal, 3ds Max silently calls the Autodesk Identity Service token endpoint with the stored refresh token. If that request returns HTTP 401 Unauthorized or HTTP 400 Bad Request (indicating an expired or revoked refresh token), the licensing SDK treats the attempt as a failure and immediately shows the Autodesk sign‑in dialog. There is no configurable waiting period; the fallback occurs on the very next refresh attempt.

Typical timing

The background refresh is performed roughly every 60 minutes while the application is running. Consequently, the user will see the sign‑in prompt up to an hour after the refresh token becomes invalid, but the delay is solely due to the scheduled refresh interval, not an additional retry count.

Triggering the fallback without restarting

Deleting the local token cache forces the licensing SDK to obtain a new session on the next launch or on the next background refresh, which reproduces the same 401/400 flow if the refresh token is no longer valid.

1. Close 3ds Max (optional; the cache can also be cleared while the app is running, but a restart guarantees the SDK reads the cleared state).
2. Open a command prompt and run:

del "%LOCALAPPDATA%\Autodesk\Licensing\LoginState.xml"

If additional token files exist (e.g., TokenCache.dat), remove them as well.

Verification

To confirm the exact HTTP response, monitor the licensing log:

%LOCALAPPDATA%\Autodesk\Licensing\Autodesk Licensing.log

Look for lines containing 401 or 400 from the token endpoint.