Skip to content

docs: comment about installing the CA in the system store for macOS #608

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.

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

NickIliev
Copy link
Member

@NickIliev NickIliev requested review from Copilot and a team July 4, 2025 08:22
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds guidance on installing the Fiddler CA certificate into the macOS system store.

  • Introduces a tip explaining how to export and manually install the CA on macOS
  • Clarifies that Fiddler Everywhere will recognize the CA from both user and system stores
Comments suppressed due to low confidence (3)

installation-and-setup/trust-fiddler-ca.md:42

  • Use proper markdown admonition syntax to match existing docs style—for example, prefix with > Tip: (capitalized and with a space after >) rather than >tip.
   >tip To install the Fiddler CA certificate in the system store, you must use the export option and then proceed with manually installing it on macOS. The Fiddler Everywhere application automatically recognizes the installed CA from the user and system stores.

installation-and-setup/trust-fiddler-ca.md:42

  • Insert a blank line before this tip block to visually separate it from the preceding list item for better readability.
   >tip To install the Fiddler CA certificate in the system store, you must use the export option and then proceed with manually installing it on macOS. The Fiddler Everywhere application automatically recognizes the installed CA from the user and system stores.

installation-and-setup/trust-fiddler-ca.md:42

  • [nitpick] Consider shortening the sentence for clarity, e.g., "Export the Fiddler CA certificate and install it manually on macOS. Fiddler Everywhere will then recognize it from the user and system stores."
   >tip To install the Fiddler CA certificate in the system store, you must use the export option and then proceed with manually installing it on macOS. The Fiddler Everywhere application automatically recognizes the installed CA from the user and system stores.

Copy link
Contributor

@lini lini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

keychain should be more recognizable for mac users

@@ -39,6 +39,7 @@ Use the manual approach if the automated wizard fails or you need more control o

1. Go to **Settings** > **HTTPS** in Fiddler Everywhere.
2. Click **Trust Fiddler CA in the User Store**.
>tip To install the Fiddler CA certificate in the system store, you must use the export option and then proceed with manually installing it on macOS. The Fiddler Everywhere application automatically recognizes the installed CA from the user and system stores.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
>tip To install the Fiddler CA certificate in the system store, you must use the export option and then proceed with manually installing it on macOS. The Fiddler Everywhere application automatically recognizes the installed CA from the user and system stores.
>tip To install the Fiddler CA certificate in the system keychain, you must use the export option and then proceed with manually installing it on macOS. The Fiddler Everywhere application automatically recognizes the installed CA from the login and system keychains.

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.

2 participants