-
Notifications
You must be signed in to change notification settings - Fork 354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"$user is missing the Job/Configure permission" error when using Role-Based Authorization Strategy #823
Comments
Was it the Role-based Authorization Strategy plugin that caused this issue, or a change in the Bitbucket Branch Source plugin? Do we know exactly which version caused the problem? I need to rollback, and can't figure this out. |
I have this error too. Did you find a solution? |
Is there any fix to this? |
The same author of this issue has proposed a PR that has been merged. Unfortunately the github user has been deleted so we will never get a feedback for this issue. |
I'm not able to replicate the issue with suggested steps
The user I create with the following permission I had create an Organization Folder than I had navigate branch job feature/test and click on View Configuration http://localhost:8090/jenkins/job/test/job/feature%252Ftest/configure |
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Ubuntu Linux 22.04
Reproduction steps
Expected Results
The "Branch sources" section of the Configuration page shows the current Bitbucket configuration.
Actual Results
An iframe (?) of the Jenkins instance is shown instead, with the following error message:
$user is missing the Job/Configure permission
(where$user
is the username of the currently logged in user). None of the fields are clickable.This happens even if the current user has that permission, and even if the current user has the
admin
role.See attached screenshot.
Anything else?
No response
Are you interested in contributing a fix?
Yes, see linked PR.
The text was updated successfully, but these errors were encountered: