Your Setup:
- Tested on Seatable 5.3.12 Enterprise self-hosted
- Not yet possible to verify under 6.0.x
Describe the Problem/Error/Question:
- When the user limit is reached, there are several safeguards in the user interface (Backend / Registration) of Seatable to make sure no additional users are registered beyond the license limit.
- That does not seem to be true when a new user authenticates via LDAP. The user is created and active.
- What is more, the server just crashes because the user limit is exceeded, and does not restart until a user is deactivated via direct database manipulation.
Background: While we still have enough licenses, but we needed a way to block the implicit self-registration of users via LDAP. The idea was to create a number of dummy users (via API) up until the licensed number of users, and deactivate on of them each time we want to admit a new “real“ user.
That plan failed due to seatable’s behaviour. So:
- Can this be considered a bug,
- and / or are there any other ways to achieve our goal to manually assign licenses in a LDAP-based installation?
