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

Group attribute is not working when adding to project based security marix using AWS SSO


      Hello Team,


      We are integrating Jenkins user with AWS single sign on. The AWS Single signon with Jenkins is working perfectly for us.

      In Jenkins, we have different project team who use Jenkins in their build and pipeline deployment and every project team should not be able to access other application team jenkins folder.


      Can you please let us know  whether below scenarios can be implemented in Jenkins or not?


      Scenario 1:

      Can we add groups which is present in AWS SSO under Jenkins project based matrix strategy and give required permission like build, create , read etc of that  particular project.


      Scenario 2:

      If we need to give application team access to particular application jenkins folder , then how this can be achieved using role based strategy.



            oleg_nenashev Oleg Nenashev
            ananda_1785 Ananda Bose
            0 Vote for this issue
            2 Start watching this issue