search

itsMeDavidV / Watchla-Support

This repository is dedicated for support with issues and bugs related to the Watchla beta & production apps
11 stars 3 forks source link

ver 3.5.1 no more sign-in token #207

Open skipcooney opened 10 months ago

skipcooney commented 10 months ago

Updated to version 3.5.1. Was asked to sign out and sign back in. When I try to sign in the iOS app does not give me an option of signing in using my token. Only offers sign in using Tesla account.

ngkonchin commented 10 months ago

I have the same issue. Do we have a resolution this?

skipcooney commented 10 months ago

Still no option to sign in using a token

ngkonchin commented 10 months ago

I kinda gave up, but it started working on the watch. I didn't do anything special, I guess it took some time to sync iPhone with ultra watch. iPhone and watch have the latest software release installed.

On Wednesday, January 17, 2024 at 12:48:03 PM EST, skipcooney ***@***.***> wrote:

Still no option to sign in using a token

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

skipcooney commented 10 months ago

@ngkonchin - My watch app will not launch. It just ask me to authenticate my account in the Watchla IOS app. I'm not willing to use my Tesla username and password to sign in to the IOS app.

ngkonchin commented 10 months ago

Follow the steps to authenticate from Watchla App on the iPhone. Watchla redirect you to Tesla website and there is an option to allow third party to have access to certain commands. Just select the commands you which to grant and that’s it. If you don’t trust the redirect, you can do the same by going to the Tesla website (that’s what I did), sign in and select option to grant access to third party.

On the Watch delete Watchla (swipe left then tap on delete). Once deleted you’ll get an option to install the app again from the Watch app on your iPhone. Once completed then click refresh on the Watch app then stop and wait. It took mine an hour or so to sync up with the watch. That’s why I mentioned, I gave up and it started working.

Hope this help, those are the steps I took, the key is to stop and wait after you reinstall the app.

On Jan 17, 2024, at 3:20 PM, skipcooney @.***> wrote:

@ngkonchin https://github.com/ngkonchin - My watch app will not launch. It just ask me to authenticate my account in the Watchla IOS app. I'm not willing to use my Tesla username and password to sign in to the IOS app.

— Reply to this email directly, view it on GitHub https://github.com/itsMeDavidV/Watchla-Support/issues/207#issuecomment-1896628606, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFKIUAG7PLQYMC2Y2PKWHMLYPAXATAVCNFSM6AAAAABBZMVNBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJWGYZDQNRQGY. You are receiving this because you were mentioned.

skipcooney commented 10 months ago

@ngkonchin thanks for the detailed instructions. For now I’ll wait to see if the developer brings back authentication using tokens.

ngkonchin commented 10 months ago

I think Tesla updated their API how to communicate with the vehicle. It’s still using tokens on the backend to validate credentials. The developer of watchla needs to register and approve by Tesla before access is granted.

On Jan 17, 2024, at 5:21 PM, skipcooney @.***> wrote:

@ngkonchin https://github.com/ngkonchin thanks for the detailed instructions. For now I’ll wait to see if the developer brings back authentication using tokens.

— Reply to this email directly, view it on GitHub https://github.com/itsMeDavidV/Watchla-Support/issues/207#issuecomment-1897118054, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFKIUADB5CJI2DB32RXGYYTYPBFF3AVCNFSM6AAAAABBZMVNBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJXGEYTQMBVGQ. You are receiving this because you were mentioned.

flmeng1978 commented 10 months ago

It sound reasonable

skipcooney commented 10 months ago

Updated to 3.5.2 today. Still no option to sign in to the IOS app with a token.

itsMeDavidV commented 10 months ago

Hi everyone, so this will be posted on the FAQs very soon, but I wanted to touch base with you all first.

When I first started Watchla years ago, some other developers were still requiring actual passwords in their own input fields for them to use their apps and it was truly the wild west.

For obvious reasons, (both for pro-trust and pro-liability/security) I never wanted this to be the case for Watchla and so it never was.

Watchla has always used Tesla's official OAuth sign-in webpage instead of allowing users to sign in with Watchla controlled input fields directly. This is akin to 'Sign in with Google' on your favorite app or website. And going one-step further, Watchla has always included token sign-in for those who want total control over the token creation process, until now.

Fast-forward to now and a lot has changed. For starters, the old Tesla API that was open to everyone with a Tesla account is now getting phased out and there is a new API in its place only open to registered developers who are directly approved by Tesla. According to Tesla's schedule most vehicles can now only use the new Tesla API and are incompatible with the old API.

Furthermore, tokens are not the same as they once were. Before you could create a Tesla SSO token yourself and use it on any app like Watchla or other 3rd party Tesla apps and everything would work smoothly. Now only approved developers can create Tesla API tokens and these tokens are hard-locked to the registered developers that create them. For those with networking knowledge, tokens must be passed to Tesla servers with their associated client IDs. Tokens passed with non-associated clientIDs will be rejected. This means as an individual, you now cannot use a token you generated with any apps that you are not the developer of, like Watchla. Adding to that, signed commands will also only work with a token that is associated with the virtual key used to verify said signed command. This is for good reason as it allows for Tesla or you to disable a specific app's access remotely via the token that was created by said app.

While this transition to the new API makes it impossible for Watchla to offer token sign in, it also adds much more security and peace of mind to using 3rd party Tesla apps in general. For starters, with the new Tesla API you:

So while I'm personally a little sad to see token sign in go, I'm also very happy that Tesla has taken these very necessary steps to drastically improve the security of the Tesla API and your Tesla account.

-David

PS: I'll be leaving this issue open until this FAQ is up so others can see.

skipcooney commented 10 months ago

Thank you David for explaining why we can no longer authenticate with tokens. When I sign in with my Tesla account credentials, what are the minimum app permissions needed for Watchla to work? What if I only want the bluetooth key feature?