Skip to content

Clarify macOS PFX certificate handling #807

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

Draft
benitoalba wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Clarify macOS PFX certificate handling #807

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
8 changes: 8 additions & 0 deletions docs/getting-started/server/guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -318,6 +318,14 @@ To run your local server environment as a licensed instance, you will need to do
6. Re-run `setup_secrets.ps1` to apply the new values to every server project — see
[Configure user secrets](#configure-user-secrets).

:::note macOS users

The `dev.pfx` file does not need to be imported into Keychain Access. If macOS reports that the
password is invalid while opening or importing the file, leave it out of Keychain and use the
`licenseCertificatePath` and `licenseCertificatePassword` values in `secrets.json` instead.

:::

:::warning

Do not import the "Licensing Certificate - Dev" into your keychain. Doing so may compromise all TLS
Expand Down
11 changes: 11 additions & 0 deletions docs/getting-started/server/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,17 @@ sidebar_position: 10

## macOS

### PFX password rejected by Keychain Access

If Keychain Access reports that the password is invalid when opening a `.pfx` file, first confirm
that the setup instructions actually require importing the file. For example, the
`Licensing Certificate - Dev` should be referenced from `secrets.json`, not imported into Keychain
Access.

When you are generating your own PKCS#12 file and do need to import it into Keychain Access,
regenerate the file with a macOS-compatible PKCS#12 format. For OpenSSL 3, add the `-legacy` option
to the `openssl pkcs12 -export` command, or regenerate the file with OpenSSL 1.1.

### AppleCFErrorCryptographicException

Error:
Expand Down
Loading