nuxsmin / sysPass

Systems Password Manager
https://syspass.org
GNU General Public License v3.0
976 stars 209 forks source link

[Feature Request] different account types #821

Open traskat opened 6 years ago

traskat commented 6 years ago

hey,

maybe it would be nice to have different account type to choose when creating new ones. for example an account type for storing ssh key or only pins and so on.

thanks

vmario89 commented 6 years ago

this is a good idea, but i think this should be implemented not as different account types. I would prefer to have a common container - "the account" - which contains different data. It could contain special fields for this case or similar cases.

Imagine you have a user and a password an a system. This user could be used for many different things like logging on the system be protocol FTP, SSH, WinSCP, ... . For each of these protocols there could be a special "protocol" field which defines an action shortcut/protocol url. Could also be a teamspeak shortcut as handy example (ts3server://) or TOTP url (otpauth://). There are many different things what could be done from a password manager itself. You could use some custom fields for storing this data at first. Maybe later some execution actions could be done with this data from sysPass or special remote plugins...

its also possible to write a linux/windows client for the user system. So the user could receive field action data by provided API to run something on his local system by getting the credentials and the "what to do with it".

Please refer to some commercial systems and what they give as types for example:

https://www.manageengine.com/products/passwordmanagerpro/help/managing_resource_types.html

http://help.passwordsafe.de/v8/1/en/topic/anwendungen

dvdfabian commented 6 years ago

I think that tying the existing custom fields to categories would suffice. Imagine a category for SSH, web account or a LUKS password. Each can have a different set of (required) fields associated with them. Account categories could turn into something like account templates. Also, a user access field should not be mandatory, some accounts don't need it (disk encryption).

Best regards,

David Fabian