You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jamie goodyear (JIRA)" <ji...@apache.org> on 2011/05/10 13:44:03 UTC
[jira] [Resolved] (KARAF-626) admin:connect always fails with
"Authentication failed"
[ https://issues.apache.org/jira/browse/KARAF-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear resolved KARAF-626.
----------------------------------
Resolution: Not A Problem
This issue occurs when the JCE libraries are not being included in the classpath.
On some systems, the jars for cryptography are located in ${JAVA_HOME}/jre/lib/endorsed or ${JAVA_HOME}/lib/endorsed.
Setting JAVA_HOME resolves the issue.
> admin:connect always fails with "Authentication failed"
> -------------------------------------------------------
>
> Key: KARAF-626
> URL: https://issues.apache.org/jira/browse/KARAF-626
> Project: Karaf
> Issue Type: Bug
> Components: runtime
> Affects Versions: 2.2.0
> Reporter: Jean-Baptiste Onofré
> Fix For: 2.2.1
>
> Attachments: karaf626-error.log
>
>
> After creating a child instance, it's not possible to connect on this instance using admin:connect command (even supplying the correct username/password):
> karaf@root> admin:connect node2
> Connecting to host localhost on port 8102
> Connected
> Authentication failed
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira