summaryrefslogtreecommitdiff
path: root/src/common/resourcemanager.hpp
diff options
context:
space:
mode:
authorThorbjørn Lindeijer <bjorn@lindeijer.nl>2023-05-26 13:03:23 +0200
committerThorbjørn Lindeijer <bjorn@lindeijer.nl>2023-05-26 13:03:26 +0200
commit98dd12a2ccf16d9889b9a97b8ddf6ad64011f9c4 (patch)
treefdfb2f681212ccbb97074baa5f512b9127529046 /src/common/resourcemanager.hpp
parent1f7c7fa192907d90a0ef6bbfbfe770a1e2fffa08 (diff)
downloadmanaserv-master.tar.gz
manaserv-master.tar.bz2
manaserv-master.tar.xz
manaserv-master.zip
Fixed login in case an account gets two pending tokens assignedHEADmaster
Not entirely sure if this is what was happening, but if a PAMSG_LOGIN_RNDTRGR was handled, a new pending account was always created and appended to mPendingAccounts. However, when handling the follow-up PAMSG_LOGIN, only the first pending account with matching username was checked, which could result in a failed login due to mismatching token. Resolved this issue by unifying the client-specific random token with the Stellar token stored on the AccountClient. This means the username value in PAMSG_LOGIN_RNDTRGR could be removed. Eventually it would also be nice to simplify this further such that the token is automatically sent to the client after connecting rather than being something that needs to be requested.
Diffstat (limited to 'src/common/resourcemanager.hpp')
0 files changed, 0 insertions, 0 deletions