Open a-schild opened 5 months ago
Sorry, cannot reproduce.
We don't see any 429 errors in our instance and have successfully migrated some weeks ago.
Are you using the very latest version of ctldap
?
How many users and groups do you have in your instance? Are you using default caching options (defaults to CACHE_LIFETIME_MS=300000
) or have you increased the frequency?
We did migrate back from our own hosted churchtool to ChurchTool.
Since then, the rest api of CT returns a lot of 429 errors (Too many requests) Even with caching enabled we get these errors, and then the logins fail in the LDAP.
Any way to improve handling of this?