Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow support for different authentication providers #43

Open
ahitrin opened this issue May 8, 2013 · 0 comments
Open

Allow support for different authentication providers #43

ahitrin opened this issue May 8, 2013 · 0 comments

Comments

@ahitrin
Copy link
Contributor

ahitrin commented May 8, 2013

At the current moment, we have the only one possibility to set password for an account: the configuration file. This is acceptable in corporate environment, where all passwords may be managed by the one person and used by all other persons. But in single user environment this situation may not be useful enough:

  • user may want to store hosts in accounts file, but enter passwords manually
  • user may want to use ssh keys instead of passwords
  • user may use some kind of password manager and may want to use its API to provide passwords

Therefore, SA should allow user to determine how to provide authentication information for each account.

UPD:

Additional use case:

  • in corporate environment, this feature may allow to (partially) split hosts and passwords management. all hosts are stored in one file enabled for all employees, but each password request is being made through external API, which may allow or deny access (and also write access history into the log, like in Logging to the external syslog #33)
@ahitrin ahitrin added this to the 0.9.17 milestone May 16, 2014
ahitrin added a commit that referenced this issue Oct 20, 2014
Seems that MindTerm doesn't support RSA/DSA encrypted keys, but for
paswordless keys everything works fine.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant