Indicate requirements that need to be met in order to remove an OAuth account #17799
michael-tharrington
started this conversation in
Feature Requests
Replies: 2 comments
-
thanks for this suggestion @michael-tharrington ! |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi there @michael-tharrington and @maestromac : do you need a help with this? I think this feature here as well as this one Allow to add Mastodon profile URLs would be really valuable to the current state of the internet (and 🤞 to the near future)! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Background
A community member recently wrote in and asked how they might unlink their Twitter account (OAuth) from their DEV account.
My explanation summed up was:
The community member wrote back and was grateful for direction, but they mentioned
I agree that it would be quite helpful if the "Remove Twitter" button would appear but be greyed out with an explanation to connect another authorization method for the option to disconnect.
Change Requested
Currently, if you only have 1 OAuth account connected to your DEV account, then you do not see the option to Remove OAuth Associations (see pick below) under the "Danger Zone"
Ideally, this section should still be viewable even with just 1 OAuth account connected, but the button to "Remove Twitter" (or GitHub/Forem Account) should be greyed out with an explanation that 1 OAuth account must always be connected to your account.
Outcome
Hopefully this would help DEV community members to solve their OAuth issues on their own because they would have an explanation in place in the UI as to why they can't remove their own OAuth and what they need to do to make that happen.
Beta Was this translation helpful? Give feedback.
All reactions