yumoqing/rbac
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: verify user exists before returning existing apikey in usersync, clean stale downapikey records

Browse Source
This commit is contained in:
yumoqing 2026-05-12 18:13:50 +08:00
parent 09acce0637
commit f1ed6ad151
1 changed files with 78 additions and 63 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
wwwroot/usersync/index.dspy
View File

@ -80,6 +80,13 @@ async with db.sqlorContext(dbname) as sor:
})
if existing:
# 验证用户是否存在
user_check = await sor.R('users', {'id': existing[0].userid})
if not user_check:
# 脏数据：downapikey 存在但用户已删除，清理后重新创建
await sor.D('downapikey', {'id': existing[0].id})
existing = None
else:
apikey = password_decode(existing[0].apikey)
return json.dumps({
'status': 'success',
@ -169,6 +176,13 @@ async with db.sqlorContext(dbname) as sor:
})
if existing:
# 验证用户是否存在
user_check = await sor.R('users', {'id': existing[0].userid})
if not user_check:
# 脏数据，清理后重新创建
await sor.D('downapikey', {'id': existing[0].id})
existing = None
else:
apikey = password_decode(existing[0].apikey)
result_data.append({
'user_id': user_id,
@ -176,6 +190,7 @@ async with db.sqlorContext(dbname) as sor:
'apikey': apikey,
'status': 'existing'
})
continue
else:
# 创建新apikey
apikey_id = getID()