From 414c338d3f39339b799cf4039a351f6c32f1bb46 Mon Sep 17 00:00:00 2001
From: Mark Craig <mark.craig@forgerock.com>
Date: Tue, 24 Jul 2012 08:29:57 +0000
Subject: [PATCH] Review suggestion from Ludovic: Clarify how global account lockout happens in a replication topology
---
opendj-sdk/opendj3/src/main/docbkx/release-notes/chap-issues.xml | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/opendj-sdk/opendj3/src/main/docbkx/release-notes/chap-issues.xml b/opendj-sdk/opendj3/src/main/docbkx/release-notes/chap-issues.xml
index 4fefeb5..d3103ab 100644
--- a/opendj-sdk/opendj3/src/main/docbkx/release-notes/chap-issues.xml
+++ b/opendj-sdk/opendj3/src/main/docbkx/release-notes/chap-issues.xml
@@ -217,7 +217,8 @@
<para>When you configure account lockout as part of password policy,
OpenDJ locks an account after the specified number of consecutive
authentication failures. Account lockout is not transactional across a
- replication topology, however.</para>
+ replication topology, however. Global account lockout occurs as soon as
+ the authentication failure times have been replicated.</para>
</listitem>
<listitem>
<para>OpenDJ is not fully integrated with Microsoft Windows, yet OpenDJ
--
Gitblit v1.10.0