Skip to content

Add PingCastle KB: Scheduler/Agent 401 Unauthorized Error#749

Merged
hilram7 merged 5 commits intodevfrom
add-pingcastle-kb
Apr 14, 2026
Merged

Add PingCastle KB: Scheduler/Agent 401 Unauthorized Error#749
hilram7 merged 5 commits intodevfrom
add-pingcastle-kb

Conversation

@hilram7
Copy link
Copy Markdown
Collaborator

@hilram7 hilram7 commented Apr 14, 2026

Adds a new KB article for PingCastle covering the 401 Unauthorized error returned during scheduler and agent deployment, with supporting images.

Also includes the configuration changes needed to enable KB support for PingCastle:

  • Added PingCastle to kb_allowlist.json and products.js
  • Added _category_.json for the PingCastle KB sidebar
  • Added sidebar_position to all 7 PingCastle 3.5 docs to prevent the KB section from appearing at the top of the sidebar

Tested locally with npm run start and npm run build — no errors.

- Add KB article for scheduler and agent deployment 401 Unauthorized error, with images
- Enable KB support for PingCastle in kb_allowlist.json and products.js
- Add _category_.json for PingCastle KB sidebar
- Add sidebar_position to all 7 PingCastle 3.5 docs to fix KB appearing at top of sidebar
@hilram7 hilram7 requested review from a team as code owners April 14, 2026 00:08
Copy link
Copy Markdown
Collaborator

@JoeDibley JoeDibley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Builds ok and looks ok

@hilram7 hilram7 merged commit ba2da06 into dev Apr 14, 2026
9 checks passed
@hilram7 hilram7 deleted the add-pingcastle-kb branch April 14, 2026 13:30
@github-actions
Copy link
Copy Markdown
Contributor

Documentation PR Review

Editorial Review

docs/pingcastle/3.5/enterpriseinstall.md

No issues found.


docs/pingcastle/3.5/enterpriseupgrade.md

No issues found.


docs/pingcastle/3.5/enterpriseuser.md

  • Clarity — Line 344: Removing "on" from "a click on certain data" produces an ungrammatical phrase: "a click certain data can forward you directly to the page." Suggested fix: "Clicking certain data forwards you directly to the page containing the data used to generate the chart."

  • Clarity — Line 504: Removing "on" from "A click on the domain" and "A click on the entity full name" breaks both clauses: "A click the domain open the domain view and a click the entity full name open the management view for the entity." The verb form ("open" → "opens") was also not corrected. Suggested fix: "Click a domain to open the domain view, or click an entity's full name to open the management view for that entity."

  • Clarity — Line 733: "allows the user to set up all the tool to be able to use it completely" — "tool" should be plural. Suggested fix: "allows the user to set up all the tools to use it completely."

  • Clarity — Line 739 and line 884: "configurate" is a non-standard English word. Suggested fix: change both instances to "configure."

  • Clarity — Line 792: Removing "Please" from "Please pay attention to the next chart" left the sentence starting with a lowercase letter: "pay attention to the next chart." Suggested fix: Capitalize: "Pay attention to the next chart."

  • Clarity — Line 929: "click Create and the fill the information required" contains a spurious "the." Suggested fix: "click Create and fill in the required information."


docs/pingcastle/3.5/index.md

  • Clarity — Line 672: "The following applies:" is vague as a replacement for the original contextual lead-in inside the AV detection note block. A reader scanning the blockquote won't understand why these bullet points are being stated. Suggested fix: "Note the following regarding PingCastle's safety:" or "Keep the following in mind:"

docs/pingcastle/3.5/proinstall.md

  • Clarity — Line 130: The note block contains grammar errors carried from the source: "It MUST starts with HTTPS and MUST ends with /signin-oidc." These were moved into a :::note block but not corrected. Suggested fix: "It MUST start with HTTPS and MUST end with /signin-oidc."

  • Clarity — Line 284–285: Removing "Please" from "Please note the back square at the right of the PingCastlePro website" produced a sentence fragment: "is. not the back square at the right of the PingCastlePro website." This is unreadable. The surrounding paragraph also needs restructuring. Suggested fix: "Sometimes the PingCastlePro site isn't started because the Default Web Site is running. Check the indicator square to the right of the PingCastlePro website to confirm its status."

  • Clarity — Line 295: "ensure you have a certificate installed." starts with a lowercase letter after the original "Make sure you have a certificate installed." was changed. Suggested fix: Capitalize: "Ensure you have a certificate installed."


docs/pingcastle/3.5/proupgrade.md

No issues found.


docs/pingcastle/3.5/prouser.md

  • Clarity — Line 142: "set up all the tool to be able to use it completely" — "tool" should be plural. Suggested fix: "set up all the tools to use it completely."

Summary

9 editorial suggestions across 4 files. 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

19 issues fixed, 10 skipped across 7 files

Category Fixes
FirstPersonPlural (rewrite) 1
Dale: idioms 1
Dale: passive-voice 14
Dale: positional-references 3
Skipped (needs manual review) Reason
docs/pingcastle/3.5/enterpriseinstall.md:77 — Netwrix.FirstPersonPlural 'us' in 'us.contoso.com' is a country-code domain prefix, not first-person plural — false positive
docs/pingcastle/3.5/enterpriseinstall.md:2135 — Netwrix.OxfordComma 'changed, close and reopen' — 'changed' is the end of a conditional clause; 'close and reopen' is a two-verb pair, not a three-item list — false positive
docs/pingcastle/3.5/enterpriseinstall.md:3366 — Netwrix.OxfordComma 'errors, verify and update' — 'For license errors' is a prepositional phrase; 'verify and update' is a two-verb pair, not a three-item list — false positive
docs/pingcastle/3.5/enterpriseuser.md:118 — Netwrix.FirstPerson 'my' appears inside a quoted UI label name ('View my user's claims page') — preserving exact UI label text
docs/pingcastle/3.5/enterpriseuser.md:303 — Netwrix.WeakLinkText 'Click here to get more details' is a button label being described in prose, not hyperlink anchor text — false positive
docs/pingcastle/3.5/proinstall.md:84 — Netwrix.FirstPersonPlural 'us' in 'us.consto.com' is a country-code domain prefix, not first-person plural — false positive
docs/pingcastle/3.5/enterpriseuser.md:21 — Dale: passive-voice Technical security description: 'the application has been designed in a framework where most common attacks... are prohibited by design' — 'prohibited by design' is a standard technical phrase and changing it would reduce clarity
docs/pingcastle/3.5/enterpriseuser.md:44 — Dale: passive-voice Technical security statement: 'all queries to the database are parameterized' — standard security terminology; rewording would reduce precision
docs/pingcastle/3.5/proupgrade.md:21 — Dale: passive-voice 'No data is stored outside of the DB.' — describes a factual state; active rewrite ('the DB stores all data') shifts emphasis and alters meaning slightly
docs/pingcastle/3.5/enterpriseinstall.md:508 — Dale: passive-voice 'This is required for the Task Scheduler...' — describes a system requirement; the sentence structure is clear and a rewrite would not improve readability

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.

3 participants