Status: Closed (View Workflow)
Resolution: Not A Defect
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?
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.
If we need to give application team access to particular application jenkins folder , then how this can be achieved using role based strategy.
|Field||Original Value||New Value|
|Component/s||saml-plugin [ 20321 ]|
|Resolution||Not A Defect [ 7 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
this is not an issue is a support request please use the google groups for questions, also reed the documentation of the plugins you question is there https://www.jenkins.io/participate/report-issue/#:~:text=For%20Infrastructure%2C%20if%20you're,urgently%20you%20want%20it%20fixed.