-
Bug
-
Resolution: Fixed
-
Low
-
4.20.6, 4.20.7, 4.22.2
-
None
-
2
-
Severity 3 - Minor
-
12
-
Issue Summary
When modifying an existing Insight LDAP import and finishing the process (without making any changes to the LDAP password), the system will no longer be able to sync with the LDAP service as the password will no longer be filled out. You will have to edit the LDAP import again to add the password back in.
This issue is happening for all the import configuration which requires password.
This is reproducible on Data Center: Yes
Steps to Reproduce
- Create a working Insight LDAP import configuration and run the import.
- Configure the import and change something which isn't the password (add a description, for example).
- Note that when you reach the "Module fields" section of the configuration, the password appears as dots and greyed out as though the password is still there.
- Complete the configuration.
- Try to run the import.
Expected Results
As the password was not changed, the import should run just fine.
Actual Results
The import fails complaining that "A non blank password is required". You have to go back into the import to update the password as it is now blank and empty.
There does not appear to be any errors in the "insight_import.log" file which indicates an issue when the import config is initially updated and the password is removed.
However, when the import is attempted after the password has been removed, the below is logged in the file:
2022-05-02 10:40:25,383 [https-jsse-nio-49222-exec-10] | Error when importing objects with DefaultImportService, Error: ValidationInsightException: Validation errors were found: password: ErrorMessage{i18nKey='A non blank password is required', parameters=[], additionalMessage=null};
com.riadalabs.jira.plugins.insight.common.exception.ValidationInsightException: ValidationInsightException: Validation errors were found: password: ErrorMessage{i18nKey='A non blank password is required', parameters=[], additionalMessage=null};
at com.riadalabs.jira.plugins.insight.services.imports.common.DefaultImportService.testConnectionWithConfiguration(DefaultImportService.java:367)
at com.riadalabs.jira.plugins.insight.services.imports.common.DefaultImportService.testConnection(DefaultImportService.java:348)
at com.riadalabs.jira.plugins.insight.services.imports.common.DefaultImportService.testConnection(DefaultImportService.java:324)
at com.riadalabs.jira.plugins.insight.services.imports.common.DefaultImportService._startImport(DefaultImportService.java:579)
at com.riadalabs.jira.plugins.insight.services.imports.common.DefaultImportService.startImport(DefaultImportService.java:262)
.....
rest of the traceback is in attached file.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|