Skip to content

Clarify macOS PFX certificate handling#807

Draft
benitoalba wants to merge 1 commit into
bitwarden:mainfrom
benitoalba:macos-pfx-keychain-note
Draft

Clarify macOS PFX certificate handling#807
benitoalba wants to merge 1 commit into
bitwarden:mainfrom
benitoalba:macos-pfx-keychain-note

Conversation

@benitoalba
Copy link
Copy Markdown

Summary

  • Clarifies that the internal dev.pfx licensing certificate should be referenced from secrets.json rather than imported into macOS Keychain Access.
  • Adds a macOS troubleshooting entry for Keychain Access rejecting a PFX password, including the OpenSSL 3 -legacy compatibility option for locally generated PKCS#12 files.

Fixes #178

Checks

  • npx.cmd prettier --check docs/getting-started/server/guide.md docs/getting-started/server/troubleshooting.md
  • npx.cmd cspell lint docs/getting-started/server/guide.md docs/getting-started/server/troubleshooting.md
  • npm.cmd run build

Notes

The full npm.cmd run lint command currently reports existing formatting warnings across many files in this Windows checkout. The two changed files pass targeted Prettier checks.

@bitwarden-bot
Copy link
Copy Markdown

Thank you for your contribution! We've added this to our internal Community PR board for review.
ID: PM-37041
Link: https://bitwarden.atlassian.net/browse/PM-37041

Details on our contribution process can be found here: https://contributing.bitwarden.com/contributing/pull-requests/community-pr-process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Issue in Certificate Generation in MacOS

3 participants