 |
 |
KeePassXC (a cross-platform, community-updated fork of KeePass) has a shared entry feature that natively allows credential sharing between users: https://keepassxc.org/docs/KeePassXC_UserGuide.html#_database_sharing_with_keeshare It can also handle time-based one-time passwords generation for 2FA a la Google Authenticator/Authy. However, a reasonable threat model would have one store account credentials in a different database as TOTPs to avoid a single point of failure. Best, Andrew Ward (he/him/his) Digital Services Librarian Troy Public Library On Tue, Oct 12, 2021 at 2:41 PM Bigwood, David <[log in to unmask]> wrote: > We use KeePass on a shared drive. It's free and stores the encrypted > passwords. It doesn't paste them into the login forms or even generate > hard-to-crack passwords. It's free and meets our minimum needs. IT decided > this is what we needed. > > David Bigwood (he,him,his) > [log in to unmask] > Planetary Image Facility, Library > Lunar and Planetary Institute > > > > -----Original Message----- > From: Code for Libraries <[log in to unmask]> On Behalf Of Emily > Lynema > Sent: Monday, October 11, 2021 1:24 PM > To: [log in to unmask] > Subject: [CODE4LIB] Database passwords > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you recognize the sender and know > the content is safe. > ---- Message Below ---- > > I'm curious to survey the community -- has anyone found a way to store > database administration passwords used by technical services staff that is > both user-friendly and secure? For example: the passwords to configure NC > State's various OCLC resources / services / databases. > > Feel free to message me directly if you're not comfortable sharing on-list. > > thanks! > > -- > Emily Lynema > Head, Information Technology > North Carolina State University Libraries > 919-513-8031 > [log in to unmask] >