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.
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.
In Joomla 2.5 I have a custom component installed that is only available to the Administrator. I would like to make this component available to the Manager Group as well.
Can someone please tell me what file I must edit? Is it an XML file in the administrator/components/name_here/? Or is this a lot more complicated than I think?
I hope I am reading the right file, this Joomla system is a mad hatter.
It's not just an XML file your component will need to check the permissions a user has.
Since Joomla! 1.6 there is an extensive Access Control (ACL) mechanism implemented for front-end and backend access. You can define an unlimited number of Groups all with different access levels on a per component basis (this presumes that the component is written correctly). The default groups that are created with the initial setup can be deleted or renamed and may not to exist on all installations, users can create groups of any name with any range of permissions.
I would recommend starting with the Access Control List/2.5/Tutorial this will give you a better understanding of the new ACL.
Then from the "Developing a Model-View-Controller Component/2.5" tutorial, re-read "Adding ACL" article, if you need custom rules you will probably want to read the Adding ACL Rules to your component article as well.
I have Joomla site using JCE. I use the JCE groups to create permissions for different users.
I have created few groups and every group is permitted to control one media directory.
I have combined a specific user to two different groups assuming that this user will have the ability to access two different media directories.
But the user can access only one directory -- the first one I have assigned.
Can anybody help me to fix this problem?
What should I do in order to give a specific user access to different directories?
Does it affect the way joomla authenticate users if I add a custom user groups in the Joomla 1.5.15 and does it make it less secure?
I'm planning to add a custom group using the table jos_core_acl_aro_groups as described at http://docs.joomla.org/Custom_user_groups.
But someone told me that if I add a new user group and the group_id is greater than 25 (this is the ID of the Super Administrator), that new group will have the same access as the super admin in the default joomla core files without changing anything just the additional user group. Is this true?
Don't you have a local instsall of Joomla to try this?
Anyways, it's not true because it can't be, why should the group_id define the access rights? That would be a terrible ACL implementation. But please try it, before you actually use it live.
In Joomla 1.5 you can make user groups but they will have one of the existing role patterns. In Joomla 1.6 (alpha) there will be full flexibility in defining your groups, roles and granular ownership settings for each article, module, etc.
There are several extension you can find at:
http://extensions.joomla.org/extensions/access-a-security
Which enhance the core ACL functions. Give them a look and you'll probably find the solution without hacking the core files.