Position OIDC and Keyring Encrypted File for MySQL/PXC (#214, #215)#220
Draft
brianamarie wants to merge 8 commits into
Draft
Position OIDC and Keyring Encrypted File for MySQL/PXC (#214, #215)#220brianamarie wants to merge 8 commits into
brianamarie wants to merge 8 commits into
Conversation
Contributor
New File Governance CheckNo added markdown files detected. Doc Coverage CheckNo new markdown docs detected. Manual waiver commands (maintainers)
Waiver JSON is stored in a hidden PR comment ( Triggered by |
Contributor
|
{ |
Contributor
Messaging Smart Suggestions
Only auto-apply suggestions at high confidence with reviewer approval. Triggered by |
Collaborator
Author
|
/impact-ok all |
Contributor
|
🤖 Recorded |
Contributor
Messaging Impact Check
licensing-or-open-source-claims (WARN)License and open source positioning changes are cross-cutting. Required review files:
Suggested additional scan:
product-messaging-module-touch (WARN)Product messaging modules often need checks against company framing and shared pillars or offerings. Required review files:
Suggested additional scan:
Manual waiver commands (maintainers):
Waiver state is stored in Triggered by |
Add customer-outcome copy for OpenID Connect Pluggable Authentication in open source builds, plus a MySQL SSO alignment use case in the security pillar. Merge at PS/PXC 8.4.11 / 9.7.2 GA. Co-authored-by: Cursor <cursoragent@cursor.com>
Add customer-outcome copy for encrypted local keyring storage, clarify the external KMS path when policy requires keys outside the database server, and propagate to the security pillar. Merge at PS/PXC 8.4.11 / 9.7.2 GA. Co-authored-by: Cursor <cursoragent@cursor.com>
Fixes prose-and-links Spelling (typos) false positive on HashiCorp Vault. Co-authored-by: Cursor <cursoragent@cursor.com>
brianamarie
force-pushed
the
analysis/issues-214-215
branch
from
June 30, 2026 11:27
30caefb to
d039687
Compare
brianamarie
added
Content & messaging
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.
Summary
Positions two Enterprise-parity security capabilities for Percona Server for MySQL and Percona XtraDB Cluster, tracked in #214 (server-side OpenID Connect authentication) and #215 (Keyring Encrypted File component).
Updates:
products/mysql/messaging.md(Enterprise parity list, Security pillar bullets, sales enablement, Adaptability cross-reference)use-cases-value-pillars/security-sovereignty-compliance.md(audit/key custody proof, MySQL OIDC use case)Copy uses present-tense canonical framing per repo rules. Do not merge to
mainuntil the features GA.Closes #214
Closes #215
Made with Cursor