kdbx file yet, I recommend to create one using the Keepass 2 desktop app, and copy it inside the /webdav folder. Header always set Access-Control-Allow-Credentials "true" Header always set Access-Control-Allow-Methods "GET, HEAD, POST, PUT, OPTIONS, MOVE, DELETE, COPY, LOCK, UNLOCK"
Header always set Access-Control-Expose-Headers "ETag" Header always set Access-Control-Allow-Headers "origin, content-type, cache-control, accept, authorization, if-match, destination, overwrite" Header always set Access-Control-Allow-Origin "*" Then a classic location tag to configure WebDav: So we'll keep it outside the following location tags # According to the dev of KeeWeb, OPTIONS request must work without authorization. kdbx database file will be stored in the webdav folder of our website.
#Keeweb config full#
This is my full virtual host configuration file, we assume that the.
Next, we are going to write a Virtual Host for KeeWeb: Then chown -R apache.apache /var/www/html/ Sudo mv /var/www/html/keeweb-gh-pages/* /var/www/html/ & sudo rmdir /var/www/html/keeweb-gh-pages/ You should have a folder /var/www/html/keeweb-gh-pages, let's move its content to the parent folder: Sudo unzip gh-pages.zip -d /var/www/html/ Unzip it at the root of your HTTP server. Next, we have to get the resources of the KeeWeb application:
#Keeweb config mods#
So let's get started by installing Apache httpd.Īpache on CentOS loads automatically the necessary mods that we'll use in our configuration so don't worry about that. I'll be working on CentOS 7 so some commands may vary depending on your operating system. kdbx database hosted on the same server using WebDAV protocol, and finally, we'll protect the access to the website by configuring the Apache LDAP module. We'll deploy KeeWeb on an Apache httpd web server, we'll configure KeeWeb to look for our. It uses browser cache whenever it can, so keep an eye on that when redeploying your application. kdbx database locally on the browser, so security++ ) It's basically written in HTML/CSS and JavaScript, and it's based on KeePass, so you get almost all the features of the KeePass desktop app.
#Keeweb config password#
Sadly, most of the open source web-based password managers that offer self-hosting and LDAP authentication were paid. In addition to that, we needed it to be protected by an LDAP authentication and self-hosted (I personally can't trust any cloud-based password manager). We might need some more functions from nginx, so we would better compile the nginx ourself or pull the official docker image with docker pull nginx.Where I work, we really needed a team password manager that's kept up to date with any password that's been added by a team member. KeeWeb basically save all the information into a single database file which have a suffix. It is compatible with KeePass, which is a very famous. KeeWeb is a web based password managing system.