Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for certificate based authentication #452

Open
carlo-quinonez opened this issue Oct 17, 2024 · 7 comments
Open

Support for certificate based authentication #452

carlo-quinonez opened this issue Oct 17, 2024 · 7 comments

Comments

@carlo-quinonez
Copy link

I searched and saw some issues and even a PR that were relevant to certificate support, but it wasn't clear what plugin supports this nor how to configure it.

Our company has setup Step CA to enable certificate-based SSH access for service persons supporting customers with the devices we sell.

Does ssh-piper support certificate-based SSH authentication?

@carlo-quinonez carlo-quinonez changed the title Authentication with SSH Certificates Support for certificate based authentication Oct 17, 2024
@tg123
Copy link
Owner

tg123 commented Oct 17, 2024

yes both downstream and upstream

but need a customized plugin to do the ca verification

auth downstream in your case only right?

@tg123
Copy link
Owner

tg123 commented Oct 18, 2024

to verify downstream ca, need new custom plugin
to send ca+cert to upstream, you can check exmaple here https://github.com/tg123/sshpiper/blob/master/plugin/testcaplugin/main.go

@carlo-quinonez
Copy link
Author

Yes, we only need to use certificate authentication of the user that's initiating the ssh connection.

And just want to confirm my understanding...

Downstream means User -> ssh-piper
Upstream meand ssh-piper -> device

@tg123
Copy link
Owner

tg123 commented Oct 18, 2024

correct

may i know which plugin you're using, i can add ca check support

@carlo-quinonez
Copy link
Author

At the moment, we're (re)planning out a solution.

full context

We designed, implemented and tested a solution based on ssh-piper V0, but project lost momentum and we never deployed it to production. The entire solution consisted of ssh-piper and AWS Step Functions to orchestrate transient jump hosts. The lifecycle of the jump host was tied to the lifecycle of the support case.

The solution involved two instances of ssh-piper, one to handle routing connections from our field service engineerings, and the second instance handled routing connections from the devices. We needed two instances of ssh-piper because people and machines needed to authenticate differently...

Now, we've been asked to resurrect the solution AND enhance it to support certificate based authentication and I'm trying to wrap my head around what, if any, changes we need to make to the prior solution.

@carlo-quinonez
Copy link
Author

We were using the old database plugin

@tg123
Copy link
Owner

tg123 commented Oct 21, 2024

i would suggest to take a look at https://github.com/tg123/sshpiper-openpubkey
it integrates with google oauth with magic from open public key

also, CA support will be first added to yaml plugin soon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants