Problem Experienced
Jira provides no indication that it saved invalid remote directory configuration or that it read one from the database (for example a configuration that contains no attributes), as seen e.g. in JRASERVER-40291.
This makes it hard to diagnose related problems and their timelines, because:

• Jira caches values related to user directories and re-reads them during startup; if directory configuration has been corrupted, the symptoms will only start occurring after the next restart
• it's impossible to know what execution path has corrupted the configuration

Existing Behavior:

There is no information that Jira read/wrote invalid configuration until Jira is restarted (and starts to throw unclear exceptions then).

Expected Behavior

When Jira reads or writes directory configuration to the database, it should print a warning message when it detects directory with missing (or too few) attributes, along with a stacktrace, to enable further investigation.