Open jag3773 opened 10 years ago
we are already set up to receive an optional username in the request. We could send back a response requesting the password to the account which the server will use to validate then hook everything up. On the app side the user will be presented with a password prompt.
As long as we are in a secure communication channel by this point then that would be great.
of course. This relies on https://github.com/Door43/tS-server/issues/2 and proper implementation within the app
Provide ability in tS-server to associate SSH keys with a door43 account. This will require coordination with tS 2.X.