> So one way to handle this from your side would be to just forget the > user's OAuth tokens. Your app will still appear "authorized" to the user > in the connections screen, which would be confusing, but your > application wouldn't be able to perform any operations on their behalf.
its really cool, but i need to see login and password field i dont wonna be authorized i need it for changed of users, and user would not do extra work, only enter login and password > It might be useful to have a "destroy credentials" endpoint though, to > remove your app from the connections screen. what you means? PS I fully agree with Ken and i need it
