User is unable revoke a Authorized application unless User OAuth applications is checked in admin settings
Summary
A user is unable to to access /profile/applications if "User OAuth applications" is checked in the admin section. So they are unable to revoke a authorized application.
I would like to setup a couple of system wide applications that my users can use to OAuth to gitlab but I do not want them to be able to add their own. However they should still need to be able to revoke them.
Steps to reproduce
Add a application in the admin section. make sure "User OAuth applications" under the "Account and limit settings" is unchecked. Use the application with gitlab. You will now have a authorized application on your account you are unable to revoke.
Example Project
This does not happen on gitlab.com
What is the current bug behavior?
If you try and access /profile/applications while "User OAuth applications" under the "Account and limit settings" is unchecked you will be redirected back to /profile
What is the expected correct behavior?
That you would be able to access /profile/applications but only be able to see the authorized applications and revoke them not add a new application as user.
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Ubuntu 14.04 Current User: git Using RVM: no Ruby Version: 2.3.7p456 Gem Version: 2.6.14 Bundler Version:1.13.7 Rake Version: 12.3.1 Redis Version: 3.2.11 Git Version: 2.16.4 Sidekiq Version:5.0.5 Go Version: unknown
GitLab information Version: 10.8.3 Revision: 564c342 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql URL: https://gitlab.rmsginc.com HTTP Clone URL: https://gitlab.rmsginc.com/some-group/some-project.git SSH Clone URL: git@gitlab.rmsginc.com:some-group/some-project.git Using LDAP: no Using Omniauth: no
GitLab Shell Version: 7.1.2 Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
Checking GitLab Shell ...
GitLab Shell version >= 7.1.2 ? ... OK (7.1.2) Repo base directory exists? default... yes Repo storage directories are symlinks? default... no Repo paths owned by git:root, or git:git? default... yes Repo paths access is drwxrws---? default... yes hooks directories in repos are links: ... 4/6 ... ok 4/7 ... ok 4/8 ... ok 4/9 ... ok 4/10 ... ok 4/11 ... ok 4/12 ... ok 4/14 ... ok 4/16 ... ok 3/17 ... ok 4/18 ... ok 4/19 ... ok 4/20 ... ok 4/21 ... ok 4/23 ... ok 4/24 ... ok 4/25 ... ok 4/26 ... ok 4/27 ... ok 4/28 ... ok 4/30 ... ok 4/31 ... ok 4/32 ... ok 4/33 ... ok 4/34 ... ok 4/35 ... ok 4/36 ... ok 4/37 ... ok 4/38 ... ok 2/39 ... repository is empty 4/40 ... ok 4/41 ... ok 4/42 ... ok 4/43 ... ok 4/44 ... ok 6/45 ... ok 6/46 ... ok 6/47 ... ok 6/49 ... ok 6/50 ... ok 8/51 ... ok 9/53 ... ok 6/54 ... ok 6/55 ... ok 6/57 ... ok 6/58 ... ok 6/59 ... ok 6/60 ... ok 6/61 ... ok 6/62 ... ok 6/63 ... ok 6/64 ... ok 4/65 ... ok 4/67 ... ok 4/68 ... ok 6/69 ... ok 4/70 ... ok 4/71 ... ok 4/73 ... ok 4/74 ... ok 4/75 ... ok 10/76 ... ok 4/77 ... ok 11/78 ... ok 11/79 ... ok 10/80 ... ok 4/81 ... repository is empty 4/82 ... ok 12/83 ... ok 12/84 ... ok 4/85 ... ok 10/87 ... ok 2/88 ... ok 3/89 ... ok 2/90 ... ok 11/91 ... ok 2/92 ... ok 2/93 ... ok 11/94 ... ok 3/95 ... ok 2/96 ... ok 2/97 ... ok 7/98 ... ok 3/99 ... repository is empty 15/100 ... ok 4/101 ... ok 2/102 ... ok 3/103 ... ok 3/104 ... ok 3/105 ... ok 3/106 ... ok 3/107 ... ok Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Check GitLab API access: OK Redis available via internal API: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Reply by email is disabled in config/gitlab.yml Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 4/6 ... yes 4/7 ... yes 4/8 ... yes 4/9 ... yes 4/10 ... yes 4/11 ... yes 4/12 ... yes 4/14 ... yes 4/16 ... yes 3/17 ... yes 4/18 ... yes 4/19 ... yes 4/20 ... yes 4/21 ... yes 4/23 ... yes 4/24 ... yes 4/25 ... yes 4/26 ... yes 4/27 ... yes 4/28 ... yes 4/30 ... yes 4/31 ... yes 4/32 ... yes 4/33 ... yes 4/34 ... yes 4/35 ... yes 4/36 ... yes 4/37 ... yes 4/38 ... yes 2/39 ... yes 4/40 ... yes 4/41 ... yes 4/42 ... yes 4/43 ... yes 4/44 ... yes 6/45 ... yes 6/46 ... yes 6/47 ... yes 6/49 ... yes 6/50 ... yes 8/51 ... yes 9/53 ... yes 6/54 ... yes 6/55 ... yes 6/57 ... yes 6/58 ... yes 6/59 ... yes 6/60 ... yes 6/61 ... yes 6/62 ... yes 6/63 ... yes 6/64 ... yes 4/65 ... yes 4/67 ... yes 4/68 ... yes 6/69 ... yes 4/70 ... yes 4/71 ... yes 4/73 ... yes 4/74 ... yes 4/75 ... yes 10/76 ... yes 4/77 ... yes 11/78 ... yes 11/79 ... yes 10/80 ... yes 4/81 ... yes 4/82 ... yes 12/83 ... yes 12/84 ... yes 4/85 ... yes 10/87 ... yes 2/88 ... yes 3/89 ... yes 2/90 ... yes 11/91 ... yes 2/92 ... yes 2/93 ... yes 11/94 ... yes 3/95 ... yes 2/96 ... yes 2/97 ... yes 7/98 ... yes 3/99 ... yes 15/100 ... yes 4/101 ... yes 2/102 ... yes 3/103 ... yes 3/104 ... yes 3/105 ... yes 3/106 ... yes 3/107 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.3.5 ? ... yes (2.3.7) Git version >= 2.9.5 ? ... yes (2.16.4) Git user has default SSH configuration? ... yes Active users: ... 6
Checking GitLab ... Finished
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
Solution
- When User OAuth disabled you can only see and revoke apps and when User OAuth enabled you can create apps too.
- add the following call-out above the table when its not possilbe:
Adding new applications is disabled in your GitLab instance. Please contact your GitLab administrator to get the permission