-
Suggestion
-
Resolution: Unresolved
-
None
-
None
Bitbucket Data Center and Jira Software use Embedded Crowd and provide an option to use Delegated LDAP User Directory.
However, the advanced settings for this feature are limited and do not allow for setting options such as 'ldap.read.timeout,' 'ldap.search.timelimit,' and 'ldap.connection.timeout,' which are available for other LDAP Connector directory types.
These timeouts can be manually set for Delegated LDAP directories via database inserts, and they are respected by the Delegated LDAP directories as well.
To insert explicit timeouts in the database for the delegating directories:
INSERT INTO public.cwd_directory_attribute (directory_id, attribute_name, attribute_value) VALUES (<directory_id>, 'ldap.connection.timeout', '120000'); INSERT INTO public.cwd_directory_attribute (directory_id, attribute_name, attribute_value) VALUES (<directory_id>, 'ldap.search.timelimit', '60000'); INSERT INTO public.cwd_directory_attribute (directory_id, attribute_name, attribute_value) VALUES (<directory_id>, 'ldap.read.timeout', '10000');
- relates to
-
JRASERVER-76406 LDAP connection issues may cause continuous user authentication failure and lead to an outage on Jira when using an internal user directory with LDAP authentication
- Long Term Backlog
- is cloned by
-
KRAK-5275 Loading...