-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
feat(cli): Support using brokered private key in ssh subcommand #2267
Conversation
238f054
to
fef22f0
Compare
@jefferai lets chat about this in the morning, I figured a very structured credential would allow us to control when we consume a credential. This allows us to in the future to have multiple steps that each look for a type of credential and then can decide to use it or not. So results from testing, first using boundary connect both are displayed. Please note I pointed the default target to a test server I use...
Second using the helper
|
And finally if we consume one credential in sshpass
|
No description provided.