Fix absolute image path in accessanalyzer KB article

[jake-mahon-netwrix]

Summary

Fixes the remaining build error from PR #346 that was causing CI/CD failure.

Problem

The file docs/kb/accessanalyzer/500-Internal-Server-Error-Using-Okta-SSO-Published-Reports.md
uses an absolute image path which doesn't work in Docusaurus:

![...](/docs/kb/accessanalyzer/images/kA0Qk00000036C9KAI-Okta-settings.png)

This causes the build error:

Error: Image static/docs/kb/accessanalyzer/images/kA0Qk00000036C9KAI-Okta-settings.png not found

Solution

Changed to relative path format:

![...](./images/kA0Qk00000036C9KAI-Okta-settings.png)

Why This Was Missed

This fix was pushed to the PR #346 branch after the PR was already merged, so it didn't make it into dev.

Testing

✅ Image path now uses correct relative format
✅ Follows same pattern as all other KB articles

---

🤖 Generated with Claude Code

Co-Authored-By: Claude [email protected]

[claude]

PR Review - Fix absolute image path in accessanalyzer KB article

Summary

This PR fixes a build error by converting an absolute image path to a relative path in a knowledge base article. The change is correct and follows Docusaurus best practices.

---

✅ Code Quality & Best Practices

Excellent:

• The fix correctly changes from absolute path /docs/kb/accessanalyzer/images/ to relative path ./images/
• This aligns with Docusaurus conventions where image references should use relative paths
• Consistent with the pattern used throughout the codebase (verified 10+ other KB articles using the same ./images/ pattern)
• The PR description is thorough and explains both the problem and the solution clearly

File Changed: docs/kb/accessanalyzer/500-Internal-Server-Error-Using-Okta-SSO-Published-Reports.md:51

---

✅ Correctness & Functionality

Verified:

• ✅ The image file exists at the expected location: docs/kb/accessanalyzer/images/kA0Qk00000036C9KAI-Okta-settings.png
• ✅ The relative path ./images/kA0Qk00000036C9KAI-Okta-settings.png will correctly resolve from the markdown file's location
• ✅ The alt text is descriptive and follows accessibility best practices
• ✅ The fix addresses the exact build error mentioned in the PR description

---

✅ Documentation Standards

The file follows proper documentation conventions:

• Frontmatter: Well-structured with appropriate metadata (keywords, products, sidebar_label, etc.)
• Content Structure: Clear sections (Symptom, Cause, Resolution)
• Markdown Format: Proper headings, code blocks, and notes
• SEO: Good description and keyword coverage

---

🔍 Potential Issues

None identified. This is a straightforward, correct fix.

---

🎯 Recommendations

No changes needed. This PR is ready to merge.

The fix is:

• Minimal and focused
• Correct implementation
• Consistent with repository patterns
• Well-documented in the PR description

---

📊 Impact Assessment

• Risk Level: Minimal
• Scope: Single file, single line change
• Breaking Changes: None
• Build Impact: Fixes existing build failure

---

Summary

LGTM ✅ - This PR correctly fixes the build error and follows all best practices. The change from absolute to relative image paths is the proper solution for Docusaurus, and the implementation is correct.

---

Review conducted by Claude Code