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

Role-based Authorization Strategy: Naming Strategy = Role-Based Strategy is not working

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • role-strategy-plugin
    • None
    • Jenkins 2.319.1, Role-based Authorization Strategy 3.2.0

    Description

      Role-based Authorization Strategy plug-in provides Naming Strategy = Role-Based Strategy in Configure System. With this option:

      • If a user doesn't have global Job > Create permission then New Item menu item disappears for a user and creation of jobs becomes impossible. This is not how it's supposed to work per plug-in docs. User with item role and item Job > Create permission should be able to create jobs following a pattern defined in Item roles.
      • If a user does have global Job > Create permission then the user can create any job: this is working as documented.

      Attachments

        Activity

          dk Dmitriy Korobskiy created issue -
          dk Dmitriy Korobskiy made changes -
          Field Original Value New Value
          Description Role-based Authorization Strategy plug-in provides Naming Strategy = Role-Based Strategy in Configure Systems. With this option:

          * If a role doesn't have global Job > Create permission then New Item menu item disappears for a user and creation of jobs becomes. This is not how it's supposed to work per plug-in docs. User with item role and item Job > Create permission should be able to create jobs following a pattern defined in Item roles.
          * If a roles does have global Job > Create permission then the user can create *any* job: this is working as documented.
          Role-based Authorization Strategy plug-in provides Naming Strategy = Role-Based Strategy in Configure Systems. With this option:

          * If a role doesn't have global Job > Create permission then New Item menu item disappears for a user and creation of jobs becomes impossible. This is not how it's supposed to work per plug-in docs. User with item role and item Job > Create permission should be able to create jobs following a pattern defined in Item roles.
          * If a roles does have global Job > Create permission then the user can create *any* job: this is working as documented.
          dk Dmitriy Korobskiy made changes -
          Description Role-based Authorization Strategy plug-in provides Naming Strategy = Role-Based Strategy in Configure Systems. With this option:

          * If a role doesn't have global Job > Create permission then New Item menu item disappears for a user and creation of jobs becomes impossible. This is not how it's supposed to work per plug-in docs. User with item role and item Job > Create permission should be able to create jobs following a pattern defined in Item roles.
          * If a roles does have global Job > Create permission then the user can create *any* job: this is working as documented.
          Role-based Authorization Strategy plug-in provides Naming Strategy = Role-Based Strategy in Configure Systems. With this option:

          * If a user doesn't have global Job > Create permission then New Item menu item disappears for a user and creation of jobs becomes impossible. This is not how it's supposed to work per plug-in docs. User with item role and item Job > Create permission should be able to create jobs following a pattern defined in Item roles.
          * If a user does have global Job > Create permission then the user can create *any* job: this is working as documented.
          dk Dmitriy Korobskiy made changes -
          Description Role-based Authorization Strategy plug-in provides Naming Strategy = Role-Based Strategy in Configure Systems. With this option:

          * If a user doesn't have global Job > Create permission then New Item menu item disappears for a user and creation of jobs becomes impossible. This is not how it's supposed to work per plug-in docs. User with item role and item Job > Create permission should be able to create jobs following a pattern defined in Item roles.
          * If a user does have global Job > Create permission then the user can create *any* job: this is working as documented.
          Role-based Authorization Strategy plug-in provides Naming Strategy = Role-Based Strategy in Configure System. With this option:

          * If a user doesn't have global Job > Create permission then New Item menu item disappears for a user and creation of jobs becomes impossible. This is not how it's supposed to work per plug-in docs. User with item role and item Job > Create permission should be able to create jobs following a pattern defined in Item roles.
          * If a user does have global Job > Create permission then the user can create *any* job: this is working as documented.
          fvila Francis made changes -
          Attachment image-2022-04-15-14-20-59-034.png [ 57703 ]
          mawinter69 Markus Winter made changes -
          Assignee Oleg Nenashev [ oleg_nenashev ] Markus Winter [ mawinter69 ]

          People

            mawinter69 Markus Winter
            dk Dmitriy Korobskiy
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: