Bug 129714 - authentication failed when log on
Summary: authentication failed when log on
Status: RESOLVED DUPLICATE of bug 128649
Alias: None
Product: kopete
Classification: Unmaintained
Component: Jabber Plugin (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-23 18:46 UTC by Lie_Ex
Modified: 2006-07-26 21:28 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lie_Ex 2006-06-23 18:46:49 UTC
Version:           0.11.3 (using KDE 3.5.3, compiled sources)
Compiler:          Target: i686-pc-linux-gnu
OS:                Linux (i686) release 2.4.22-3Thiz

When I'm trying to login a Jabber account(GoogleTalk),it won't pass the authentication.But I assure that my username and password are both corrent...

In fact,before I change my password from GMail web page,everything was OK.But the trouble happend after my password was changed.Now I have no way to login my GoogleTalk Account by Kopete,but official GoogleTalk works fine.

I had to re-compile kopete with debug mode.The following messages are printed when the Jabber account trying to login.I wish that they will be useful.

------------------------------separate line------------------------

kopete (jabber): [const XMPP::Resource& JabberResourcePool::bestResource(const XMPP::Jid&, bool)] Determining best
resource for lilith.ex@gmail.com
kopete (jabber): [const XMPP::Resource& JabberResourcePool::lockedResource(const XMPP::Jid&)] Current lock for
lilith.ex@gmail.com is 'Kopete'
kopete (jabber): [const XMPP::Resource& JabberResourcePool::bestResource(const XMPP::Jid&, bool)] We have a locked
resource 'Kopete' for lilith.ex@gmail.com
kopete (jabber): [virtual void JabberAccount::connectWithPassword(const QString&)] called
kopete (jabber): [virtual void JabberAccount::connectWithPassword(const QString&)] Determined timezone CST with UTC
offset 8 hours.
kopete (jabber): [virtual void JabberAccount::connectWithPassword(const QString&)] Connecting to Jabber server
talk.google.com:5223
kopete (jabber): [void JabberAccount::setPresence(const XMPP::Status&)] Status: connecting, Reason: 
kopete (jabber): [void JabberResourcePool::addResource(const XMPP::Jid&, const XMPP::Resource&)] Updating existing
resource Kopete for lilith.ex@gmail.com
kopete (jabber): [void JabberBaseContact::reevaluateStatus()] Determining new status for lilith.ex@gmail.com
kopete (jabber): [const XMPP::Resource& JabberResourcePool::bestResource(const XMPP::Jid&, bool)] Determining best
resource for lilith.ex@gmail.com
kopete (jabber): [const XMPP::Resource& JabberResourcePool::lockedResource(const XMPP::Jid&)] Current lock for
lilith.ex@gmail.com is 'Kopete'
kopete (jabber): [const XMPP::Resource& JabberResourcePool::bestResource(const XMPP::Jid&, bool)] We have a locked
resource 'Kopete' for lilith.ex@gmail.com
kopete (jabber): [void JabberBaseContact::reevaluateStatus()] New status for lilith.ex@gmail.com is 正在连接
kopete (jabber): [void JabberResourcePool::lockToResource(const XMPP::Jid&, const XMPP::Resource&)] Locking
lilith.ex@gmail.com to Kopete
kopete (jabber): [void JabberResourcePool::removeLock(const XMPP::Jid&)] Removing resource lock for
lilith.ex@gmail.com
kopete (jabber): [void JabberResourcePool::removeLock(const XMPP::Jid&)] No locks found.
kopete (jabber): [JabberConnector::JabberConnector(QObject*, const char*)] New Jabber connector.
kopete (jabber): [JabberByteStream::JabberByteStream(QObject*, const char*)] Instantiating new Jabber byte stream.
kopete (jabber): [void JabberConnector::setOptSSL(bool)] Setting SSL to true
kopete (jabber): [void JabberConnector::setOptHostPort(const QString&, Q_UINT16)] Manually specifying host
talk.google.com and port 5223
kopete (jabber): [virtual void JabberByteStream::close()] Closing stream.
kopete (jabber): [virtual void JabberConnector::connectToServer(const QString&)] Initiating connection to gmail.com
kopete (jabber): [bool JabberByteStream::connect(QString, QString)] Connecting to talk.google.com, service 5223
kopete (jabber): [void JabberConnector::slotConnected()] We are connected.
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] TLS handshake done,
testing certificate validity...
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] Certificate is not
valid, asking user what to do next.
kopete (jabber): [void JabberAccount::slotHandleTLSWarning(int)] Handling TLS warning...
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML OUT: <?xml
version="1.0"?>
kopete (jabber - raw protocol): 
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML OUT: <stream:stream
xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" to="gmail.com" >
kopete (jabber - raw protocol): 
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML IN: <stream:stream
from="gmail.com" id="X97543E8EE2736652" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client">
kopete (jabber - raw protocol): 
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] Client stream warning.
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML OUT: <iq type="get"
id="auth_1" to="gmail.com" >
<query xmlns="jabber:iq:auth">
<username>lilith.ex</username>
</query>
</iq>
kopete (jabber - raw protocol): 
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML IN: <iq
from="gmail.com" type="result" id="auth_1" >
<query xmlns="jabber:iq:auth">
<username/>
<resource/>
<password/>
</query>
</iq>
kopete (jabber - raw protocol): 
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] Sending auth
credentials...
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML OUT: <iq type="set"
id="auth_2" to="gmail.com" >
<query xmlns="jabber:iq:auth">
<username>lilith.ex</username>
<password>[Filtered]</password>
<resource>Kopete</resource>
</query>
</iq>
kopete (jabber - raw protocol): 
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] XML IN: <iq
from="gmail.com" type="error" id="auth_2" >
<query xmlns="jabber:iq:auth">
<username>lilith.ex</username>
<password/>
<resource>Kopete</resource>
</query>
<error type="auth" code="403" >
<forbidden xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
<text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">username or password not correct</text>
</error>
</iq>
kopete (jabber - raw protocol): 
kopete (jabber): [virtual void JabberByteStream::close()] Closing stream.
kopete (jabber): [void JabberByteStream::slotConnectionClosed()] Socket has been closed.
kopete (jabber): [virtual void JabberByteStream::close()] Closing stream.
kopete (jabber - raw protocol): [void JabberAccount::slotClientDebugMessage(const QString&)] Client stream error.
kopete (jabber): [void JabberAccount::slotCSError(int)] Error in stream signalled.
kopete (jabber): [void JabberAccount::slotCSError(int)] Disconnecting.
Comment 1 Olivier Goffart 2006-06-24 10:54:35 UTC
> <iq from="gmail.com" type="error" id="auth_2" > 
>  <query xmlns="jabber:iq:auth"> 
>  <username>lilith.ex</username> 
>  <password/> 
>  <resource>Kopete</resource> 
>  </query> 
>  <error type="auth" code="403" > 
>  <forbidden xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/> 
>  <text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">username or password not correct</text> 
>  </error> 
>  </iq> 


The password simply seems wrong,  please check it again.
Comment 2 Lie_Ex 2006-06-24 12:52:02 UTC
Well...I've found the solution.

I surmise that Kopete have two place to store Jabber account settings.

Configure Kopete..> Manage Accounts > certain Jabber account
Click the Jabber bulb at the bottom of main UI > Property

When I changed the password from “Manage Accounts” dialog,the password for "Property" is not in-sync(it won't be changed)....Now the Jabber account have two different password settings,but the second one is used when logining.I guess that this is the reason why I failed to pass the authentication.

You should edit your GoogleTalk password in "Property" dialog to take the affect.May be it's a useful solution way.

Is it a bug or original design?

Sorry for my poor English.I can only speak a little...
Comment 3 Olivier Goffart 2006-07-26 21:28:47 UTC

*** This bug has been marked as a duplicate of 128649 ***