Managing Login Failure Allowance and User Inactivity Settings in openSIS

Managing Login Failure Allowance and User Inactivity Settings in openSIS

Overview

The Preference settings in openSIS allow administrators to configure basic account security and inactivity controls for users within the institution.

These settings help improve system security by controlling:

  • Failed login attempt limits
  • Automatic account disabling due to inactivity
  • Two-Factor Authentication (2FA) preferences

This article focuses on:

  • Login failure allowance count
  • User inactivity day settings

Accessing Preference Settings

To access the Preference screen:

Notes
Settings > School Settings > Preference

The screen allows administrators to configure:

  • Login failure allowance count
  • User inactivity limits
  • Two-Factor Authentication (2FA) settings

Login Failure Allowance Count

This setting defines how many failed login attempts are allowed before a user account is disabled.

The purpose of this setting is to help protect accounts from:

  • Unauthorized access attempts
  • Brute-force login attacks
  • Repeated invalid credential usage

Configuring Login Failure Allowance Count

To configure the setting:

  1. Navigate to:
    Info
    Settings > School Settings > Preference
  2. Locate:
    Set login failure allowance count
  3. Enter the maximum number of failed login attempts allowed.
  4. Click Update

Example

If the value is set to:
5

Then a user account may be disabled after 5 unsuccessful login attempts.

An administrator may later re-enable the account if required.


Allowable User Inactivity Days

This setting defines the maximum number of inactive days allowed before a user account is disabled automatically.

The inactivity period helps institutions:

  • Maintain account security
  • Reduce unused active accounts
  • Improve access management practices

Configuring User Inactivity Days

To configure inactivity settings:

  1. Navigate to:
    Info
    Settings > School Settings > Preference
  2. Locate:
    Set allowable user inactivity days
  3. Enter the maximum number of inactive days allowed.
  4. Click Update

Example

If the value is set to:
180

Then accounts that remain inactive for more than 180 days may be disabled automatically.


Security Benefits

These settings help institutions:

  • Improve account security
  • Reduce unauthorized access risks
  • Manage dormant accounts
  • Enforce institutional security policies

Best Practices

  • Use reasonable login attempt limits to balance security and usability.
  • Review inactive accounts periodically.
  • Configure inactivity settings according to institutional policies.
  • Enable Two-Factor Authentication (2FA) for additional security.
  • Inform users about account inactivity policies when required.