Skip to content

Documentation of the Common Criteria Flag#1983

Open
kitography wants to merge 1 commit intovault/2.xfrom
feature/vault-42991
Open

Documentation of the Common Criteria Flag#1983
kitography wants to merge 1 commit intovault/2.xfrom
feature/vault-42991

Conversation

@kitography
Copy link
Contributor

This PR adds documentation for the feature flag common_criteria_mode which addresses some of the incompatibilities between the NIAP common criteria requirements and Vault APIs that need to be addressed ahead of getting NIAP certification.

@kitography kitography requested a review from a team as a code owner March 11, 2026 16:14
@github-actions github-actions bot added the Vault Content update for Vault product docs label Mar 11, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Mar 11, 2026

Vercel Previews Deployed

Name Status Preview Updated (UTC)
Dev Portal ✅ Ready (Inspect) Visit Preview Wed Mar 11 16:29:54 UTC 2026
Unified Docs API ✅ Ready (Inspect) Visit Preview Wed Mar 11 16:25:45 UTC 2026

@github-actions
Copy link
Contributor

github-actions bot commented Mar 11, 2026

Broken Link Checker

No broken links found! 🎉


# Common Criteria Flag

The feature flag is "common_criteria_mode", it's set to "true" (the string) in
Copy link
Contributor

Choose a reason for hiding this comment

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

I thought to enable the feature common_criteria_mode was added within the slice of the feature_flags configuration field within vault.hcl?

feature_flags = ["common_criteria_mode"]

| `POST` | `/pki/issuer/:issuer_ref/sign-intermediate/` |
| `POST` | `/pki/sign-verbatim(/:name)` |
| `POST` | `/pki/issuer/:issuer_ref/sign-verbatim(/:name)` |
| `POST` | `/pki/roles/:name` |
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: This API uses not_before_duration not not_before

@@ -0,0 +1,85 @@
---
Copy link
Contributor

Choose a reason for hiding this comment

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

If you're adding new pages, please make sure to also update the nav file in the data folder

@@ -0,0 +1,85 @@
---
layout: api
page_title: Common Criteria Feature Flag
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
page_title: Common Criteria Feature Flag
page_title: Common criteria feature flag

Style correction: use sentence case for titles and headings

necessary but not sufficient to run Vault in a manner compliant with common
criteria.

# Common Criteria Flag
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm very confused about the purpose of this page.

Just to confirm, this is a configuration parameter and an activation flag?

If it's a configuration parameter, why are we documenting how to enable it and the limitations/affects of the configuration setting in the API docs?

Generally speaking, content related to enabling a configuration parameter (and the effect it has on your server) should be in the configuration section. The API docs should focus on the available API endpoints, what they do, and what the request/response objects look like.

From skimming the rest of the PR, it doesn't seem like this is in the right place.

@schavis schavis added the waiting-response Waiting on response from contributor. label Mar 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Vault Content update for Vault product docs waiting-response Waiting on response from contributor.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants