Skip to content

fix(accessanalyzer): correct BYO-cert staging path and filenames to /etc/dspm - #1428

Open
eanandappa99 wants to merge 2 commits into
netwrix:devfrom
eanandappa99:evan/aa-419-tls-cert-path-fix
Open

fix(accessanalyzer): correct BYO-cert staging path and filenames to /etc/dspm#1428
eanandappa99 wants to merge 2 commits into
netwrix:devfrom
eanandappa99:evan/aa-419-tls-cert-path-fix

Conversation

@eanandappa99

Copy link
Copy Markdown
Collaborator

https://netwrix.atlassian.net/browse/AA-419

Summary

Follow-up to #1414 (merged 2026-08-24), which fixed quickinstall.md's BYO-cert directory (/opt/dspm-tls/etc/dspm) but left two things still wrong:

  • quickinstall.md's BYO-cert section still names the files <hostname>.crt/<hostname>.key/ca-bundle.crt. The installer wizard's actual pre-filled defaults (deploy/installer/internal/wizard/wizard.go:201-205 in access-analyzer) are tls.crt/tls.key/ca-bundle.pem. A customer who names files per the doc, then presses Enter to accept the wizard's suggested path, hits a file-not-found validation error.
  • install/system/certificates.md wasn't touched by fix(accessanalyzer): correct install and IDP setup docs to match current installer #1414 — it's still entirely on /opt/dspm-tls/, and its Summary table's CA-bundle prompt label ("AD/DC Root CA Bundle Path") doesn't match the wizard's actual prompt title ("CA Bundle File (optional)").

What changed

  • install/system/certificates.md: path and filenames corrected throughout (Summary table, section headers, code blocks, troubleshooting table); CA-bundle prompt label corrected; dropped a "choose Bring your own certificate" framing the current wizard doesn't offer — it always asks for a cert/key/bundle path, no other provisioning mode.
  • install/quickinstall.md: filenames corrected in the "Bring your own certificate file requirements" table, code blocks, and troubleshooting row; added a one-line note that these are the wizard's pre-filled defaults.

Test plan

  • Vale/Dale checks pass
  • Editorial review
  • Manually verify anchors/links once deployed to preview

Generated with AI

Co-Authored-By: Claude Code ai@netwrix.com

…etc/dspm

The installer wizard's TLS step (deploy/installer/internal/wizard/wizard.go:201-205
in access-analyzer) pre-fills /etc/dspm/tls.crt, /etc/dspm/tls.key, and
/etc/dspm/ca-bundle.pem. Pressing Enter at each prompt accepts those exact
paths, so docs that stage files under different names or /opt/dspm-tls/ send
customers straight into a "file not found" validation failure the moment
they accept the wizard's own suggested default.

- install/system/certificates.md: /opt/dspm-tls/ -> /etc/dspm/, <hostname>.crt/
  .key/ca-bundle.crt -> tls.crt/tls.key/ca-bundle.pem, and the Summary table's
  CA Bundle prompt label corrected to "CA Bundle File (optional)" (was
  "AD/DC Root CA Bundle Path", which isn't the wizard's actual prompt title).
  Also drops a "choose Bring your own certificate" framing the current
  wizard doesn't offer -- it always asks for a cert/key/bundle path.
- install/quickinstall.md: the live "Bring your own certificate file
  requirements" section already used /etc/dspm/ but kept the old
  <hostname>.crt/.key/ca-bundle.crt filenames; corrected to match, and added
  a one-line note that these are the wizard's pre-filled defaults.

AA-419

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
@eanandappa99
eanandappa99 requested a review from a team as a code owner August 25, 2026 17:03
@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the contribution! Tagging codeowners for review: @netwrix/accessanalyzer-docs

Drop "wizard" terminology throughout both files -- the interactive prompt
flow is just referred to as the installer.
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.

1 participant