tg123/sshpiper

Possible to configure challenger-driver by pipe?

michael-skiles-tfs opened this issue · 7 comments

Hello @tg123!

I know it's possible to configure different upstream drivers when adding a new pipe, and was wondering if challenges and be configured the same way. For example:

/sshpiperd --challenger-driver=azdevcode pipe add ...

Thanks!

tg123 commented

challenger is a global setting for now
i am adding challenger api to grpc upstream, thus, you can have per pipe challenger

tg123 commented

the figure is now doable by introducing v1
need to create a new plugin to do different challenger by pipe

let me know your detailed scenario and I will see how I can help

Damme commented

I would be interested in this, I still use the workingdir router and an extra file for example totp.key with the secret and no or empty file equals no totp for this route.
Similar technique for the other router, being able to specify secret or no totp per route (user), or specify another challenge plugin.

Edit;
Maybe to have a global yaml where we specify the different available plugins and then specify in the router what if any to use.

tg123 commented

@Damme
This is technically doable, but could you please elaborate your scenario or how do you think the config is like
Maybe a customized plugin or something i can make it global

Hello @tg123!

I know it's possible to configure different upstream drivers when adding a new pipe, and was wondering if challenges and be configured the same way. For example:

/sshpiperd --challenger-driver=azdevcode pipe add ...

Thanks!
@michael-skiles-tfs (@tg123)
I have created a plugin that can almost do that, it can skip the challenge or not, depending on your backend, it's a rest plugin so it works with anything: https://github.com/11notes/docker-sshpiper

tg123 commented

Hello @tg123!
I know it's possible to configure different upstream drivers when adding a new pipe, and was wondering if challenges and be configured the same way. For example:
/sshpiperd --challenger-driver=azdevcode pipe add ...
Thanks!
@michael-skiles-tfs (@tg123)
I have created a plugin that can almost do that, it can skip the challenge or not, depending on your backend, it's a rest plugin so it works with anything: https://github.com/11notes/docker-sshpiper

can i link your plugin to readme? or you can send a PR as well

Hello @tg123!
I know it's possible to configure different upstream drivers when adding a new pipe, and was wondering if challenges and be configured the same way. For example:
/sshpiperd --challenger-driver=azdevcode pipe add ...
Thanks!
@michael-skiles-tfs (@tg123)
I have created a plugin that can almost do that, it can skip the challenge or not, depending on your backend, it's a rest plugin so it works with anything: https://github.com/11notes/docker-sshpiper

can i link your plugin to readme? or you can send a PR as well

added PR #159