This is for an internal system that is not public-facing, but does require authentication to separate the end users from service technologists (me). The end user login has a static username and password, but the service user has a static username and updating password that regenerates every day at 00:00. This password is based on known algorithm, and isn’t complex but it doesn’t have to be - it just needs to change so if someone wrote it on a sticky note it won’t work any more after midnight.
Is there any way to store this in my vault so I don’t have to mentally ‘run’ the algorithm?
An example of the password would be Keyword.29! where ‘Keyword’ is one of seven words (one for each of the days of the week), 29 is the day of the month plus the month numerically (27+2 for 27 Feb) and always two digits (so with a leading zero), and with a couple symbols thrown in for good measure.
I am confused about the question, since you can store any old password in Bitwarden. If the question is: is there a way to automatically generate the password and store it in the vault, there is the Bitwarden CLI’s edit command, which happens to have an example in the documentation:
That strategy seems like it would offer less protection than imagined. If I was trying to break in and Keyword.29! did not work, the very first thing I would try is incrementing the number one or more times.
If your management does not feel that an unchanging password is good enough, you might encourage them to look into TOTP instead. Its “changing portion” has the advantage of being non-sequential.
