@yusf What are you wanting to see incorporated? The directory sync connector?

That diff that @girish linked is to add experimental support for the upstream Directory Connector APIs to allow you to use the upstream connector.

The directory connector could probably be added as a separate app much like ONLYOFFICE is with Nextcloud.

Alternately, I wrote the original bitwarden_rs_ldap connector, which was supported from within the single install. It was auto configured and then triggered by a timer every 5 min to auto send invites. The reason it wasn't included in the final Cloudron release was because the LDAP connector doesn't in the same way as other Cloudron apps and it was confusing to the users who were testing.

As @girish said, it works by sending users invites. Passwords cannot be synced because the Bitwarden server never even gets to know your password.

It looks like it has been removed, but we could probably patch back in the old LDAP sync at least and make it something that could be configured using file manager or the terminal as an advanced feature.

@yusf the problem with the export from the bitwarden cli is that this would only concern the actual password data, but would not include any of the attachments.

In that sense Bitwarden is only good enough for a whole installation disaster recovery (since Cloudron is doing regular backups, you can restore the setup as it was at a given time). If you want per user backups you could use https://github.com/vwxyzjn/portwarden however (would need the credentials of the given user, but could be used for migrations as well).

@fbartels yep, you're right, I see it listed in the Features Request META issue.

@danigl oh thanks for the heads up, i wonder how we missed the release. I guess since it was over xmas, it somehow got overlooked.

@nebulon said in Why I'm unable to login in my bitwarden ?:

Maybe your Phone is not set to update from network time?

indeed, I just assumed after 6 years that was enabled 🙂
but apparently it wasn't 😳

@girish said in iOS 14.1 can not login, everywhere else works:

@privsec Do you have an app installed on myprivsec.com ? It doesn't look like you have any app installed there? Looks like just the DNS points to the server.

(If it's not clear, when you install an app, leave the location field empty. When you leave the location field empty, it will install the app to myprivsec.com)

Gosh darn it.

Lol.

I did it for a previous issue, and then changed it and then checked the SSL. I will leave this (An app on the bare domain) as the setup currently. Thank you.

@thetomester13 Thanks! Should be fixed now.

@rmdes yes, it works on iOS. Gotta dig in the settings or https://lmgtfy.app/#gsc.tab=0&gsc.q=bitwarden mobile setup

@nebulon Ah yes I see what you mean. Let's hope this does the trick. From the changelog: "Now the initial database connection doesn't fail instantly when there's an error, but retries for up to 15 times by default, adjustable with the DB_CONNECTION_RETRIES option."

sudo dpkg-reconfigure tzdata Current default time zone: 'Etc/UTC' Local time is now: Fri Sep 25 09:36:14 UTC 2020. Universal Time is now: Fri Sep 25 09:36:14 UTC 2020.

It now works with the Bitwarden login but not with Amazon - I also contacted Amazon - apparently they have a problem on their side!

I tried on a new instance here and it works. You may have to report that upstream at the bitwarden_rs project. Hopefully they know how to debug this further.

Yup - that's a sendgrid thing - they do that to help keep spam down, but you may have to pay or something to get the reputation filters up or something?

@d19dotca Indeed.

I have reverted the changes and pushed a new package.

Put the notes at https://cloudron.io/documentation/apps/bitwardenrs/#yubikey