Failed to add or import users due to Maximum User Limit Reached Error

Overview

The ScaleArc Authentication Offload feature allows ScaleArc to authenticate users internally instead of connecting to the database server for each authentication request. Enabling this feature allows ScaleArc to store user credentials thereby offloading the overhead of establishing new connections for every incoming authentication request resulting in significant performance improvement.

Authentication Offload however has an internal hard limit of a maximum of 1000 users and any attempt to add or import users beyond this limit will result in one of these error messages depending on how the users are being added:

  • Error 2259: Failed to add user. Error Maximum user reached
  • Error 2181: Unable to import users. Maximum user limit reached.

 

Environment

  • Affected Release: 3.10.1.1 and later on All platforms (MySQL & MSSQL)

 

Information

The above error messages indicate that the upper limit for the maximum number of users for Authentication Offload has been reached.

Any attempt to add or import users beyond this limit will result in these errors depending on whether the additional users are added through the Add User button or imported through the Fetch Users functionality.

Error when Add User violates the 1000 users limit:

Error_2259_Failed_to_add_user.png

Error when the Fetch Users functionality violates the 1000 user limit:

Error_2181_Unable_to_import_users.png

 

Solution

The maximum number of users that can be added for Authentication Offloading is 1000 with ScaleArc v3.10.1.1 and later.

The following workarounds are recommended if you have more than 1000 database users:

  1. Delete any unwanted users that are no longer needed to reduce the DB user count to below 1000.
  2. In case the above action is not feasible, the only alternative for ScaleArc to support more than 1000 users is to Turn OFF the Authentication Offload feature such that the database users are authenticated directly through the database server as authentication data is no longer stored in ScaleArc.
Note: If the second workaround is adopted, ScaleArc will lose the performance boost brought about by the Authentication Offloading feature.

Back to top

Comments

0 comments

Please sign in to leave a comment.