Unable to Sign in with SSO with formerly working install as well as fresh installs

[halhollis]

I have an educational license for EAGLE 9.6.2 installed on a Dell laptop running Ubuntu 22.04.5 LTS, and I can no longer use the program due to problems with the "Sign in" process for SSO. This installation worked fine as late as August of last year.

However, when I launch EAGLE now, the "Control Panel" window opens followed by the "Sign in" popup. When I enter my University email address, my University's SSO page is brought up, I enter my credentials, and a "403: Forbidden" page appears.

After checking the forums and Autodesk support for this problem, I decided to try a fresh install on my another PC running an up-to-date Windows 11 OS. In this case, only the "Sign in" window opens and I get the same "403: Forbidden" page after entering my credentials.

The Autodesk Assistant AI recommended creating the environment variable "EAGLE_SIGNIN_DEFAULTUSERAGENT" and setting its value to 1. Now, after I enter my credentials, I get a message "Check for Duo Push" and a request to approve the login on my phone. After I approve, the "Sign in" window is cleared and ... nothing else happens. EAGLE does not start and the "Sign in" window just sits there with a blank white page.

Please note that I refreshed my educational license on 2/18, and I received an email from Autodesk with the subject "You're verified for Autodesk education access".

Also, I have tried a fresh install on Ubuntu 24.04.1 with exactly the same behavior, i.e., a "403: Forbidden" page unless I run "export EAGLE_SIGNIN_DEFAULTUSERAGENT=1" and then "./eagle" from a terminal after which I get through the SSO cycle only to get a blank white page on the "Sign in" window and no EAGLE.

This is incredibly frustrating as I really need to use this program today, and nothing I've tried yet seems to work, and I've spent hours trying to fix this. Is there someone here that can fix this problem?

[jorge_garcia]

Hello @halhollis ,

I've reached out to the developers to see if something is going on.

Let me know if there's anything else I can do for you.

Best Regards,

[halhollis]

Thank you Jorge. Would you check to see if there is a fix for this in work?

[jorge_garcia]

Hello @halhollis ,

I hope you're doing well.  I got this response from a developer. Could you try this?

"

This is how I start Eagle 9.6.2 from the command line (on MacOS):

EAGLE_SIGNIN_USERAGENT="Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko) EAGLE/9.6.2" /Applications/Eagle-9.6.2/eagle.app/Contents/MacOS/eagle

This works for me using the Autodesk SSO. I would recommend the user to try the same on his machine, changing the path to the eagle executable, as that is different on Linux.
If that does not work and if it has been from August that he used Eagle, it can well be that there was an update in the SSO provider. We have had a few cases in the past where a special configuration needed to be made on the SSO provider to handle login request from Eagle in a compatible way.
"

Let me know what you find.

Best Regards,