feat(ipa): Add sensitive fields guidance in IPA-111 and OpenAPI markings in IPA-117#77
Draft
AgustinBettati wants to merge 1 commit into
Draft
feat(ipa): Add sensitive fields guidance in IPA-111 and OpenAPI markings in IPA-117#77AgustinBettati wants to merge 1 commit into
AgustinBettati wants to merge 1 commit into
Conversation
…ngs in IPA-117 CLOUDP-412562
AgustinBettati
force-pushed
the
CLOUDP-412562-ipa-111-117-sensitive-fields
branch
from
00bb50c to
c620d81
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Formalizes how secret-carrying fields (passwords, API keys, credentials) are modeled.
****, last-4) must be modeled as a separate read-only redacted sibling property, never sharing the raw field's name.format: passwordon properties whose value is itself a secret; do not use it on redacted sibling properties.Ticket: CLOUDP-412562