-
Type:
Suggestion
-
Resolution: Low Engagement
-
Component/s: None
-
0
-
29
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
In extremely rare situations, after a JIRA crash/restart or network/database connectivity problems, the directory configuration seems to be lost. Examples are
- JRA-36677
- JIRA drops LDAP configuration - java.naming.provider.url property does not contain a URL.
- Connection to Crowd Fails due to URI-Reference required
There are two parts to this suggestion:
- JIRA should prevent the database corruption.
- This kind of corruption, being very rare and unexpected, is very difficult to detect manually. During startup/ access, JIRA should verify if mandatory directory parameters exist and inform the administrator if there are parameters missing - so that it is much more easier for administrators to verify and fix the configuration.
- is related to
-
JRASERVER-40291 Jira should not remove directory configuration during sync to avoid the possibilty that the configuration isn't properly written back
-
- Closed
-
-
JRACLOUD-36677
Active directory synchronization lost after restart
-
- Closed
-
-
- Closed