You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just started testing out Semaphore and it's pretty nice. I used AWX a long time ago and the one basic thing I noticed is missing is the ability for users to load their own SSH Keys, and keep them isolated to their own session. IIRC AWX allowed you to add an SSH key, and while it would be a selection available to any user on a team, you could still place a password on it within AWX (not just a passphrase on for the key, which still needs to be added in the Sempahore project keystore). Unless I'm missing something, it seems like in order to use SSH Keys for your own account, you can only upload them to a project. At that point thought any team members in your project would be able to use them. The only other way to do this is just to have everyone own their own projects, or run everything with a single service account. The first kinda works, but one of the main concepts I like about setups like AWX and Semaphore is the ability for users to create tasks and workflows that can be shared with a team. However if we're all using the same account, auditing and security becomes a little trickier since it all hinges on tracking events within Semaphore. Are there any plans to add individual user key stores so credentials can be isolated to each authorized user, or is there a way to do this that I'm overlooking?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Just started testing out Semaphore and it's pretty nice. I used AWX a long time ago and the one basic thing I noticed is missing is the ability for users to load their own SSH Keys, and keep them isolated to their own session. IIRC AWX allowed you to add an SSH key, and while it would be a selection available to any user on a team, you could still place a password on it within AWX (not just a passphrase on for the key, which still needs to be added in the Sempahore project keystore). Unless I'm missing something, it seems like in order to use SSH Keys for your own account, you can only upload them to a project. At that point thought any team members in your project would be able to use them. The only other way to do this is just to have everyone own their own projects, or run everything with a single service account. The first kinda works, but one of the main concepts I like about setups like AWX and Semaphore is the ability for users to create tasks and workflows that can be shared with a team. However if we're all using the same account, auditing and security becomes a little trickier since it all hinges on tracking events within Semaphore. Are there any plans to add individual user key stores so credentials can be isolated to each authorized user, or is there a way to do this that I'm overlooking?
Beta Was this translation helpful? Give feedback.
All reactions