[JENKINS-61589] role-strategy-plugin does not respect distributed lists

[jenkins-infra-bot]

Hi,

we are trying to get the role-strategy-plugin working without success using distributed lists.

Assigning item roles to a DL is working but the user inside the DL does not receive any permissions.

Assigning a single user is working so the pattern works but does not make sense because we have a lot of users.

The DL is listed with a group symbol so my guess is that AD is working in my eyes so no problems here.

 

Is someone else having this problem?

 

Thanks and best regards

Tobias

---

Originally reported by toho, imported from: role-strategy-plugin does not respect distributed lists

• assignee: oleg_nenashev
• status: Open
• priority: Major
• component(s): role-strategy-plugin
• resolution: Unresolved
• votes: 0
• watchers: 2
• imported: 20251211-223321

Raw content of original issue

Hi,

we are trying to get the role-strategy-plugin working without success using distributed lists.

Assigning item roles to a DL is working but the user inside the DL does not receive any permissions.

Assigning a single user is working so the pattern works but does not make sense because we have a lot of users.

The DL is listed with a group symbol so my guess is that AD is working in my eyes so no problems here.

 

Is someone else having this problem?

 

Thanks and best regards

Tobias

environment

Jenkins ver. 2.225<br/>
openjdk version 1.8.0_242<br/>
role-strategy-plugin 2.16<br/>
Linux Ubuntu 16.04

1 attachment

• Screenshot.jpg

  

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

  My guess is that the Active Directory plugin does not properly list authorities in the distributed lists. It can be checked by going to the /whoAmI page for users who are supposed to have permissions.
  
  Also, there are some permission caching issues reported for recent weekly releases. I still need to investigate them, but it would be great if you could check whether the issue remains after the restrt
  

My guess is that the Active Directory plugin does not properly list authorities in the distributed lists. It can be checked by going to the /whoAmI page for users who are supposed to have permissions.

Also, there are some permission caching issues reported for recent weekly releases. I still need to investigate them, but it would be great if you could check whether the issue remains after the restrt

[jenkins-infra-bot]

toho:

• Original comment link
• Raw content of original comment:

  oleg_nenashev Thanks. The DL we assigned to roles is listed in the /whoAmI page of the users. What should I restart? Jenkins? We already did that many times. The problem exists since we installed the plugin in October 2019.
  

oleg_nenashev Thanks. The DL we assigned to roles is listed in the /whoAmI page of the users. What should I restart? Jenkins? We already did that many times. The problem exists since we installed the plugin in October 2019.

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

  Then I will investigate it as a part of the general caching problem.
  
  If you could provide an Active Directory Docker image which helps to reproduce the issue, it would help. I do not have AD, and I doubt I will be able to quickly reproduce the issue
  

Then I will investigate it as a part of the general caching problem.

If you could provide an Active Directory Docker image which helps to reproduce the issue, it would help. I do not have AD, and I doubt I will be able to quickly reproduce the issue

[jenkins-infra-bot]

toho:

• Original comment link
• Raw content of original comment:

  oleg_nenashev Nope sorry. Another department is responsible for our AD. Let me know if you need further information.
  

oleg_nenashev Nope sorry. Another department is responsible for our AD. Let me know if you need further information.

[jenkins-infra-bot]

ianw:

• Original comment link
• Raw content of original comment:

  toho, just wondering if perhaps all the rest of these were created in error; they appear  to be duplicates of this:
  Bug   Major  JENKINS-61543
  Bug   Major  JENKINS-61544
  Bug   Major  JENKINS-61552
  Bug   Major  JENKINS-61567
  Bug   Major  JENKINS-61585
  Bug   Minor  JENKINS-61549
  Task  Major  JENKINS-61551
  

toho, just wondering if perhaps all the rest of these were created in error; they appear  to be duplicates of this:
Bug   Major  JENKINS-61543
Bug   Major  JENKINS-61544
Bug   Major  JENKINS-61552
Bug   Major  JENKINS-61567
Bug   Major  JENKINS-61585
Bug   Minor  JENKINS-61549
Task  Major  JENKINS-61551

[jenkins-infra-bot]

toho:

• Original comment link
• Raw content of original comment:

  ianw wow okay, I was not aware that this ticket was duplicated 7 times. Sorry. I don't have the permission to close them.
  

ianw wow okay, I was not aware that this ticket was duplicated 7 times. Sorry. I don't have the permission to close them.

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

   Yes. The current state of the tracker is a mess. Due to some personal reasons, I have been unable to secure time for a proper caching fix
  

 Yes. The current state of the tracker is a mess. Due to some personal reasons, I have been unable to secure time for a proper caching fix