Make username fall back to file name if not included in metadata #3

New issue

Closed

opened 2021-12-18 14:44:30 +00:00 by Marty · 1 comment

Marty commented

2021-12-18 14:44:30 +00:00

Owner

Currently, every password file needs a username field, even though the pass convention is to carry usernames as filenames.

If a username exists it should take precedence but otherwise the filename should be userd for inputing a username.

Currently, every password file needs a username field, even though the pass convention is to carry usernames as filenames. If a username exists it should take precedence but otherwise the filename should be userd for inputing a username.

Marty added the

bug

label 2021-12-18 14:45:24 +00:00

Marty commented

2021-12-18 14:51:25 +00:00

Author

Owner

also add to readme description of config option:
sets the name of the field in the pass entry which contains the username. Usually, the default setting should be fine (it will look for user, then username, then login) but custom field names can be supplied. If multiple field names are given, it will use the first supplied field name a secret contains.

-> Will always fall back to using filename itself.

also add to readme description of config option: sets the name of the field in the pass entry which contains the username. Usually, the default setting should be fine (it will look for `user`, then `username`, then `login`) but custom field names can be supplied. If multiple field names are given, it will use the first supplied field name a secret contains. -> Will always fall back to using filename itself.

Marty started working 2021-12-18 15:45:03 +00:00

Marty referenced this issue from a commit

2021-12-18 16:16:27 +00:00

Add fallback to entry name if no username field

Marty closed this issue

2021-12-18 16:16:27 +00:00

Marty stopped working 2021-12-18 16:16:27 +00:00

31min 24s