Page MenuHomePhabricator

MWOAuthManageMyGrants: learn more link, separate revocation/management
Closed, ResolvedPublic

Description

UX requested that:

  • Since we will no longer mention OAuth on the preferences screen (bug 55716), and to allow users to understand what these "Connected Apps" are, add a "Learn More" link that links to a page about OAuth. (where?)
  • Instead of one link to "manage", have a separate link (or preferably, button) to deauthorize the Consumer. The "manage" form would only be used to update the grants.

Version: master
Severity: normal

Details

Reference
bz56021

Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 2:25 AM
bzimport set Reference to bz56021.

(In reply to comment #0)

  • Instead of one link to "manage", have a separate link (or preferably,

button) to deauthorize the Consumer. The "manage" form would only be used to
update the grants.

This part is taken care of by Gerrit change 91212, I believe.

So this would go in mwoauthmanagemygrants-text? Would it go to a blank local page by default? Maybe it could default to a policy page on the central wiki? This still pretty vague.

(In reply to comment #2)

So this would go in mwoauthmanagemygrants-text? Would it go to a blank local
page by default? Maybe it could default to a policy page on the central wiki?
This still pretty vague.

It is. I was looking for a way for the extension to insert a Manual: page, but there doesn't seem to be a way to do that.

Since Jared also recommended having the grants on /authorize link to a page where the exact rights are listed too, what about having Special:MWOAuth/about (or another special page entirely) that just outputs a bunch of text about the extension? The other option would be to have a translatable link that points to the Extension page on mw.o, and we can translate to other pages as needed?

(In reply to comment #3)

what about having
Special:MWOAuth/about
(or another special page entirely) that just outputs a bunch of text about
the extension? The other option would be to have a translatable link that
points to the Extension page on mw.o, and we can translate to other pages
as needed?

I'd go for the second option. It's a lot easier for non-developers to improve the user-facing help page when it's on mw.o instead of being contained in the i18n files in the code.

Change 92594 had a related patch set uploaded by Aaron Schulz:
Various grants management message cleanups

https://gerrit.wikimedia.org/r/92594

Change 92594 merged by jenkins-bot:
Various grants management message cleanups

https://gerrit.wikimedia.org/r/92594