it's fixed. because i use ./configure --pfefix=/usr/local/qpid so the sasl's configure file stay in /usr/local/qpid/etc/sasl2, when i copy the configure file into /etc/sasl2, it's work. ------------------ Original ------------------ From: "Steve Huston (via Nabble)"<[email protected]>; Date: 2009年3月17日(星期二) 晚上7:33 To: "doublefox1981"<[email protected]>; Subject: RE: about sasl
> this my c++ client, it's on windows > > Connection connection; > ConnectionSettings Setting; > Setting.host = 192.168.1.233; > Setting.port = 5672; > Setting.username = "uniqueeye"; > Setting.password = "uniqueeye"; > Setting.virtualhost = "/"; > Setting.maxFrameSize = 65535; > Setting.mechanism = "PLAIN"; > connection.open(Setting); > > [r...@localhost qpid]# /usr/sbin/sasldblistusers2 -f > /usr/local/qpid/var/lib/qpidd/qpidd.sasldb > unique...@unique: userPassword > > i'm sure ,the username and password is right. > > should the c++ client to build something else to support sasl? In M4, yes. On trunk, it was broken until late yesterday; I recommend updating to latest and rebuild then try again. -Steve --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@... This email is a reply to your post @ http://n2.nabble.com/about-sasl-tp2485483p2490822.html You can reply by email or by visting the link above. -- View this message in context: http://n2.nabble.com/about-sasl-tp2485483p2495317.html Sent from the Apache Qpid users mailing list archive at Nabble.com.
