Repository navigation
feat: add Direct WSS provisioning - #40
Merged
Merged
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.
Summary
Adds supported provisioning and onboarding for the existing authenticated Direct WSS transport.
imp-direct-wss setup|rotate|statusimp-direct-wsscommand through the server bundleSecurity and architecture
Unchanged:
/ingestand/action-consumerremain unavailable through the gatewayValidation
Independent implementation review: approved after remediation.
Full repository gate passed:
Server-bundle acceptance passed using real relay/gateway processes with simulated systemd.
Focused verifier acceptance passed against disposable local TLS infrastructure.
Live acceptance
Real user-systemd, public-CA TLS, Windows Direct mode, live MUD action delivery, credential rotation, and released-artifact reinstall/upgrade acceptance remain intentionally pending.
Those checks require the released artifact produced after this PR merges. No live VPS, desktop, credential, or public endpoint was modified during the pre-merge acceptance pass.