How to resolve locked out user

Owned by Kimberly Cruz (Unlicensed)
Last updated: Aug 29, 2023 by Ricky Villa
3 min read

How to resolve locked out user

We have added a couple settings to help with security: 1) The max limit of failed login attempts (default 4 attempts), and 2) Password expiration (default 90 days). If users aren’t aware of these settings, they can find themselves being locked out.

Note By default these are enabled and can be disabled by setting them to 0. These settings are found in the Host → Settings → under the User section.

A few reasons a user can be locked out:

  • It could be that someone whether a colleague or unauthorized user was attempting to access FIN with an incorrect password.

  • It could be that there is a connector using the same username but using an incorrect password and is constantly attempting to connect.

  • It could be that there is an external instance trying to access FIN with the same username and bad password, which again is exceeding the amount of attempts.

Exceeding the max limit of failed login attempts will disable the user. It is best practice to create separate users for connectors and/or external sources so that regular users aren’t locked out. Below are ways on how to resolve this based on FIN on a server and FIN on an F200 device.

FIN on a server

If the user is locked out of a server with access to the directory, below are the options on how to resolve this:

  1. One is to try and login with another superuser if you already have one. You can either disable those new settings or create a new user strictly for the connectors and/or external sources to connect with so that your main user is not locked out. Then you can re-enable the user and assuming nothing else is attempting to login with bad credentials should be good.

  2. The second way is if you don't have another superuser, is to create a backup of the project (stop the FIN service first) and save it outside of the FIN directory. Then re-install FIN and create the users along with a separate user strictly for your connector(s) and/or external sources.

  3. The third way is if you have linked the project(s) to Edge2Cloud. You can use the Edge2Cloud user credentials to log into the project and reset the user. As well as create a separate user for your connector(s) and/or external sources.

  4. Contact J2 Support and provide system integrator and/or distributor contact that installed FIN and is managing the project. As well as sending a copy of the users folder found in the FIN directory. Path should be something like this but with your version: C:\Program Files (x86)\FIN Stack\FIN Stack v5.1.4.191\var\user

FIN on a F200

If the user is locked out on an F200, below are two options on how to resolve this:

  1. First option is if the device is registered to Edge2Cloud, then the cloud user can login and enable and/or create a new user to access the instance locally or tunneling through Horizon. When it comes to F200s, we strongly recommend to register the devices to Edge2Cloud to avoid this issue.

  2. The second option is to do a Reset Configuration in the gateway settings of the device. This will delete the app data such as the project, users and gateway settings. After the device reboots, the user has to reconfigure the gateway network settings and re-install FIN.