![]() This whole process works fine on Windows machines, domain joined or not. The longer the KeePass dev lags behind the runtime and SDK toolchain, the. That would put it in a better position for cross platform and make the code simpler (which is a good thing). The users connecting need to be a part of the first group. The problem with (the first) KeePass IMO today is the unwillingness to migrate to the current developed and supported. ![]() 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. KeePass is not able to connect using the same credentials, produces 401 unauthorized. 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 Comments
Leave a Reply. |