Module: Authentication for the STOCK System¶

Executive summary¶

The module explains a user how to log into the graphical interface (GUI) of STOCK.

In the basic version, the initial licensing policy of STOCK is respected. In practice, it entails that you must have bought a license for the STOCK system. After having bought a license, an implementer has to add a new user to the system. Also, a “competitive use” is enforced: only a single user can be logged in from just a single computer.

The basic method of logging in into STOCK is by using a username and password.

Functional description¶

The module concerning the logging in into the system is ready to be further extended and synchronized with the customer’s authentication infrastructure.

In the basic version, you can log in using the username and password you obtained from the system implementer. A customer is not allowed to add their own users into the system.

In the basic version, user permissions cannot be changed.

Changing username and password¶

The user can – after login – change their username and password using the Settings tab.

Extensions¶

Import data from the customer system using SIDI¶

The login information (login + password) can be exported from the customer’s system. The users will then be imported into the Planning Wizard system.

Login using certificates¶

If your computers use certificates and you use them for login into your internal systems, STOCK is also able to use these certificates for its authentication. The precise settings and implementation of the certificates must be discussed and settled during the implementation phase of STOCK.

User administration using STOCK’s GUI¶

For customers with a large number of users, it may be convenient to use the user administration module. In this module, you can add, edit and remove users via STOCK’s GUI. In this module, you can also change their passwords and change their permission level (if there are different permission levels implemented in the system in the first place).

The administration contains a list of user accounts.

Details settings of an account.

Due to licensing policy of this administration, once a month, there is a recap of active accounts (system and control). The idea is to control whether a user doesn’t use more than prepaid accounts. If so, the user is obliged to pay for the licenses that excess the contract.