I noticed that Firefox seems to also generate a 401 error, but then the second request generates a log entry with the username. Firefox worked just fine with the standard 'user' and password method. I've tried connecting with domain\user, fqdn.domain\user, \user. Trying to connect with the "Connect to server" option also produces a 401 unauthorized. KeePass is not able to connect using the same credentials, produces 401 unauthorized. In the examples below the KeePassXC will be used instead of vanilla KeePass, but there is no difference in their configuration (the only difference here is that KeePassXC already has the plugin installed).I'm looking to figure out why KeePass2 installed on Ubuntu 12.04 Desktop keeps getting error 401 (Unauthorized) when accessing our password protected WebDAV server (hosted on IIS).įirefox is able to connect using my credentials.
To achieve this – we need in three components – an ssh-client ( ssh, ssh-add, git, etc), the KeePass itself with a KeeAgent plugin, and the ssh-agent which will keep unencrypted files to pass them to clients. One of the possible solutions is to use KeePass, which will store keys and their passwords and will decrypt keys before load them to the ssh-agent. The idea now is to make simpler to work with password-protected SSH keys, to avoid the necessity to enter a password each time when you want to load a key to the ssh-agent.
As a follow-up to the SSH: RSA keys, and ssh-agent for SSH keys and their passwords management post.
0 kommentar(er)
