[ 
https://issues.apache.org/jira/browse/KARAF-6058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16746987#comment-16746987
 ] 

Serge Huber commented on KARAF-6058:
------------------------------------

Thanks for all the changes. 

I was wondering if we should provide an example with another user name than 
"karaf" ? Because in my tests it works well with other users and maybe also 
clarify that users don't need to be registered in the users.properties file at 
all because that wasn't clear to me until I looked at the LoginModule code.

Also I was wondering if there was some way we could make the realm registration 
configurable because currently its hardcoded in the bundles but I guess that a 
story for another ticket :)

Regards,
  Serge

> Even key based auth enabled, ssh still prompt for password
> ----------------------------------------------------------
>
>                 Key: KARAF-6058
>                 URL: https://issues.apache.org/jira/browse/KARAF-6058
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf
>    Affects Versions: 4.1.7
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: 4.1.8, 4.2.3
>
>
> It's documented at: 
> http://karaf.apache.org/manual/latest/#_managing_authentication_by_key
> I cannot get it work and wondering if I'm doing something wrong. Steps I did 
> to test the feature:
> {code}
> ssh-keygen -t dsa -f karaf.id_dsa # enter nothing for the passphrase
> {code}
> {code}
> # add a "karaf" entry with the generated public key
> vi apache-karaf-4.1.7/etc/keys.properties
> # start Karaf
> apache-karaf-4.1.7/bin/karaf server
> # try to connect without providing a password
> ssh -p 8101 -i ./karaf.id_dsa karaf@localhost
> Password authentication
> Password:
> {code}
> So it still prompts for a password... the public/private key-pair approach 
> doesn't work in Karaf 4.1.7 :-(
> I tried 4.1.5, 4.1.6, it also does not work. However, same approach works 
> fine in 4.0.10. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to