Script users suddenly stopped working

,
1

We have a bunch of automations running from script users.
Today suddenly they cannot login

tank_vendor.shotgun_api3.shotgun.AuthenticationFault: Can't authenticate script

Checked all local factors, they get their key fine, but face this error.

1 Like
2

Same on our site

3

same here on only one site - other sites seem to be working

4

+1 to bump this, its preventing us from launching sg desktop in all sites

5

same here, unable to work with a deadline looming …

7

Also seeing event plugin scripts here failing to authenticate.

8

We have had scripts running for years that just stopped! :frowning:

AuthenticationFault(sg_response.get(“message”, “Unknown Authentication Error”))

9

Something changed on the server, presumably

1 Like
10

SG Desktop has stopped launching. We use bundle caches to pull apps dynamically and all of a sudden it’s not authenticating properly:

  File ".../tk-framework-desktopstartup/v2.1.12/python/tk-core/python/tank/bootstrap/cached_configuration.py", line 357, in update_configuration
    "Configuration could not be installed: %s." % e
TankBootstrapError: Configuration could not be installed: Failed to download into path .../shotgun/bundle_cache/tmp/7affb264430c46dd9b476cfcbbfd3a98: The Toolkit App Store credentials found in SG are invalid.
Please contact support at https://knowledge.autodesk.com/contact-support to resolve this issue..

(have replaced detailed paths with ‘…’ in the above logs)

11

Clients of mine that have keys made recently seem to be fine - this error seems to affect keys that are older. I have created a new key on our site and replaced in the code and it works so far.

-UPDATE-
new keys are failing, old keys are working

2 Likes
12

+1
raise AuthenticationFault(sg_response.get(“message”, “Unknown Authentication Error”))

13

Ok, thx for the tip! I’ll try updating our keys they are old…

14

Same here, older keys stopped working.

Also key length and structure seems different for old and new keys.
Security updates?

15

Hi - this has happened in our studio too, basically halting the whole pipeline.
A number of API accounts cannot be authorized.

It coincides in time with the update of Flow to version 8.69.

16

Looks like its now officially broken according to the status page https://status.shotgridsoftware.com/

Hopefully we’ll hear back from SG/Flow soon

1 Like
17

Yes, creating new keys works for our inhouse pipiline, very annoying though as everyone had issues.

The new keys have different length and content ( now alphanumeric and not just numerical as before so even if they are shorter they probably are longer so to say…

– UPDATE –

The keys worked for a little bit now also the new keys are failing :frowning:

– UPDATE 2 –

So, ok NOW the original ones works…

18

+1 Also affected our site. Autodesk, heelppp!!

1 Like
19

Got a reply to my ticket, they are reverting the latest update.

20

Can anyone confirm if re-generating the bad keys is required now that Autodesk says the issue is resolved? We’ve done that once and they failed again, so trying to avoid re-deploying the key if it’s not necessary.

21

We had to re-generate keys twice, as they stopped working shortly after the first time.

All good now.

1 Like