You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2011/05/09 14:46:03 UTC

[jira] [Created] (KARAF-626) admin:connect always fails with "Authentication failed"

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


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

[jira] [Commented] (KARAF-626) admin:connect always fails with "Authentication failed"

Posted by "Jamie goodyear (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030983#comment-13030983 ] 

Jamie goodyear commented on KARAF-626:
--------------------------------------

After some investigation it turns out that 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.

On my Mac I just had to ensure I had my Java Home set correctly, then I was able to create and connect to instances without problems.

{code}
$ echo $JAVA_HOME
/Library/Java/Home
{code}

See the following thread for more details.
http://karaf.922171.n3.nabble.com/Strange-behaviour-with-SSH-td1306643.html

> 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

[jira] [Commented] (KARAF-626) admin:connect always fails with "Authentication failed"

Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031143#comment-13031143 ] 

Jean-Baptiste Onofré commented on KARAF-626:
--------------------------------------------

jb@latitude:~/apache-karaf-2.2.0/bin$ echo $JAVA_HOME
/opt/jdk/1.6.0_24
jb@latitude:~/apache-karaf-2.2.0/bin$ ./karaf
[...]
karaf@root> admin:create test
[...]
karaf@root> admin:start test
karaf@root> admin:list
  SSH Port   RMI Port   State       Pid  Name
[    8102] [    1100] [Started ] [22133] test
[    8101] [    1099] [Started ] [22021] root
karaf@root> admin:connect test

It confirms that it works fine defining JAVA_HOME

> 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

[jira] [Resolved] (KARAF-626) admin:connect always fails with "Authentication failed"

Posted by "Jamie goodyear (JIRA)" <ji...@apache.org>.
     [ 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

[jira] [Updated] (KARAF-626) admin:connect always fails with "Authentication failed"

Posted by "Jamie goodyear (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jamie goodyear updated KARAF-626:
---------------------------------

    Attachment: karaf626-error.log

Exceptions seen in log when admin:connect is attempted to instance. This log file is from the child instance.

> 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

[jira] [Issue Comment Edited] (KARAF-626) admin:connect always fails with "Authentication failed"

Posted by "Jamie goodyear (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030983#comment-13030983 ] 

Jamie goodyear edited comment on KARAF-626 at 5/10/11 1:47 AM:
---------------------------------------------------------------

After some investigation it turns out that 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.

On my Mac I just had to ensure I had my Java Home set correctly, then I was able to create and connect to instances without problems.

$ JAVA_HOME=/Library/Java/Home
$ echo $JAVA_HOME
/Library/Java/Home

See the following thread for more details.
http://karaf.922171.n3.nabble.com/Strange-behaviour-with-SSH-td1306643.html

      was (Author: jgoodyear):
    After some investigation it turns out that 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.

On my Mac I just had to ensure I had my Java Home set correctly, then I was able to create and connect to instances without problems.

{code}
$ echo $JAVA_HOME
/Library/Java/Home
{code}

See the following thread for more details.
http://karaf.922171.n3.nabble.com/Strange-behaviour-with-SSH-td1306643.html
  
> 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

[jira] [Commented] (KARAF-626) admin:connect always fails with "Authentication failed"

Posted by "Jamie goodyear (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030977#comment-13030977 ] 

Jamie goodyear commented on KARAF-626:
--------------------------------------

I've reproduced what you have experienced here on Mac, interestingly I can ssh into the instance as per normal just not using the admin:connect method.

> 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
>
>
> 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

[jira] [Closed] (KARAF-626) admin:connect always fails with "Authentication failed"

Posted by "Jamie goodyear (Closed) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jamie goodyear closed KARAF-626.
--------------------------------

    
> 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: karaf-core
>    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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira