Logged in as an Administrator, I've manually added a few users to SonarQube. However, when trying to assign an issue, these users are not listed.
Is there some level of permissions that need to be granted to these users to be able assign issues to them?
This actually just seems to be the case where the documentation does not match the product. The documentation shows users in the drop-down:
The actual product shows as in my question:
But if you type in the Search... field, you actually can find the person and make the assignment:
Related
I am using soarqube version 8.4.2. We have different groups to review code in sonarqube. but i need to create one group, whose user can just check and see reports and can not access/ update issue or bug from dashboard of sonarqube.
I have tried over internet but i could not find any suitable stpes to restrict user for it.
I would appreciate if any one share me suggestion, or document regarding it.
Thanks in advance.
In Sonarqube, Go to the Project for which you want to apply permissions for a group of users.
Then, click on the drop down tab Administration >> Permissions >> Click on Groups
Then, search for the Group for which you want to apply permissions.
There are 6 different types of permissions, you can assign to a group or users.
Types of Permissions available under Project Administration are:
Browse: Access a project, browse its measures and issues, confirm issues, change the assignee, comment on issues and change tags.
See Source Code: View the project's source code. (Users will also need "Browse" permission)
Administer Issues: Change the type and severity of issues, resolve issues as being "fixed", "won't fix" or "false-positive" (users also need "Browse" permission).
Administer Security Hotspots: Open a Vulnerability from a Security Hotspot. Resolved a Security Hotspot as reviewed, set it as in review or reset it as to review (users also need Browse permission).
Administer: Access project settings and perform administration tasks. (Users will also need "Browse" permission)
Execute Analysis: Ability to get all settings required to perform an analysis (including the secured settings like passwords) and to push analysis results to the SonarQube server.
For your case, you can assign the Browse and See Source code. Please find the screenshot:
Note: You need administrator access to perform this permission changes.
We have a running instance of Sonar 6.2 that's been upgraded from sonar 4.5.x and since the beginning we have used the LDAP plugin to recover user data.
Once upgraded to the 6.2 version we have noticed that we can't authorize new users and groups to projects, because we can't see them.
If we select a project and go to the users tab on the project's permisions section we get this, in spite of having this users list. And if we select the groups tab we only see the previously groups assignated and not the rest of the existing ones.
Help is appreciated.
Thanks in advance.
By default, the list you see on project Administration > Permissions > Users is the list of people with permissions on the project. Since you haven't assigned any users permissions on the project, the list is blank by default. Why not show everyone by default? Imagine a SonarQube instance with hundreds of users. You certainly wouldn't want to see them all there by default. Instead, you only want to see the ones relevant to your current context; the ones with existing permissions on the project.
To find your missing users, try entering a username in the search input. Matching users should appear in the list area so you can enable permissions for them.
I am using SonarQube (SQ) 6.0 community version and trying to setup authorization using groups and project permissions. There doesn't appear to be a way to assign permissions to a created group, even though the defined SQ groups have permissions assigned to them. What I wanted to do was assign permissions to a created group via the Admininistration->Security->Global Permissions process. But this action only returns the Anyone and sonar-administrators defined groups based on the usage of the internal API api/permissions/groups, which only returns groups with permissions. This same API is used in the action Administration->Projects->Management->Actions->Edit Permissions. From this last action the goal was to remove permissions for this project from the Anyone group and allow permissions from a created group (which would apply to the users in that group). But that doesn't seem possible. I've looked at permission templates, but that doesn't seem to allow association to a group. What I'm really attempting to do is a common RBAC process, which SQ does not seem to support. Is there a solution in SQ for this capability?
Yup, the UI is very confusing in this area, I struggled for quite some time before realising what to do.
What you need to do is first search for a string in the search box ("sonar" is a good query), and then the list will be populated with all users/groups matching that query. You can then assign them permissions as you see fit.
There are two different concepts at work here. Global permissions grant users and groups the ability to make global-level changes, i.e. changes that effect everyone such as which plugins are installed and what rules are active in a Quality Profile. Project permissions grant users and groups the ability to see and change individual projects.
Once your group is created and populated, you have two options:
Edit Permissions of Individual Permissions
Give the group specific permissions to individual projects by navigating to the project, then Administration > Permissions. This could get tedious if you have a lot of projects to update.
Create a Permissions Template
Create a permission template (Administration > Security > Permission Templates) and populate it by granting the group specific permissions. At this point no permissions have actually changed.
Once your template is properly constructed, you can apply it to projects individually, en masse, and/or by default as new projects are created via the template's Project Key Pattern. You can also make your new template the default so that its settings are automatically applied to all new projects regardless of project key.
Note that there is no ongoing relationship between a Permissions Template and the projects to which it has been applied. Subsequently editing a template will not update the permissions of any project.
I have been watching a strange issue that is making me think that TYPO3 has a sort of user configuration cache and don't know how to clean it.
The website has some users and some groups of users. There are some extensions to manage records on tables.
Some of the fields of those extensions are of type "group" to reference files.
The strange thing is that the old users in the same group don't see the upload button in those fields, but when create new users in the same group they do see the button.
There is no difference between the configuration of the old and new users.
What might be happening?
More Info:
They are BE users and the problem is in the Web->List view.
No special modules and no disabled_controls in the TCA for those fields.
It is also interesting that if I duplicate an old user, the duplicated one is not able to see the buttons, either.
Images
This is how the old users see the fields:
And, this is how the new users see the field:
I would expect, that there are Options in TSUser Config or in user settings are set.
Have a look in TSConfig of that Users and Usergroups:
setup.default.edit_docModuleUpload = 0
setup.override.edit_docModuleUpload = 0
Perhaps it is set in the user settings:
I have set up user group called "Article Editor" with a parent of Administrator. Within that group I have a user of "Agent" and assigned them to the "Article Editor" User group.
I have a blog page in which when they are logged in they can create an article (only with a particular category called blog) and they can edit all articles, however, I cannot get any option anywhere to enable them to delete any article they have created within the "blog" category. I have gone into the article manage and made sure the permissions are set to enable Edit, Delete and Create.
Any ideas how I allow the user to log into the front end and have the option to delete? Ive tried everything I can think of an am going around in circles now.
The Delete permission should be given only to trusted administrators (with intended access to the back-end) and can be performed in the back-end.
From your description, you don't want this group of users to have access in the back-end and even more have delete permissions, as these users if they log-in to the backend they will be able to delete many things.
These users should be able to edit state (publish/unpublish) their own articles.
So, concluding:
Give this group only front-end access, with permissions similar to the author (core joomla group) with the addition of edit state.
So they will be able to create and publish/unpublish (**addition- or trashing) their articles.