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
I couldn't find any discussions on this topic, but it seems like this information should be available somewhere. Am I correct in understanding that enabling OIDC support in SFTPGo settings does not apply this authentication method when connecting to the server via SFTP/FTP protocols using file clients (e.g., FileZilla, WinSCP, etc.)?
In other words, while OIDC works and the user can successfully log in through the WebClient, authorization fails when attempting to connect through file clients.
Isn't the goal of unified authorization to make this process seamless across all access methods? Could you clarify what we might be missing in the configuration?
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
-
Hello,
I couldn't find any discussions on this topic, but it seems like this information should be available somewhere. Am I correct in understanding that enabling OIDC support in SFTPGo settings does not apply this authentication method when connecting to the server via SFTP/FTP protocols using file clients (e.g., FileZilla, WinSCP, etc.)?
In other words, while OIDC works and the user can successfully log in through the WebClient, authorization fails when attempting to connect through file clients.
Isn't the goal of unified authorization to make this process seamless across all access methods? Could you clarify what we might be missing in the configuration?
Beta Was this translation helpful? Give feedback.
All reactions