New OAuth token requred for GTalk whenever BitlBee server updates; this is not documented

[adrianna.pinska@…]

I have observed that whenever the BitlBee server is upgraded my OAuth token for GTalk is invalidated and I am unable to log in:

jabber - Login error: OAuth failure (invalid_grant)

I have to delete the account and re-add it (I don't know if there is a faster way just to request a new token; I haven't been able to find one).

This isn't documented anywhere, which made it frustrating to figure out the first time it happened.

I don't know if this affects other types of accounts.

If there is no existing way to request a new OAuth token without deleting and recreating the account, that should perhaps be a separate bug.

[dx]

ac jabber set password ''

This is suggested in the error message for many kinds of oauth errors, not sure why it's not displayed for this one.

I don't think this has anything to do with "bitlbee server updates", maybe it's just a coincidence.

[wilmer]

During likely login failures when oauth is enabled, I thought it'd normally already include a hint on this?

(with the command actually being ac x set -del password IIRC)

[adrianna.pinska@…]

My bad -- I've had a closer look at my logs, and it looks like there is no correlation with version changes after all. I sometimes get a message that it's my first time using a particular version even if I previously connected to the exact same version (maybe because I connected to a different server?). It occurred to me that this might be related to cycling between servers, but I can't find a clear pattern for that either.

I will try the other suggested workaround the next time this happens.

[dx]

I sometimes get a message that it's my first time using a particular version even if I previously connected to the exact same version (maybe because I connected to a different server?)

So your config isn't getting saved, which means it's probably reusing a very old and already invalid token. Bitlbee only saves on quit, so if your server crashes and you didn't save manually, it will keep loading the old config, repeat the message saying you installed a new version, and try to log in to gtalk with a broken token. To solve this just use the "save" command.

[anonymous]

OK, I think this explains it (and also why my nick format occasionally changed).

I have previously connected to testing.bitlbee.org 99% of the time, but have occasionally cycled to im.bitlbee.org or another server (which no longer seems to be active).

My config isn't being saved on testing.bitlbee.org right now because the server reports that there is no space left on the device, but the token which is currently saved there is valid. I can save my settings on im.bitlbee.org, and the token there is also valid.

Last time the failure happened I was connected to im, which suggests that the previous time I connected to im I got a new token and it wasn't saved (because I seldom disconnect). I can't confirm this 100%, or that previous failures also happened when I switched servers, because I can't access the relevant logs. But this seems like the most plausible explanation.

I have now switched to using only im -- I think I only added other servers because of some temporary outage in the past.

Thanks for your help!

[wilmer]

My config isn't being saved on testing.bitlbee.org right now because the server reports that there is no space left on the device

YIKES! :<

Interesting how that error made it through to you, I thought that error reporting was mostly pretty vague. But ... Clearing up some disk space there now. No clue how this could've happened but ... yeah not much of whitebox monitoring going on there. Maybe I should extend my blackbox monitor to do a register or something like that each time.

[dx]

Interesting how that error made it through to you, I thought that error reporting was mostly pretty vague.

732061027ec0d83db224e81df0fd1b3905a3cdec

wilmer: np wilmer