We aren’t able to login to Shotgrid on newly installed Linux (CentOS 7) machines. We get the following error: 'Authentication Failed: Can’t authenticate user ‘A@B.com’ '. We’re sure credentials are correct (tried multiple accounts) and on other machines in our studio when we log in we get redirected to Autodesk ID site and are able to log in with our AU-identity account but not on these newly installed ones. Do you maybe know how to fix this? We’re on the latest Shotgrid version for Centos 1.7.0
Hi @lennard
Could you please share a screenshot of the issue ?
If the Desktop is prompting you with the old username/password Qt dialog, and not the Web-like login, then it means that there is something incorrect in the environment.
Have you setup a special PYTHONPATH ?
Ideally we would also need to see the content of the tk-desktop.log file… Have you opened a support case ?
-Patrick
Hello @patrick-hubert-adsk ,
i am getting the same issue, not getting web-like login.
please find below tk-desktop.log
[root@myftest2 logs]# cat tk-desktop.log
2021-11-18 19:13:00,934 [tk-desktop.DEBUG] Registering tk-desktop logger.
2021-11-18 19:13:00,934 [tk-desktop.bootstrap.INFO] ------------------ Desktop Application Bootstrap ------------------
2021-11-18 19:13:00,934 [tk-desktop.bootstrap.DEBUG] Bootstrap version v1.7.1
2021-11-18 19:13:00,983 [tk-desktop.bootstrap.INFO] tk-framework-desktopstartup will be loaded from /opt/Shotgun/Resources/Desktop/Python/tk-framework-desktopstartup.
2021-11-18 19:13:00,984 [tk-desktop.startup.INFO] ------------------ Desktop Startup Framework Startup ------------------
2021-11-18 19:13:00,985 [tk-desktop.startup.INFO]
Python
Executable: /opt/Shotgun/Shotgun
Version: 2.7.17
sys.path:
- /opt/Shotgun/Resources/Desktop/Python/tk-framework-desktopstartup/python
- /opt/Shotgun/Resources/Desktop/Python
- /opt/Shotgun/Python/lib/python27.zip
- /opt/Shotgun/Python/lib/python2.7
- /opt/Shotgun/Python/lib/python2.7/plat-linux2
- /opt/Shotgun/Python/lib/python2.7/lib-tk
- /opt/Shotgun/Python/lib/python2.7/lib-old
- /opt/Shotgun/Python/lib/python2.7/lib-dynload
- /opt/Shotgun/Python/lib/python2.7/site-packages
Environment variables
PATH:
- /usr/lib64/qt-3.3/bin
- /usr/local/bin
- /usr/local/sbin
- /usr/bin
- /usr/sbin
- /bin
- /sbin
- /home/surajs/.local/bin
- /home/surajs/bin
PYTHONHOME: Not Set
PYTHONPATH: Not Set
SGTK_DESKTOP_ORIGINAL_PYTHONHOME: Not Set
SGTK_DESKTOP_ORIGINAL_PYTHONPATH: Not Set
2021-11-18 19:13:00,985 [tk-desktop.startup.INFO] Using tk-core from ‘/opt/Shotgun/Resources/Desktop/Python/tk-framework-desktopstartup/python/tk-core/python’
2021-11-18 19:13:01,056 [tk-desktop.DEBUG] Unregistering tk-desktop logger.
2021-11-18 19:13:01,181 [30062 DEBUG sgtk.core.log] Debug logging enabled. To permanently enable it, set the TK_DEBUG environment variable.
2021-11-18 19:13:01,181 [30062 DEBUG sgtk.core.log] Setting TK_DEBUG in the environment for this session. This ensures that subprocesses spawned from this process will inherit the global debug logging setting from this process.
2021-11-18 19:13:01,181 [30062 DEBUG sgtk.core.util.user_settings] Reading user settings from /home/surajs/.shotgun/preferences/toolkit.ini
2021-11-18 19:13:01,181 [30062 DEBUG sgtk.core.util.user_settings] Default site:
2021-11-18 19:13:01,181 [30062 DEBUG sgtk.core.util.user_settings] Default login:
2021-11-18 19:13:01,181 [30062 DEBUG sgtk.core.util.user_settings] SG proxy:
2021-11-18 19:13:01,181 [30062 DEBUG sgtk.core.util.user_settings] App Store proxy:
2021-11-18 19:13:01,181 [30062 DEBUG sgtk.core.util.user_settings] System proxy:
2021-11-18 19:13:01,181 [30062 DEBUG sgtk.ext.shotgun_desktop.startup] Retrieving credentials
2021-11-18 19:13:01,181 [30062 DEBUG sgtk.core.authentication.session_cache] Loading ‘/home/surajs/.shotgun/authentication.yml’
2021-11-18 19:13:01,181 [30062 DEBUG sgtk.core.authentication.session_cache] Yaml file missing: /home/surajs/.shotgun/authentication.yml
2021-11-18 19:13:01,181 [30062 DEBUG sgtk.core.authentication.session_cache] Current host is ‘None’
2021-11-18 19:13:01,182 [30062 DEBUG sgtk.core.authentication.shotgun_authenticator] No default user found.
2021-11-18 19:13:01,182 [30062 DEBUG sgtk.core.authentication.session_cache] Loading ‘/home/surajs/.shotgun/authentication.yml’
2021-11-18 19:13:01,182 [30062 DEBUG sgtk.core.authentication.session_cache] Yaml file missing: /home/surajs/.shotgun/authentication.yml
2021-11-18 19:13:01,182 [30062 DEBUG sgtk.core.authentication.session_cache] Current host is ‘None’
2021-11-18 19:13:01,182 [30062 DEBUG sgtk.core.authentication.session_cache] Loading ‘/home/surajs/.shotgun/authentication.yml’
2021-11-18 19:13:01,182 [30062 DEBUG sgtk.core.authentication.session_cache] Yaml file missing: /home/surajs/.shotgun/authentication.yml
2021-11-18 19:13:01,182 [30062 DEBUG sgtk.core.authentication.session_cache] Current host is ‘None’
2021-11-18 19:13:01,182 [30062 DEBUG sgtk.core.authentication.ui_authentication] Requesting username and password in a dialog.
2021-11-18 19:13:01,182 [30062 DEBUG tank.authentication.sso_saml2.core.utils] Constructing SSO dialog: Web Login
2021-11-18 19:13:01,182 [30062 WARNING sgtk.core.authentication.login_dialog] Web login not supported due to missing Qt module: The QtWebKit or QtWebEngineWidgets modules are unavailable
2021-11-18 19:13:01,196 [30062 DEBUG sgtk.core.authentication.session_cache] Loading ‘/home/surajs/.shotgun/authentication.yml’
2021-11-18 19:13:01,196 [30062 DEBUG sgtk.core.authentication.session_cache] Yaml file missing: /home/surajs/.shotgun/authentication.yml
2021-11-18 19:13:01,196 [30062 DEBUG sgtk.core.authentication.session_cache] Recent hosts are:
2021-11-18 19:13:01,198 [30062 DEBUG tank.authentication.sso_saml2.core.utils] Destroying SSO dialog
2021-11-18 19:13:08,850 [30062 DEBUG sgtk.core.authentication.session_cache] Loading ‘/home/surajs/.shotgun/authentication.yml’
2021-11-18 19:13:08,850 [30062 DEBUG sgtk.core.authentication.session_cache] Yaml file missing: /home/surajs/.shotgun/authentication.yml
2021-11-18 19:13:08,850 [30062 DEBUG sgtk.core.authentication.session_cache] Recent users are:
2021-11-18 19:13:08,851 [30062 DEBUG sgtk.core.authentication.session_cache] Recent users are:
2021-11-18 19:13:14,073 [30062 DEBUG sgtk.core.authentication.session_cache] Loading ‘/home/surajs/.shotgun/myfairy/authentication.yml’
2021-11-18 19:13:14,074 [30062 DEBUG sgtk.core.authentication.session_cache] Yaml file missing: /home/surajs/.shotgun/myfairy/authentication.yml
2021-11-18 19:13:14,074 [30062 DEBUG sgtk.core.authentication.session_cache] Recent users are:
2021-11-18 19:13:14,074 [30062 DEBUG sgtk.core.authentication.session_cache] Recent users are:
2021-11-18 19:13:26,988 [30062 DEBUG sgtk.core.authentication.session_cache] Connecting to SG to generate session token…
2021-11-18 19:13:27,839 [30062 DEBUG sgtk.stopwatch.tank.authentication.session_cache] generate_session_token: 0.851063s
I’ll ask a colleague with access to a Centos 7 environment (and more knowledge of the toolkit than me) to test on Monday (tomorrow is a company-wide day off)
-Patrick
Sure, but request you to please help us as soon as possible, and also I have opened support case from my license account.
Hi @sonu.k,
on my side I was able to login with SG Desktop v1.7.1 on CentOS 7. Can you give me more info about your setup? Which version of CentOS 7 are you running, are you using Gnome or kde?
Also, you said that you are not getting the web login, so you just enter your Shotgrid site and then click on Sign In button and nothing happen? Do you have anything in the terminal where you launch Desktop?
If you click on forgot your password, does it open a web browser to your site? If yes, in which browser, Firefox?
Thanks,
Francis
Hello @mathurf ,
Thanks for the reply, I am using latest Version of SG and centos 7 2009.
My issue is resolved now, I created legacy login and using the same I got logged in.
Thank you 
…