I went through OAuth with this 3rd party app using a new login email/password which I had just created. Now, I want to remove that account and use a different account for OAuth. I removed the account just fine, but when I try restarting OAuth, SmartThings automatically logs me in using the old login, but then I can’t do anything, since the account doesn’t exist!
Is there a way to remove this old OAuth auto-login and start again with a new one?
Here’s a follow up. After quite a few hours, SmartThings finally realized that the login their OAuth web page was automatically logging in, didn’t exist, and thus I was finally given a proper login page, so I was able to move to the login I wanted to use after all. I still don’t know how to force SmartThings OAuth page to ask for a login such that I could change accounts.
On the same theme.
Out of curiosity I just went to an OAuth-In test app of my own. I haven’t played with it for weeks, and probably months. I clicked on the link to connect to SmartThings and it jumped straight in with the Samsung account in use on my phone without asking. Yet if I go to account.samsung.com or my.smartthings.com in the same browser I am asked to login.
As a user there doesn’t seem to be anything that I am logged into that I can log out of. As an app developer all I am doing is making a call to the SmartThings OAuth that I only know how to do one way.
On the other hand, using Edge rather than Chrome did give me a login.
Yep, one user of my Pebble “Smart Stuff” app (which lets you turn on & off devices from your Pebble watch), keeps telling me that every time he’s taken to SmartThings OAuth page to get started, it asked for login & password, then asks for 2FA and then times out and exits before he can provide it! He has found no way around the 2FA, which I don’t think should even be asked during OAuth login, certainly not timed out! Strangeness from SmartThings.
Hi @rajid
Generally, when removing an OAuth service from the account, it can be done from the “Linked services” section by deleting the integration there.
Could you also please check if the same behavior happens when using an incognito/private browser window? We’d like to confirm whether this could be related to the browser cache.
Also, regarding the 2FA mention, just to confirm: do you have two-factor authentication enabled directly on your Samsung Account?
The issue of the OAuth account being logged in automatically was solved a few hours later, when I’m guessing SmartThings realized the account had been deleted.
The issue with 2FA coming into play during initial OAuth setup, is a problem of one of my app users, not me. I’m not sure what you’re asking, but since I’m going to be on the road soon, maybe I should just direct him to this conversation.
/raj(sent from iPhone)
Thanks for the clarification.
To continue investigating the 2FA issue affecting the other user, we would need the information directly from him. So, please ask him to follow this conversation and share the details from his side, since that will help us troubleshoot the behavior properly.