Opened 7 years ago
Closed 7 years ago
#1036 closed enhancement (fixed)
Add support for public/private key authentication
Reported by: | Nicklas Nordborg | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | Open Grid Scheduler service v1.2 |
Component: | net.sf.basedb.opengrid | Keywords: | |
Cc: |
Description
Instead of a username/password, it would be nice to be able to use username/private key to login on a remote server.
Change History (6)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
comment:3 by , 7 years ago
comment:4 by , 7 years ago
comment:5 by , 7 years ago
comment:6 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I got this to work when using PuTTY key files, but there is a problem with OpenSSH files. At first I got an exception:
It is a known issue since #831 that it is not a good idea to register BouncyCastle as a security provider since it will cause problems with class loading.
But after registering BouncyCastle the OpenSSH key also works. Maybe we should start shipping BouncyCastle with the BASE core? That would solve the problem with different extensions having to supply their own versions. Of course, it will still be a problem for anyone running more than one BASE installation in the same Tomcat instance (typically in development environments).