-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TConnectSync has stopped working as of 9/5/2024 (with tconnectsync v0.9) #97
Comments
So, i've gotten the data for this in a similar way, and also ran into this. Since no one has responded yet, i'll just post what i've found: TConnect changed how their sign-in works. They no longer provide the accessToken in the cookie on login. You now have to get the UserID from the login, and then make an additional call to the following service to get the accessToken, and then it will work. Service: It requires a Bearer authorization, which...i don't know why, its hard coded in their javascript: "Bearer M0U2MzU3QkEtRjYyNS00REQyLUI2NUYtNEI1RTgxNDRBQTZGOnFDMmlxSHNsNzhRaEdEWHQqTHpxcG9acWU5d3hzeg=="; And the post will have the following json: grant_type:'client_credentials' Hope this helps |
Hey @zaharuks, with the info you provided I was able to modify it and get it working again. HUGE thank you, saved me a lot of digging. |
Interesting! I have been traveling but will try and put out a fix asap. Thanks for investigating! |
@zaharuks @CJWTX can you confirm that https://github.com/jwoglom/tconnectsync/releases/tag/v1.0.0 fixes the issue for you? |
I’ve been running the modified version I made, I’ll deploy yours later to see if it’s working properly |
@jwoglom 👋 I've upgraded and can confirm that 1.0.0 fixes the issue for me. Thank you for a quick fix on this! ✨ I've opened a PR on tconnectsync-heroku to pull in the latest release, for other folks using that version. |
I have two different instances of tconnectsync-heroku. As of this moment neither has been able to successfully login to Tconnect for almost a day. Both are seeing the same issues.
The text was updated successfully, but these errors were encountered: