Our company has not found a way to definitively prove that personal access tokens, combined with legacy authentication as provided by the shotgun_api3 library, are sufficient for continued pipeline functionality after Friday.
Would appreciate confirmation, as we’re operating on a hunch here and if we’re wrong… not good.
As far as I’ve understood from @patrick-hubert-adsk 's documents, PAT’s are only required if your scripts are interacting with the Status of a HumanUser record.
So for example, if you have automated scripts that Activate or Deactivate SG accounts.
To be clear, a migrated user would use their Autodesk ID to log into SG web, but would need to use their legacy login/password + PAT to use any scripts authenticating with HumanUser credentials.
There is no way for the API to use their Autodesk ID credentials, right?