Auto Login Feature for RDP Remote Applications
Kron PAM can log in to permitted applications automatically once the credentials are configured in Kron PAM. In these cases, the application’s credentials are invisible to the user whenever they access a device and an application on that device. All sessions are logged by Kron PAM. When a user logs in to a target machine using the auto-login feature, the application will be launched in kiosk mode to restrict access to other resources. In the kiosk mode if an application is minimized users are expected to use the CTRL + M key combination to bring the window back.
- Navigate to Administration > Remote Desktop App.
- Add the name and path of the application to be logged into automatically during an RDP session, and Save.
- As shown in the above figure, we first need to define the application name and path. Then we need to configure the autologin feature. The autologin feature can be configured in three separate ways: a) Optical Character Recognition (OCR), b) Parametric Solution, and c) Application specific Special Automation Scripts
- To categorize the remote apps, you will be able to have a free text area on the Remote Desktop App page and you can add or remove applications from this list. While you are adding the remote app if you type the previously created category, the new app will be added under this category. You can also remove or edit the added applications. After you add the application to the device group you can choose the application as it is.
- When the configuration is done on Allow Remote App page you can see the applications list on the screen as categorized.
- Also you are able to search applications that you are looking for on the screen.
The following functionality is introduced in release 3.0.0. A remote application is defined on Kron PAM and started on a jump server. If the session ends (disconnected for some reason) and a new session is restarted from Kron PAM, a new remote app will not be started. This is because, according to Kron PAM, the same application has already been started (in the disconnected session). However, if a configuration is made on the server side for logging off a disconnected session, a remote app will be started again.