This whole process works fine on Windows machines, domain joined or not. The users connecting need to be a part of the first group. We have a user group that has modify access to the webdav folder, as well as the IIS_IUSRS. 21:22:38 10. GET /webdav/ourpasswordfile.kdbx - 80 domain\user 10. Mozilla/5.0+(X11 +Ubuntu +Linux+x86_64 +rv:26.0)+Gecko/20100101+Firefox/26.0 - 200 0 0 361Īny idea how I can go about getting our Linux friends connected? Am I missing a setting in IIS, or am I missing something else? 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. So you only have to remember one single master key to unlock the whole database.
You can store all your passwords in one database, which is locked with a master key. With KeePass, you can manage your passwords in a secure way. KeePass is not able to connect using the same credentials, produces 401 unauthorized. This app is a desktop password manager compatible with KeePass databases. 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.
0 kommentar(er)
