-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
None
-
Affects Version/s: 10.2.2, 10.3.3
-
Component/s: Administration - Secrets Management
-
10.02
-
26
-
Severity 3 - Minor
-
24
-
Warranty
Issue Summary
This is reproducible on Data Center: Yes
Steps to Reproduce
- Install Jira 9.12
- Configure a LDAP directory with a blank username and password, full synchronization completes successfully
- Upgrade to Jira 10.3
Expected Results
LDAP synchronization continues working
Actual Results
LDAP synchronization fails with invalid credentials
The below exception is thrown in the atlassian-jira.log file:
2025-02-24 14:10:44,915-0800 Caesium-1-4 ERROR ServiceRunner [c.a.crowd.directory.DbCachingDirectoryPoller] Error occurred while refreshing the cache for directory [ 10000 ]. com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.AuthenticationException: [LDAP: error code 49 - INVALID_CREDENTIALS: Bind failed: Invalid authentication]; nested exception is javax.naming.AuthenticationException: [LDAP: error code 49 - INVALID_CREDENTIALS: Bind failed: Invalid authentication]
Workaround
- Stop Jira
- Determine directory ID of affected LDAP directory ( select * from cwd_directory )
- Issue following SQL, replacing directory ID with the affected LDAP directory
delete from secret where identifier = 'com.atlassian.jira.secrets.directory_(directory_id)_ldap.password'; update cwd_directory_attribute set attribute_value = '' where attribute_name = 'ldap.password' and directory_id = '(directory_id)';
- Start Jira
- relates to
-
JRASERVER-78872 Upgrading while having -Datlassian.secret.service.state=disabled breaks LDAP
-
- Closed
-