The access to the INETAPP requires a login. The login is done via the Login type set in the configuration. The INETAPP automatically tries to detect the correct authentication service.
In a Windows network, the login is performed against the AD (Active Directory) or the local computer. In a Linux/macOS environment by means of PAM (Pluggable Authentication Modules). If a single sign-on is not possible, a login box for user name and password opens.
In addition, INETAPP Login can be added as a login type. In certain cases a login outside the company network is desired, e.g. in the support of external customers, whose login accounts should not be stored in any internal database. This is an additional way of logging in.
For each of these users, a password must be set in the Users and Groups application, which is stored in encrypted form.
Note: If you enable the INETAPP Login login type, then the User can create own account checkbox will be active by default. Uncheck the box if you do not want users to be able to create their own account in INETAPP.
The order of authentication mechanisms determines the display on the home page and is taken into account when logging in.
Important: The first newly created user after setup gets all permissions in the program. Each additional user has only the permissions of an end-user.
If you still want to force a login box in case of a single sign-on (SSO), i.e. an automatic login takes place, then start the desktop application using the URL with the parameter /?login=true
. This is useful, for example, if you specifically want to log in to INETAPP with a different account. The following is an example of the URL for an INETAPP installation using Windows with IIS:
http://ihr-servername:8002/swingclient/?login=true
Note: By calling the INETAPP server port directly, you bypass MS IIS. This establishes direct communication between the INETAPP desktop application and server, which is a prerequisite for single sign-on. As soon as the port of the INETAPP server cannot be reached directly by the client, e.g. because a firewall only allows ports 80 or 443 and communication takes place via a proxy, a login dialog for authentication always opens.
If the login type INETAPP Login is active, then a login box always opens by default. If you do not want a login and want to force the Windows login (SSO), then use the URL with the parameter /?login=windows
. Below is an example (Jetty web server on port 8002, if port 80 is occupied by MS IIS or Apache):
http://ihr-servername:8002/swingclient/?login=windows
When the INETAPP is accessed via the network, the computer name of the client is passed to the server and displayed in the Computername field in the user's master data. In each case, the computer name of the last access to INETAPP is saved. You can disable overwriting of the Computername field here.