-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Security issue when create agent is called from different user simultaneously #1825
Comments
Awesome thank you so much! |
Hi! @cpacker, I just tried the fix but is not getting the header correctly, it's working when using
|
@Sapessii my understanding of FastAPI code is that alias shouldn't be required in this case since Testing now to see if I can repro (thanks for the report!) |
@cpacker sure no problem :) thanks to you! |
@cpacker working perfectly! thank you so much |
Describe the bug
Hi, when the create agent endpoint is called simultaneously from different users, the user_id is always stick with the first user, hence resulting in multiple users that can access to the chat of others.
I think it's related with the middleware setting the set_current_user function is called.
The text was updated successfully, but these errors were encountered: