Running Without User Identity
Overview
By default, a Fusion WorkItem runs the Fusion engine on behalf of a specific Fusion user. The service obtains that identity from either a Personal Access Token (PAT) supplied in the WorkItem body, or from a 3-legged OAuth (3LO) token used for on-behalf-of (OBO) authentication.
You can now submit a Fusion WorkItem without supplying a PAT or OBO token. In that case the Fusion engine starts with no user logged in. The service skips token generation and the Fusion Automation API add-in skips the login step.
This is useful for scripts that do not need access to Fusion Team or other cloud-hosted Fusion data — for example, workflows that create geometry from scratch or operate only on files in the job working directory.
For WorkItems that need Fusion Team data access, continue to use PAT or OBO authentication as described in Fusion Team Integration.
Requirements
To run without user identity, all of the following must be true:
- The Activity does not require a
PersonalAccessTokenargument. - The WorkItem body does not include a
PersonalAccessTokenargument. - The WorkItem is not submitted with a 3LO token in the
Authorizationheader (OBO flow). - The WorkItem body does not include an
ADSK3LeggedTokenargument.
A 2-legged OAuth token in the Authorization header is still required to authenticate the call to the Automation API itself.
Limitations
When no user identity is provided:
- Fusion starts with no logged-in user.
- Scripts cannot access Fusion Team, hub, or other cloud-hosted Fusion data.
- Scripts cannot open designs by file URN from Fusion Team.
- Scripts can operate on files in the job working directory (for example, inputs downloaded via WorkItem arguments) or create new geometry locally.
Activity Definition
Omit PersonalAccessToken from the Activity parameters, or declare it as optional. The following example Activity runs a TypeScript AppBundle and accepts optional TaskParameters only:
{
"id": "CreateBoxActivity",
"engine": "Autodesk.Fusion+Latest",
"commandline": [],
"parameters": {
"TaskParameters": {
"verb": "read",
"description": "Optional parameters for the script",
"required": false
}
},
"appbundles": [
"<YOUR_NICKNAME>.CreateBoxAppBundle+my_working_version"
],
"settings": {},
"description": "Creates a box without requiring a Fusion user identity."
}
If an Activity declares PersonalAccessToken with "required": true, the Automation API rejects a WorkItem that omits it before the Fusion engine starts.
WorkItem Example
Submit the WorkItem with a 2-legged OAuth token and no user-identity arguments in the body:
curl -X POST \
'https://developer.api.autodesk.com/da/us-east/v3/workitems' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer <YOUR_2LO_ACCESS_TOKEN>' \
-d '{
"activityId": "<YOUR_NICKNAME>.CreateBoxActivity+my_current_version",
"arguments": {
"TaskParameters": "{\"width\": \"50mm\", \"height\": \"30mm\"}"
}
}'
Expected Behavior
When a WorkItem runs without user identity, the execution report includes the following system log messages:
- “No user impersonation” — logged by the Fusion engine runner when neither PAT nor OBO token is present.
- “No user authentication” — logged by the Fusion Automation API add-in when
task.jsoncontains no bearer token.
The WorkItem proceeds through script execution as normal if the script does not require an authenticated Fusion user.
Comparison With Other Authentication Options
| Option | OAuth Type | User Identity in Body | Fusion Team / Cloud Data Access |
|---|---|---|---|
| PAT (2LO caller) | 2LO | PersonalAccessToken |
Yes — inherits PAT owner’s permissions |
| OBO (3LO in Authorization) | 3LO | None required | Yes — inherits authorizing user’s permissions |
| No user identity | 2LO | None | No — Fusion runs without a logged-in user |
See Arguments for well-known Fusion Activity and WorkItem arguments such as TaskScript, TaskScriptUrl, and TaskParameters.