Skip to content

#392964: ccount Policy - Weak Lockout Policy - GroupID Identity Store…#828

Open
bohdan-demediuk-nwx wants to merge 4 commits intodevfrom
feature/login-trotling
Open

#392964: ccount Policy - Weak Lockout Policy - GroupID Identity Store…#828
bohdan-demediuk-nwx wants to merge 4 commits intodevfrom
feature/login-trotling

Conversation

@bohdan-demediuk-nwx
Copy link
Copy Markdown

… doc

@github-actions
Copy link
Copy Markdown
Contributor

Documentation PR Review

Editorial Review

docs/directorymanager/11.1/admincenter/signin.md

  • Structure — Line 108: The heading "Login Throttling" uses "Login" while the rest of the document consistently uses "Sign In" (see the "Sign In" and "Sign Out" section headings). Suggested fix: Rename to "Sign-in Throttling."

  • Clarity — Line 110: "system user accounts" is undefined and potentially misleading — it is not clear what distinguishes these from other account types, and the phrase adds ambiguity before the scope is clarified by the very next sentence. Suggested fix: Remove the phrase and let the second sentence carry the scope: "To protect against brute-force attacks, Directory Manager enforces login throttling based on the originating IP address. This applies when signing in using the Directory Manager provider."

  • Clarity — Lines 112–113: The first two bullets are redundant — the first introduces the 3-attempt threshold as a condition ("before your IP address is locked out"), and the second immediately restates it as a consequence ("After 3 failed attempts, your IP address is blocked"). Suggested fix: Merge into a single bullet: "After 3 consecutive failed sign-in attempts, your IP address is blocked for 5 minutes."

  • Clarity — Line 115: "one additional attempt is granted" is passive voice. Suggested fix: "you get one additional attempt" or "Directory Manager grants you one additional attempt."

  • Completeness — Lines 108–117 (section): The section does not address what an admin can do if a legitimate user's IP address is locked out before the 5-minute window expires — for example, whether a manual unlock is available or whether trusted IP ranges can be excluded. For IT admins, this is a realistic support scenario. Suggested fix: Add a sentence or note clarifying whether an admin override exists (or confirm that none does and the user must wait out the timeout).

Summary

5 editorial suggestions across 1 file. Vale and Dale issues are auto-fixed separately.


What to do next:

Comment @claude on this PR followed by your instructions to get help:

  • @claude fix all issues — fix all editorial issues
  • @claude help improve the flow of this document — get writing assistance
  • @claude explain the voice issues — understand why something was flagged

You can ask Claude anything about the review or about Netwrix writing standards.

Automated fixes are only available for branches in this repository, not forks.

@github-actions
Copy link
Copy Markdown
Contributor

Auto-Fix Summary

14 issues fixed, 0 skipped across 1 files

Category Fixes
Contractions 1
Plurals 1
Substitutions 1
FollowTheStepsTo (rewrite) 1
TypeVsEnter (rewrite) 1
Dale: idioms 1
Dale: passive-voice 5
Dale: positional-references 1
Dale: wordiness 2

Ask @claude on this PR if you'd like an explanation of any fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants