Invoke-PSUScript -AppToken not listing job as the app token user

[adamdriscoll]

Description of Issue

Run a script with Invoke-PSUScript -AppToken
Script is listed as running as system and not app token user.

Version

5.3.2

Severity

High

Hosting Method

MSI (Windows Service)

Operating System

Windows

Database

SQLite

Licensed

Yes

Features

No response

Additional Environment data

No response

Screenshots/Animations

No response

[adamdriscoll]

This is a bug and a patch will be included in version 5.3.3.

[RubenT91]

We are reopening this issue as the customer is still experiencing intermittent authentication failures when using Invoke-PSUScript after upgrading to PSU 5.3.3.

Updated Issue Details:
The customer’s script executes five PSU scripts sequentially with Invoke-PSUScript -UseDefaultCredentials -Wait.
The behavior observed:
Script 1 executes successfully.
Scripts 2, 3, and 4 fail with an "Unauthenticated. Specify an app token, use default credentials, or enable permissive security model" error.
Script 5 executes successfully.
This behavior is inconsistent, as previously all scripts were failing, and now the failure is limited to specific ones in the sequence.
A 10-second delay (Start-Sleep -Seconds 10) was introduced between script calls to rule out timing issues.

[Error] Cannot retrieve the dynamic parameters for the cmdlet. Unauthenticated.
Specify an app token, use default credentials, or enable permissive security model.

This occurs at different points in the execution order, indicating potential token/session issues in PSU 5.3.3.

[adamdriscoll]

Ticket ID 10342