I suppose you're talking about connecting through the SSH console, right ? In that case, the answer is no, because it can't be done atm. The SSH layer does not configure any PublicKeyAuthenticator so that you can't rely on SSH key based authentication. I do agree this is something we should do, it's just that I've never had the time to work on it. See KARAF-32, it's an old bug.
Another related thing is captured in KARAF-32, which is the use of agent forwarding to be able to log into another karaf instance using the same credentials. Currently, you have to give them again, even if you're already authenticated, because they are not kept in memory. This would be much better. I guess one possible problem is the use of the local console. The user isn't really authenticated and we have no way to know the password or public key in that case. Not sure how to handle that yet. On Mon, Sep 27, 2010 at 17:21, Charles Moulliard <cmoulli...@gmail.com>wrote: > Hi, > > Do we have an example or a test case showing how to configure karaf to > use certificate + keystore to authenticate admin user instead of > simple login mechanism provided by default ? > > Regards, > > Charles Moulliard > > Senior Solution Architect - Fuse Consultant > > Open Source Integration: http://fusesource.com > Blog : http://cmoulliard.blogspot.com > Twitter : http://twitter.com/cmoulliard > Linkedin : http://www.linkedin.com/in/charlesmoulliard > Skype: cmoulliard > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
