-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃殌 Feature: Turn off Rate-Limiting for user auth in functions #5614
Labels
product / auth
Fixes and upgrades for the Appwrite Auth / Users / Teams services.
product / functions
Fixes and upgrades for the Appwrite Functions.
Comments
Could you please clarify what you're trying to do? 馃 |
stnguyen90
added
product / auth
Fixes and upgrades for the Appwrite Auth / Users / Teams services.
product / functions
Fixes and upgrades for the Appwrite Functions.
labels
Aug 4, 2023
html,body{background-color:#fff;color:#333;line-height:1.4;font-family:sans-serif,Arial,Verdana,Trebuchet MS;}sorry you can delete this issue, when I wrote this I didn't know that you can turn of auth rate limiting in the settings file for dev reasons.
Have a good day!
聽
Steven wrote on 04.08.2023 17:53 (GMT +02:00):
right now you can't use the email user auth in the users api for checking if a user is valid in a appwrite function, because you hit rate limiting very soon.
Could you please clarify what you're trying to do? 馃
鈥擱eply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
product / auth
Fixes and upgrades for the Appwrite Auth / Users / Teams services.
product / functions
Fixes and upgrades for the Appwrite Functions.
馃敄 Feature description
Hi,
right now you can't use the email user auth in the users api for checking if a user is valid in a appwrite function, because you hit rate limiting very soon.
It would be perfect if you can turn off the checking internally for functions. this way you could still stay "safe", and know, that you need your own abuse checking if you use those functions.
Right now it seems like I have to turn off rate limiting in general, which somehow feels bad.
Best,
manolo
馃帳 Pitch
Could be some setting in the api.
馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: