Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-11829

Support more than one group

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      We currently use the old crowd plugin wich did not require you to specify a group in its configuration.
      The old plugin got all groups from crowd and then we could use the "Matrix-based security" under "Authorization" in Jenkins to set the permissions for the different groups.

      We have three groups with access to Jenkins with different Authorization-schemes:
      jenkins-administrators
      jenkins-developers
      jenkins-users

      It would be great if this plugin could support this way of delegating the Authorization.

        Attachments

          Activity

          Hide
          t_heit Thorsten Heit added a comment -

          Hi Jens-Martin,

          as I wrote in the wiki page, the need to specify a group name in the configuration page is mainly to restrict who at all should be allowed to log in. This doesn't restrict the names and number of groups that you can use in matrix-based security. Well, as long as users in such a group are also members of the login group.

          In your case, I'd assume the following relationship:
          jenkins-users < jenkins-developers < jenkins-administrators

          In the actual plugin version you therefore would specify "jenkins-users" as login group name because the dev group aggregates the users and admin aggregates the dev group. Then everything should work out of the box.

          Anyway, I'm adding your request to the to-do-list.

          Regards

          Thorsten

          Show
          t_heit Thorsten Heit added a comment - Hi Jens-Martin, as I wrote in the wiki page, the need to specify a group name in the configuration page is mainly to restrict who at all should be allowed to log in. This doesn't restrict the names and number of groups that you can use in matrix-based security. Well, as long as users in such a group are also members of the login group. In your case, I'd assume the following relationship: jenkins-users < jenkins-developers < jenkins-administrators In the actual plugin version you therefore would specify "jenkins-users" as login group name because the dev group aggregates the users and admin aggregates the dev group. Then everything should work out of the box. Anyway, I'm adding your request to the to-do-list. Regards Thorsten
          Hide
          ratn Ratn Dwivedi added a comment -

          1.Please allow possibility of multiple flat groups
          2.provide option for application wide authentication

          Show
          ratn Ratn Dwivedi added a comment - 1.Please allow possibility of multiple flat groups 2.provide option for application wide authentication
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Thorsten Heit
          Path:
          pom.xml
          src/main/java/de/theit/jenkins/crowd/CrowdAuthenticationManager.java
          src/main/java/de/theit/jenkins/crowd/CrowdConfigurationService.java
          src/main/java/de/theit/jenkins/crowd/CrowdSecurityRealm.java
          src/main/java/de/theit/jenkins/crowd/CrowdUserDetailsService.java
          src/main/java/de/theit/jenkins/crowd/ErrorMessages.java
          src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/config.jelly
          src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/config_de.properties
          src/main/resources/de/theit/jenkins/crowd/ErrorMessages.properties
          src/main/resources/de/theit/jenkins/crowd/ErrorMessages_de.properties
          http://jenkins-ci.org/commit/crowd2-plugin/2afc1ab37c46474ec055bdd42696349b5912c595
          Log:
          Fixes for the following issues:

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Thorsten Heit Path: pom.xml src/main/java/de/theit/jenkins/crowd/CrowdAuthenticationManager.java src/main/java/de/theit/jenkins/crowd/CrowdConfigurationService.java src/main/java/de/theit/jenkins/crowd/CrowdSecurityRealm.java src/main/java/de/theit/jenkins/crowd/CrowdUserDetailsService.java src/main/java/de/theit/jenkins/crowd/ErrorMessages.java src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/config.jelly src/main/resources/de/theit/jenkins/crowd/CrowdSecurityRealm/config_de.properties src/main/resources/de/theit/jenkins/crowd/ErrorMessages.properties src/main/resources/de/theit/jenkins/crowd/ErrorMessages_de.properties http://jenkins-ci.org/commit/crowd2-plugin/2afc1ab37c46474ec055bdd42696349b5912c595 Log: Fixes for the following issues: JENKINS-11829 : Support more than one group JENKINS-13547 : Jenkins runs extremely slow with remote crowd server

            People

            Assignee:
            t_heit Thorsten Heit
            Reporter:
            jensmartin Jens-Martin Groenne
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: