Unlocking finPOWER Connect does not apply User Policy settings for invalid login attempts

If finPOWER Connect has been locked (accessed from Window, Lock finPOWER Connect), then the User has an infinite number of login attempts when attempting to unlock.

This was incorrect, and should have been applying User Policy rules, e.g. lockout after X attempts etc. This has been addressed, and now all applicable User Policy rules are applied when attempting to unlock a locked session, just like when originally logging into the database. The only exception to this is successful logins will not be audited when simply unlocking an existing session (if configured to in the User Policy). The successful logging occurs during the opening of the database, which does not occur if simply unlocking.