-
Bug
-
Resolution: Timed out
-
Low
-
None
-
3.2
-
Severity 3 - Minor
-
The original issue is here: https://jira.atlassian.com/browse/BAM-9680 but it got overrun with a specific plugin error. So I'm raising another bug to track other plugins + the general problem
The only known JNDI classes used at the moment are LDAP related.
The current strategy is to fix it in individual plugins as it shows up.
- relates to
-
BAM-9680 Oauth Access Token and Plugin Manager option is broken when Bamboo integrate with LDAP with the cache attribute is set to false
-
- Closed
-
-
CRUC-6533 Plugin 2 can't access JNDI classes
-
- Closed
-
-
JRASERVER-26290 Plugin2 can't access JNDI when using LDAP credentials.
-
- Gathering Impact
-
Hi,
Thank you for raising this issue. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.
This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).
Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.
We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users.
Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
Thank you,
Bamboo Team