Is there a count limit for tokens? #1191
Replies: 3 comments 8 replies
-
|
In case you're wondering, it is fully reproducible like that (with a user admin that can open a session on web frontend): |
Beta Was this translation helpful? Give feedback.
-
|
There is no token limit or any kind of rate limiting implemented in LLDAP. The only thing is that we store the active sessions so it grows the DB (there's a cleanup job for outdated tokens), but I doubt you're hitting the limits of the DB Are you maybe getting to LLDAP through a proxy that has rate limiting? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I do, but my example with curl is on local machine (so, without proxy). |
Beta Was this translation helpful? Give feedback.
-
|
Just done it… No luck :/ For the records, I'm using LLDAP with docker with the following |
Beta Was this translation helpful? Give feedback.
-
|
Can you log in through the web frontend? If so, there's probably a typo in your script in the user/domain or something, and it cannot find the user. |
Beta Was this translation helpful? Give feedback.
-
|
I can confirm:
But nobody (even initial admin user) can't use the |
Beta Was this translation helpful? Give feedback.
-
|
Just re-read your initial message: when you use GraphQL, no need to specify a full DN (and, as you found out, you shouldn't!). Just user=username will work |
Beta Was this translation helpful? Give feedback.
-
|
Ohhhhhhh. OMG! Thank you so much ! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello all!
I'm currently working on an cross-integration with Pilos and WHMCS.
I've made many tests with GraphQL and each query/mutation was starting with a call to
auth/login/simpleto get a new fresh token (and, so I was not using refresh token). It is not the final behavior, il plan to cache token and refresh token to do things right but, that was my tests ;)After many tests (so after generating many new tokens) I've experiment a 401 to obtain new token (with same method, always same user, password and admin group).
As nothing has changed in my config, I wonder if I've reached some kind of limit in token generation… Do you think it's the case? If so, do you have some hint to "reset" the token list?
Thank you for your help,
Pierre
Beta Was this translation helpful? Give feedback.
All reactions