First Pre Release Of Vaultwarden

App
21

On other app instances I find a way to remove them. Am I missing or not seeing the one for vaultwarden in the status window for Vailtwarden page?

22

remove module --no-preserve moduleid1 should remove the app you need from CLI

and no he did not mean removing it altogether, he meant just setting new settings on the App settings page, and saving the details to re-apply them.

The One shown on the app settings page is not the actual, since the actual is encoded by Vaultwarden, we cant know for sure and only vaultwarden Knows the value, unless we save it seprately for your convenience, i think its rather better if its not stored by Us, but you the user stores it somewhere safe.

Don’t you think?

23

@Shadowfire were able to sort it out

24

I have realized that on the first time installation that the admin token that will be set you can’t update change it

25

and it seems not be a Nethserver Issue Alone. @kemboielvis22 Could you retest this case using a new Coolify Deployment of Vaultwarden.

26

Yes, I saved the settings (applied them again). Did not fix it.

As soon as I get back to the office later today I will check it out further.

Thanks for the feedback on this.

27

Okay i will check and investigate further

1 Like
28

Going by these here: GitHub - geniusdynamics/ns8-vaultwarden

A potential Way of Pre-implementing Ldap in VAultwarden

Ldap Configuration for Vaultwarden

Implement a new Service in VAultwaden with
GitHub - ViViDboarder/vaultwarden_ldap: Automate LDAP invites to Vaultwarden which will send an invitation to any member of the group vaultwarden.

Replace dc=example,dc=com with your LLDAP configured domain.

docker-compose.yml to run vaultwarden_ldap

version: '3'
services:
  ldap_sync:
    image: vividboarder/vaultwarden_ldap:0.6-alpine
    volumes:
      - ./config.toml:/config.toml:ro
    environment:
      CONFIG_PATH: /config.toml
      RUST_BACKTRACE: 1
    restart: always

Configuration to use LDAP in config.toml

vaultwarden_url = "http://your_bitwarden_url:port"
vaultwarden_admin_token = "insert_admin_token_vaultwarden"
ldap_host = "insert_ldap_host"
ldap_port = 3890
ldap_bind_dn = "uid=admin,ou=people,dc=example,dc=com"
ldap_bind_password = "insert_admin_pw_ldap"
ldap_search_base_dn = "dc=example,dc=com"
ldap_search_filter = "(&(objectClass=person)(memberOf=uid=vaultwarden,ou=groups,dc=example,dc=com))"
ldap_sync_interval_seconds = 300

Will check every 300 seconds your ldap group vaultwarden and send an invitation by email to any new member of this group.

We could implement a ExecCondition=/bin/sh -c ‘[ -n “$ldap_host” ]’
based on below to start the service only if Ldap was selected… systemd.service

This could Also potentially be another APP, that Does this, which connects to an existing Vaultwarden Instance.

2 Likes
29

the longest running PR, that impelments OIDC for Vaultwarden has now been merged: SSO using OpenID Connect by Timshel · Pull Request #3899 · dani-garcia/vaultwarden

1 Like
30

On the description it states as a document server, but I believe it’s a password manager?

Thanks,

1 Like
31

I guess that is a leftover of copy and paste. Small error.

Please also see the wiki.

1 Like
32

Hi, there is a new Version of vaultwarden yet to be merged, We need help testing the new VErsion:
geniusdynamics/ns8-vaultwarden at dev

Fresh Install

 add-module ghcr.io/geniusdynamics/vaultwarden:dev 1

Test Cases

  1. Test Backup
  2. Test Restore
  3. Verify Admin Keys on UI

** Update to New Version**
Install Previous Version first

add-module ghcr.io/geniusdynamics/vaultwarden:1.0.0 1

Then Update to New Version

api-cli run update-module --data '{"module_url":"ghcr.io/geniusdynamics/vaultwarden:dev","instances":["vaultwarden"],"force":true}'

Test Cases

  1. Update Works, and retains Data
  2. Login to Admin page works

On Separate Note: Vaultwarden Support SSH Authentication KEys

2 Likes