Z.J. van de Weg 0b81b5ace0 Create read_registry scope with JWT auth ... This is the first commit doing mainly 3 things: 1. create a new scope and allow users to use it 2. Have the JWTController respond correctly on this 3. Updates documentation to suggest usage of PATs There is one gotcha, there will be no support for impersonation tokens, as this seems not needed. Fixes gitlab-org/gitlab-ce#19219		2017-06-05 12:26:49 +02:00
..
admin	…
ci	…
concerns	…
dashboard	…
explore	…
groups	…
import	…
oauth	…
profiles	Create read_registry scope with JWT auth	2017-06-05 12:26:49 +02:00
projects	…
sherlock	…
snippets	…
abuse_reports_controller.rb	…
application_controller.rb	…
autocomplete_controller.rb	…
confirmations_controller.rb	…
dashboard_controller.rb	…
groups_controller.rb	…
health_check_controller.rb	…
health_controller.rb	…
help_controller.rb	…
invites_controller.rb	…
jwt_controller.rb	Create read_registry scope with JWT auth	2017-06-05 12:26:49 +02:00
koding_controller.rb	…
notification_settings_controller.rb	…
omniauth_callbacks_controller.rb	…
passwords_controller.rb	…
profiles_controller.rb	…
projects_controller.rb	…
registrations_controller.rb	…
root_controller.rb	…
search_controller.rb	…
sent_notifications_controller.rb	…
sessions_controller.rb	…
snippets_controller.rb	…
unicorn_test_controller.rb	…
uploads_controller.rb	…
users_controller.rb	…