oauth/authorized should have its own permission, not "access content" [#2102793]

in my actual use case, the user trying to authenticate through oauth and returning to oauth/authorized (still anonymous at that stage) has not (and should not have) the "access content" permission.

I suggest that we have a specific permission for that menu entry.

Comment	File	Size	Author
#3	oauth-authorized_callback_permission-2102793-3.patch	909 bytes	Nitesh Sethia
#3
#1	oauth-authorized_callback_permission-2102793-1.patch	845 bytes	garphy
#1

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

File	Size
oauth-authorized_callback_permission-2102793-1.patch	845 bytes

My only comment is that it should appear first in the hook_permission list, rather than last, for consistency with other permissions normally the "safer" ones are at the top, and the "restricted" ones are at the bottom.