Add enterprise SSO certificate rollover guard - #525
Open
jaxassistant55 wants to merge 1 commit into
Open
Conversation
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
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.
/claim #19
Summary
enterprise-sso-certificate-rollover-guardmodule for Enterprise ToolingWhy this slice is distinct
This focuses only on institutional SSO signing-certificate rollover readiness before metadata release. It avoids existing #19 work around SCIM deprovisioning, broad identity provisioning drift, webhook payload redaction/delivery, API rate limits, integration contract drift, repository sync SLA, admin dashboards, connector certification, vendor DPA review, data residency, and secret rotation.
Demo artifacts
enterprise-sso-certificate-rollover-guard/reports/demo.mp4enterprise-sso-certificate-rollover-guard/reports/summary.svgenterprise-sso-certificate-rollover-guard/reports/rollover-review-report.mdenterprise-sso-certificate-rollover-guard/reports/rollover-review-packet.jsoncd enterprise-sso-certificate-rollover-guard && npm run demoVerification
Local results:
All tenant names, domains, ticket IDs, and fingerprints are synthetic. No IdP calls, SCIM/HRIS calls, raw certificates, credentials, payment systems, private tenant data, or external APIs are used.
AI-assisted with OpenAI Codex; I reviewed and locally verified the implementation before submission. Attempt registration: #19 (comment)