Bob Trahan eee8d194eb OAuthServer - default "whoami" scope and refine scope-asking workflow ... Summary: Ref T7153. The "whoami" scope should be default and always on, because otherwise we can't do anything at all. Also, if a client doesn't want a certain scope, don't bother asking the user for it. To get there, had to add "scope" to the definition of a client. Test Plan: applied the patch to a phabricator "client" and a phabricator "server" as far as oauth shenanigans go. Then I tried to login / register with oauth. If the "client" was configured to ask for "always on" access I got that in the dialogue, and otherwise no additional scope questions were present. Verified scope was properly granted in either case. Reviewers: epriestley Reviewed By: epriestley Subscribers: Korvin, epriestley Maniphest Tasks: T7153 Differential Revision: https://secure.phabricator.com/D11705		2015-02-06 15:32:55 -08:00
..
client	OAuthServer - hide client secret behind a "View Secret" action	2015-01-14 17:27:45 -08:00
PhabricatorOAuthServerAuthController.php	OAuthServer - default "whoami" scope and refine scope-asking workflow	2015-02-06 15:32:55 -08:00
PhabricatorOAuthServerController.php	PHUIErrorView	2015-02-01 20:14:56 -08:00
PhabricatorOAuthServerTestController.php	Use modern UI for OAuthServer details page	2014-03-18 15:39:45 -07:00
PhabricatorOAuthServerTokenController.php	Remove @group annotations	2014-07-10 08:12:48 +10:00