![]() Same goes for my several LDAP backed apps.Bitwarden is a secure open-source password manager that comes with heaps of extra features and a remarkably low price tag. That way, could define a general TOTP for the login item and the second one for the withdraws/desposits URL(s) and still have bitwarden autofill them correctly. When a URL-specific TOTP and an item-wide TOTP are found, then the URL-specific should obviously be preferred if the URL is matching. I think the best way to rework this would be to make it possible to provide multiple TOTP entries item-wide as well as URL-specific. Also, the duplicate password finder would report those entries although they are actually the same account.Ĭreating login items with only TOTP and URL fields filled does not work conveniently - the generated token is not automatically copied to the clipboard since the login credentials were filled from another login item without a TOTP entry. Since the AD credentials are currently used for about 10 apps (wordpress, jitsi, mediawiki, gitlab, netbox and so on), I would rather not create separate login items for every app - updating those would become pretty annoying. I have one login item for my Active Directory account with a URL entry for every app that uses LDAP as auth backend.Ĭurrently it’s only possible to store one TOTP in this password item, although every linked app provides its own 2FA token. This is also relevant when using LDAP/AD with 2FA:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |