Skip to content

Fix: Correct YAML frontmatter syntax in Access Analyzer KBs for search indexing #372

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 20, 2025
Merged

Fix: Correct YAML frontmatter syntax in Access Analyzer KBs for search indexing #372

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...kb/accessanalyzer/500-Internal-Server-Error-Using-Okta-SSO-Published-Reports.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
description: >
description: >-
Users encounter a 500 Internal Server Error when accessing the Netwrix Access Analyzer Published Reports site using Okta Single Sign-On (SSO). The issue occurs because the Okta application uses the SHA1 algorithm, which is not supported by modern .NET Framework and OWIN security libraries.
keywords:
- 500 error
Expand Down
3 changes: 2 additions & 1 deletion docs/kb/accessanalyzer/SEEK-warning-DLPEX-Database-Not-Exist.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
---
description: >-
Explains why the warning 'DLPEX database does not exist' appears during SEEK Bulk Import and how to resolve it by verifying SEEK Scan completion and DLPEX database availability.
title: "SEEK Bulk Import Warning: DLPEX Database Does Not Exist"
sidebar_label: "SEEK Bulk Import Warning: DLPEX Database Does Not Exist"
description: "Explains why the warning 'DLPEX database does not exist' appears during SEEK Bulk Import and how to resolve it by verifying SEEK Scan completion and DLPEX database availability."
keywords:
- SEEK
- DLPEX
Expand Down
Loading