Skip to content

Conversation

rmartinoscar
Copy link
Member

image
I have no idea how to let the user know that password auth is disabled within the SFTP client.

@rmartinoscar rmartinoscar self-assigned this Jul 3, 2025
@rmartinoscar rmartinoscar requested a review from a team as a code owner July 3, 2025 19:10
@notAreYouScared
Copy link
Member

I dont think you can, maybe push a notification to the panel. Like a. Sftp Authentication failed, only ssh Authentication is allowed?

@Lovinoes
Copy link

Lovinoes commented Jul 3, 2025

maybe something like "Password authentication failed. SSH key required by server."? or "Password authentication failed. This server only accepts SSH keys."

@rmartinoscar
Copy link
Member Author

maybe something like "Password authentication failed. SSH key required by server."? or "Password authentication failed. This server only accepts SSH keys."

I was saying i have no clue how to do that not which message should i output.
I thought i'd replace the Settings text to be like Password authentication is disabled you may browse SSH Keys and then add a button taking you to EditProfile/?tab=-ssh-keys-tab

// If set to true, no write actions will be allowed on the SFTP server.
ReadOnly bool `default:"false" yaml:"read_only"`
// If set to true users won't be able to login using their password.
KeyOnly bool `default:"false" yaml:"key_only"`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we not in some way sync this from the panel?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since read_only worked this way i thought about making the panel sync config when changing the setting there not making a request once wings start but that could be better

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

Successfully merging this pull request may close these issues.

4 participants