[ 
https://issues.apache.org/jira/browse/PROTON-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roddie Kieley updated PROTON-1655:
----------------------------------
    Description: 
Initially found this issue when testing the OSX work from PROTON-522, however 
after testing it fails in the same way on Fedora 25 when SASL_IMPL is none.

As discussed in [this 
comment|https://issues.apache.org/jira/browse/PROTON-522?focusedCommentId=16218540&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16218540]
 when cyrus is configured for the sasl implementation the test fails due to the 
noted sasl_client_init parameter passing.
{code}
11: Test command: /opt/local/bin/python 
"/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
 "--" 
"GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
 "C
GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
 -I/Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c/include" 
"CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/121/p
roton-c" 
"PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
 "/opt/local/bin/go" "test" "-ldflags" "-r 
/Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c" "-v" "-race" 
"qpid.apach
e.org/..."
.
.
.
11: === RUN   TestAuthPlain
11: --- FAIL: TestAuthPlain (0.02s)
11:     electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access: 
Authentication failed [mech=PLAIN]
{code}

With a sasl implementation of 'none' configured we see that it attempts to use 
mech='none' and also fails:
{code}
11: Test command: /opt/local/bin/python 
"/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
 "--" 
"GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
 "C
GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
 -I/Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c/include" 
"CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/124/p
roton-c" 
"PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
 "/opt/local/bin/go" "test" "-ldflags" "-r 
/Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c" "-v" "-race" 
"qpid.apach
e.org/..."
.
.
.
11: === RUN   TestAuthPlain
11: --- FAIL: TestAuthPlain (0.00s)
11:     electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access: 
Authentication failed [mech=none]
{code}


  was:
As discussed in [this 
comment|https://issues.apache.org/jira/browse/PROTON-522?focusedCommentId=16218540&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16218540]
 when cyrus is configured for the sasl implementation the test fails due to the 
noted sasl_client_init parameter passing.
{code}
11: Test command: /opt/local/bin/python 
"/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
 "--" 
"GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
 "C
GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
 -I/Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c/include" 
"CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/121/p
roton-c" 
"PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
 "/opt/local/bin/go" "test" "-ldflags" "-r 
/Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c" "-v" "-race" 
"qpid.apach
e.org/..."
.
.
.
11: === RUN   TestAuthPlain
11: --- FAIL: TestAuthPlain (0.02s)
11:     electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access: 
Authentication failed [mech=PLAIN]
{code}

With a sasl implementation of 'none' configured we see that it attempts to use 
mech='none' and also fails:
{code}
11: Test command: /opt/local/bin/python 
"/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
 "--" 
"GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
 "C
GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
 -I/Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c/include" 
"CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/124/p
roton-c" 
"PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
 "/opt/local/bin/go" "test" "-ldflags" "-r 
/Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c" "-v" "-race" 
"qpid.apach
e.org/..."
.
.
.
11: === RUN   TestAuthPlain
11: --- FAIL: TestAuthPlain (0.00s)
11:     electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access: 
Authentication failed [mech=none]
{code}



> go-test TestAuthPlain fails when SASL_IMPL is none
> --------------------------------------------------
>
>                 Key: PROTON-1655
>                 URL: https://issues.apache.org/jira/browse/PROTON-1655
>             Project: Qpid Proton
>          Issue Type: Sub-task
>          Components: go-binding
>    Affects Versions: proton-c-0.18.0
>         Environment: OSX 10.11.6, Xcode 7.3.1, golang 1.9.1
> Fedora 25, gcc 6.3.1, go1.7.5
>            Reporter: Roddie Kieley
>            Assignee: Alan Conway
>
> Initially found this issue when testing the OSX work from PROTON-522, however 
> after testing it fails in the same way on Fedora 25 when SASL_IMPL is none.
> As discussed in [this 
> comment|https://issues.apache.org/jira/browse/PROTON-522?focusedCommentId=16218540&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16218540]
>  when cyrus is configured for the sasl implementation the test fails due to 
> the noted sasl_client_init parameter passing.
> {code}
> 11: Test command: /opt/local/bin/python 
> "/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
>  "--" 
> "GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
>  "C
> GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
>  -I/Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c/include" 
> "CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/121/p
> roton-c" 
> "PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
>  "/opt/local/bin/go" "test" "-ldflags" "-r 
> /Users/rkieley/LocalProjects/issues/PROTON-522/121/proton-c" "-v" "-race" 
> "qpid.apach
> e.org/..."
> .
> .
> .
> 11: === RUN   TestAuthPlain
> 11: --- FAIL: TestAuthPlain (0.02s)
> 11:     electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access: 
> Authentication failed [mech=PLAIN]
> {code}
> With a sasl implementation of 'none' configured we see that it attempts to 
> use mech='none' and also fails:
> {code}
> 11: Test command: /opt/local/bin/python 
> "/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/env.py"
>  "--" 
> "GOPATH=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/bindings/go"
>  "C
> GO_CFLAGS=-I/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/proton-c/include
>  -I/Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c/include" 
> "CGO_LDFLAGS=-L/Users/rkieley/LocalProjects/issues/PROTON-522/124/p
> roton-c" 
> "PN_INTEROP_DIR=/Users/rkieley/LocalProjects/issues/PROTON-522/qpid-proton-roddiekieley/tests/interop"
>  "/opt/local/bin/go" "test" "-ldflags" "-r 
> /Users/rkieley/LocalProjects/issues/PROTON-522/124/proton-c" "-v" "-race" 
> "qpid.apach
> e.org/..."
> .
> .
> .
> 11: === RUN   TestAuthPlain
> 11: --- FAIL: TestAuthPlain (0.00s)
> 11:     electron_test.go:39: (from auth_test.go:64) amqp:unauthorized-access: 
> Authentication failed [mech=none]
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to