From 527378d31cd8b95b6648f0b7c5bb5c3b477e34b6 Mon Sep 17 00:00:00 2001 From: jake-mahon Date: Thu, 13 Nov 2025 14:47:16 -0500 Subject: [PATCH] Fix absolute image path in accessanalyzer KB article MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Changed absolute path /docs/kb/accessanalyzer/images/ to relative path ./images/ to resolve build error. Absolute paths don't work for images in Docusaurus (they only work for markdown links). This file was missed in PR #346 because the PR was merged before this fix was pushed. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- ...00-Internal-Server-Error-Using-Okta-SSO-Published-Reports.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/kb/accessanalyzer/500-Internal-Server-Error-Using-Okta-SSO-Published-Reports.md b/docs/kb/accessanalyzer/500-Internal-Server-Error-Using-Okta-SSO-Published-Reports.md index d8d61dd29f..7a03d3e516 100644 --- a/docs/kb/accessanalyzer/500-Internal-Server-Error-Using-Okta-SSO-Published-Reports.md +++ b/docs/kb/accessanalyzer/500-Internal-Server-Error-Using-Okta-SSO-Published-Reports.md @@ -48,7 +48,7 @@ To resolve this issue, update the signature and digest algorithms in the Okta ap 1. In Okta, navigate to the **Application** used for Published Reports. 2. Open the **General Settings** tab. 3. Scroll to the **Signature Algorithm** section. - ![Okta Application Settings page showing the Signature Algorithm section with SHA1 selected](/docs/kb/accessanalyzer/images/kA0Qk00000036C9KAI-Okta-settings.png) + ![Okta Application Settings page showing the Signature Algorithm section with SHA1 selected](./images/kA0Qk00000036C9KAI-Okta-settings.png) 4. Set the following: - **Signature Algorithm**: `RSA_SHA256` - **Digest Algorithm**: `SHA256`