[GH-ISSUE #758] [FEATURE REQUEST] Allow git repos using ssh #5125

New Issue

GiteaMirror · 2026-04-22T00:23:27-05:00

GiteaMirror commented

2026-04-22 00:23:27 -05:00

Originally created by @ragchuck on GitHub (Aug 22, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/758

I'm normally using SSH keys to authenticate against GitHub and my Forgejo instance.

It would be great if Komodo would also support that.

Originally created by @ragchuck on GitHub (Aug 22, 2025). Original GitHub issue: https://github.com/moghtech/komodo/issues/758 I'm normally using SSH keys to authenticate against GitHub and my Forgejo instance. It would be great if Komodo would also support that.

GiteaMirror added the enhancement label 2026-04-22 00:23:27 -05:00

GiteaMirror commented

2026-04-22 00:23:28 -05:00

@MP-Tool commented on GitHub (Aug 22, 2025):

Hi! Thanks for your suggestion.
Just out of curiosity: is there a particular reason why you prefer using SSH keys over personal access tokens for authentication?
Tokens are generally considered more secure because you can configure their permissions in a very granular way and revoke them easily if needed.
Here’s a link to the official GitHub documentation about personal access tokens and how to manage their scopes:
https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token

Would love to hear about your use case!

@MP-Tool commented on GitHub (Aug 22, 2025): Hi! Thanks for your suggestion. Just out of curiosity: is there a particular reason why you prefer using SSH keys over personal access tokens for authentication? Tokens are generally considered more secure because you can configure their permissions in a very granular way and revoke them easily if needed. Here’s a link to the official GitHub documentation about personal access tokens and how to manage their scopes: https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token Would love to hear about your use case!

GiteaMirror commented

2026-04-22 00:23:29 -05:00

@ragchuck commented on GitHub (Aug 23, 2025):

Maybe it's personal preference, I feel like SSH-Keys are more convenient. I don't have to put them in the origin URL, they just work out of the box by lying in my ~/.ssh directory and I don't have to think about them anymore.
True, PAT can be revoked and are fine granular. But I also feel that SSH keys are one of the most secure things that you can get.

In my use case I currently have a VPS where I work with my user and I have another komodo user setup (using the systemd approach). As of now I work directly on the stacks compose files and env files and I also want komodo to manage the same stacks.
(I'm still having issues with permissions, though...)

Now, we're both working on the same repos on the machine. While I use my ssh key, I want komodo's use their ssh key, using the same origin URL. I'm not 100% sure if that works, but think it should, since both individual users have their own SSH keys.
You could even use a deploy key.

Does this makes sense?

@ragchuck commented on GitHub (Aug 23, 2025): Maybe it's personal preference, I feel like SSH-Keys are more convenient. I don't have to put them in the origin URL, they just work out of the box by lying in my ~/.ssh directory and I don't have to think about them anymore. True, PAT can be revoked and are fine granular. But I also feel that SSH keys are one of the most secure things that you can get. In my use case I currently have a VPS where I work with my user and I have another komodo user setup (using the systemd approach). As of now I work directly on the stacks compose files and env files and I also want komodo to manage the same stacks. (I'm still having issues with permissions, though...) Now, we're both working on the same repos on the machine. While I use my ssh key, I want komodo's use their ssh key, using the same origin URL. I'm not 100% sure if that works, but think it should, since both individual users have their own SSH keys. You could even use a [deploy key](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/managing-deploy-keys#deploy-keys). Does this makes sense?

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/komodo#5125