Repository navigation
Persist SSH authentication preference across profile synchronization - #3
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
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.
Profiles using in-browser SSH approval could alternate between browser-only authentication and an additional SSH key depending on the alias configuration. Editing generated aliases did not survive the next agent synchronization.
Add
warpgatesh profile ssh-auth <name> <auto|in-browser>and persist the choice in the profile through the agent's existing configuration mutation channel. In-browser mode consistently renders keyboard-interactive authentication for every target. Existing profiles retain automatic authentication; token renewal and re-enrollment preserve the preference. This does not change server-side approval duration or scope.Validation: reproduced preference loss with a failing synchronization test before the change; two successive synchronizations, a newly added target, effective OpenSSH settings for short and qualified aliases, token renewal, re-enrollment, legacy profiles and invalid input now pass. All 60 workspace tests, 33 native companion tests, 7 JavaScript tests, frontend build, formatting and Clippy checks pass. CLI and agent builds pass.
A complete application update is required before enabling the preference; the change has not been installed or released. See the getting-started guide for configuration and compatibility details.