We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
System: - OS: Windows 11 10.0.22631 - CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H - Memory: 5.45 GB / 31.73 GB Binaries: - Node: 22.11.0 - C:\Program Files\nodejs\node.EXE - Yarn: 1.22.22 - ~\AppData\Local\pnpm\yarn.CMD - npm: 10.9.0 - C:\Program Files\nodejs\npm.CMD - pnpm: 9.13.2 - C:\Program Files\nodejs\pnpm.CMD
When checking the api key and creating a session it does not work as it compares the unhashed with hashed key.
const apiKeyFromDb = await db.query.apiKeys.findFirst({ where: eq(apiKeys.apiKey, apiKeyHeaderValue), columns: { id: true, apiKey: false, salt: false, }, with: { user: { columns: { id: true, name: true, email: true, emailVerified: true, }, }, }, });
http://localhost:3000/manage/tools/api
No response
The text was updated successfully, but these errors were encountered:
fix: api keys authentication does not work #1511
4ffb40f
fix: api keys authentication does not work #1511 (#1512)
72eda1f
* fix: api keys authentication does not work #1511 * chore: add ip and user-agent to logs of unauthenticated api-keys
Meierschlumpf
Successfully merging a pull request may close this issue.
Provide environment information
System:
- OS: Windows 11 10.0.22631
- CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H
- Memory: 5.45 GB / 31.73 GB
Binaries:
- Node: 22.11.0 - C:\Program Files\nodejs\node.EXE
- Yarn: 1.22.22 - ~\AppData\Local\pnpm\yarn.CMD
- npm: 10.9.0 - C:\Program Files\nodejs\npm.CMD
- pnpm: 9.13.2 - C:\Program Files\nodejs\pnpm.CMD
Describe the bug
When checking the api key and creating a session it does not work as it compares the unhashed with hashed key.
Link to reproduction
http://localhost:3000/manage/tools/api
To reproduce
Additional information
No response
The text was updated successfully, but these errors were encountered: