Details
-
Story
-
Resolution: Fixed
-
Major
-
3.0.0-m7
-
3
-
Core - Sprint 99, Core Team - Sprint 100, Core Sprint 101
Description
Background
NX2 allows for the configuration of the LDAP query cache duration (as per http://books.sonatype.com/nexus-book/reference/ldap-sect-enterprise.html). This is pretty important to control the impact of a busy repo manager onto the LDAP server. The NX3 apparently does have cache support, but lack the ability to control the duration.
Acceptance
- NX3 admins can configure the LDAP query cache duration
- REFINE the definition of this field - what zero or -1 means, for instance
- The 2x-3x upgrade process brings this setting over from NX2
Attachments
Issue Links
- discovered while testing
-
NEXUS-12230 User token is deleted if external server cannot be reached
-
- Closed
-
- is related to
-
NEXUS-12020 LDAP cache entries do not expire properly
-
- Closed
-
-
NEXUS-13483 Re-introduce LDAP user caching
-
- Closed
-
- relates
-
NEXUS-12405 Crowd realm is missing 'Clear Cache' option like the LDAP realm has
-
- Closed
-
- mentioned in
-
Page Loading...