Release Notes Archive

Release Notes v24.03

1. Introduction

This document provides information on the features, improvements, and known issues in this release.
## 2. Changes in this Release

2.1. New Features

• User Hierarchy

2.2. Enhancements

• Table re-design in listing pages.

2.3. Bug Fixes

Nil

3. Issues

3.1. Limitations

1. A new user may need to wait a few minutes after user creation to change the password.
2. SSO supports OpenID Connect (OIDC) 2.0 and SAML 2.0.
3. When a user performs password change, the notification response takes about 10 sec.
4. When a user is associated with multiple devices, then onboarding as well as deleting of the user takes a long time. For a user with 50 associated devices, it approximately takes 8 minutes.
5. SSH to ubuntu 18.04 and higher version fails, need to allow ssh-rsa in the sshd config.
6. Associating 1000 groups to an user will result in user login failure.
7. For SSO with encryption enabled SAML IDP, support is not available.
8. Maximum of 77 devices can be accessed via ThickClient.
9. Advised to create TCP/UDP connections within the subnet with a delay of 5 minutes. This is to allow onboarding of the device to complete on the backend.
10. Associate thick client users only when the group contains minimum 1 TCP/UDP device associated. Do not associate to empty group.
11. Edit of hostname is not allowed for TCP/UDP connection endpoint.

3.2. Known Problems

1. Portal login with external IDP can fail with error "too many redirects". This happens when the user is not logged into the external IDP or the portal url is https://<customer>.remoteaccess.view.com/userprofilepage. Changing the url to https://<customer>.remoteaccess.view.com will login to the portal successfully.
2. Sometimes a user delete can take longer (upto 10 min) to reflect across systems. This issue can be hit when deleting a user and creating a user with the same email id immediately.
3. In the password reset screen, if the old password is set as the new password and a login is attempted immediately sometimes the password reset screen is presented again.
4. In a rare occurence, user logout action gets redirected to userprofile page and not log out.
5. If an existing user is deleted and recreated, then email verification is not triggered.
6. Single Logout (SLO) will not logout the session also at external identity provider.
7. User need to perform logout/login, after changing the password via ThickClient.
8. TCP/UDP device access via ThickClient is not supported after HA switchover/iNode Replacement
9. As a logged in user, when viewing the active sessions will always be empty.
10. US/Pacific-New timezone selection in scheduled access config may not work.
11. Site admin is allowed to delete other sites user_only/device_only/view_only users.

Release Notes v23.09

1. Introduction

This document provides information on the features, improvements, and known issues in this release.
## 2. Changes in this Release

2.1. New Features

• Provision to create/edit group in bulk
• Provision to delete User/Device/Group in bulk
• Provision to enable/disable User in bulk

2.2. Enhancements

• Notification email template change

2.3. Bug Fixes

Nil

3. Issues

3.1. Limitations

1. A new user may need to wait a few minutes after user creation to change the password.
2. SSO supports OpenID Connect (OIDC) 2.0 and SAML 2.0.
3. When a user performs password change, the notification response takes about 10 sec.
4. When a user is associated with multiple devices, then onboarding as well as deleting of the user takes a long time. For a user with 50 associated devices, it approximately takes 8 minutes.
5. SSH to ubuntu 18.04 and higher version fails, need to allow ssh-rsa in the sshd config.
6. Associating 1000 groups to an user will result in user login failure.
7. For SSO with encryption enabled SAML IDP, support is not available.
8. Maximum of 77 devices can be accessed via ThickClient.
9. Advised to create TCP/UDP connections within the subnet with a delay of 5 minutes. This is to allow onboarding of the device to complete on the backend.
10. Associate thick client users only when the group contains minimum 1 TCP/UDP device associated. Do not associate to empty group.
11. Edit of hostname is not allowed for TCP/UDP connection endpoint.

3.2. Known Problems

1. Portal login with external IDP can fail with error "too many redirects". This happens when the user is not logged into the external IDP or the portal url is https://<customer>.remoteaccess.view.com/userprofilepage. Changing the url to https://<customer>.remoteaccess.view.com will login to the portal successfully.
2. Sometimes a user delete can take longer (upto 10 min) to reflect across systems. This issue can be hit when deleting a user and creating a user with the same email id immediately.
3. In the password reset screen, if the old password is set as the new password and a login is attempted immediately sometimes the password reset screen is presented again.
4. In a rare occurence, user logout action gets redirected to userprofile page and not log out.
5. If an existing user is deleted and recreated, then email verification is not triggered.
6. Single Logout (SLO) will not logout the session also at external identity provider.
7. User need to perform logout/login, after changing the password via ThickClient.
8. TCP/UDP device access via ThickClient is not supported after HA switchover/iNode Replacement
9. As a logged in user, when viewing the active sessions will always be empty.
10. US/Pacific-New timezone selection in scheduled access config may not work.

Release Notes v23.08

1. Introduction

This document provides information on the features, improvements, and known issues in this release.

2. Changes in this Release

2.1. New Features

Schedule Based Access
### 2.2. Enhancements
Nil

2.3. Bug Fixes

Nil

3. Issues

3.1. Limitations

A new user may need to wait a few minutes after user creation to change the password.
SSO supports OpenID Connect (OIDC) 2.0 and SAML 2.0.
When a user performs password change, the notification response takes about 10 sec.
When a user is associated with multiple devices, then onboarding as well as deleting of the user takes a long time. For a user with 50 associated devices, it approximately takes 8 minutes.
SSH to ubuntu 18.04 and higher version fails, need to allow ssh-rsa in the sshd config.
Associating 1000 groups to an user will result in user login failure.
For SSO with encryption enabled SAML IDP, support is not available.
Maximum of 77 devices can be accessed via ThickClient.
Advised to create TCP/UDP connections within the subnet with a delay of 5 minutes. This is to allow onboarding of the device to complete on the backend.
Associate thick client users only when the group contains minimum 1 TCP/UDP device associated. Do not associate to empty group.
Edit of hostname is not allowed for TCP/UDP connection endpoint.

3.2. Known Problems

Portal login with external IDP can fail with error "too many redirects". This happens when the user is not logged into the external IDP or the portal url is https://<customer>.remoteaccess.view.com/userprofilepage. Changing the url to https://<customer>.remoteaccess.view.com will login to the portal successfully.
Sometimes a user delete can take longer (upto 10 min) to reflect across systems. This issue can be hit when deleting a user and creating a user with the same email id immediately.
In the password reset screen, if the old password is set as the new password and a login is attempted immediately sometimes the password reset screen is presented again.
In a rare occurence, user logout action gets redirected to userprofile page and not log out.
If an existing user is deleted and recreated, then email verification is not triggered.
Single Logout (SLO) will not logout the session also at external identity provider.
User need to perform logout/login, after changing the password via ThickClient.
TCP/UDP device access via ThickClient is not supported after HA switchover/iNode Replacement
As a logged in user, when viewing the active sessions will always be empty.
US/Pacific-New timezone selection in scheduled access config may not work.

Release Notes v23.06

1. Introduction

This document provides information on the features, improvements, and known issues in this release.

2. Changes in this Release

2.1. New Features

• Support for TCP/UDP device access via ThickClient.
• With Repnet association taken under the hoods, end users can add devices with the native IP of device. The need to translate device IP to Repnet IP is no more needed.
• Support for rolling upgrades. This will ensure future OTA upgrades happen without any portal downtime or maintenance window.

2.2. Enhancements

• Users can filter devices by Site.
• While adding a device, the site (iNode association) is a added as a mandatory field. This association enables to take repnet conversion agnostic to users.

2.3. Bug Fixes

Some of the notable bug fixes:

• Added capability to support HTTP(s) 2.0 device access for Metasys application.

3. Issues

3.1. Limitations

1. A new user may need to wait a few minutes after user creation to change the password.
2. SSO supports OpenID Connect (OIDC) 2.0 and SAML 2.0.
3. When a user performs password change, the notification response takes about 10 sec.
4. When a user is associated with multiple devices, then onboarding as well as deleting of the user takes a long time. For a user with 50 associated devices, it approximately takes 8 minutes.
5. SSH to ubuntu 18.04 and higher version fails, need to allow ssh-rsa in the sshd config.
6. Associating 1000 groups to an user will result in user login failure.
7. For SSO with encryption enabled SAML IDP, support is not available.
8. Maximum of 77 devices can be accessed via ThickClient.
9. Advised to create TCP/UDP connections within the subnet with a delay of 5 minutes. This is to allow onboarding of the device to complete on the backend.
10. Associate thick client users only when the group contains minimum 1 TCP/UDP device associated. Do not associate to empty group.
11. Edit of hostname is not allowed for TCP/UDP connection endpoint.

3.2. Known Problems

1. Portal login with external IDP can fail with error "too many redirects". This happens when the user is not logged into the external IDP or the portal url is https://<customer>.remoteaccess.view.com/userprofilepage. Changing the url to https://<customer>.remoteaccess.view.com will login to the portal successfully.
2. Sometimes a user delete can take longer (upto 10 min) to reflect across systems. This issue can be hit when deleting a user and creating a user with the same email id immediately.
3. In the password reset screen, if the old password is set as the new password and a login is attempted immediately sometimes the password reset screen is presented again.
4. In a rare occurence, user logout action gets redirected to userprofile page and not log out.
5. If an existing user is deleted and recreated, then email verification is not triggered.
6. Single Logout (SLO) will not logout the session also at external identity provider.
7. User need to perform logout/login, after changing the password via ThickClient.
8. TCP/UDP device access via ThickClient is not supported after HA switchover/iNode Replacement
9. As a logged in user, when viewing the active sessions will always be empty.

Release Notes v23.02

1. Introduction

This document provides information on the features, improvements, and known issues in this release.

2. Changes in this Release

2.1. New Features

• Users can choose language keyboard layouts, while connecting RDP device.
• Users can list their current active sessions.
• Admin users can list active sessions of all logged in users at org level.
• SAML 2.0 protocol support for external auth domain.
• Customer domain name is changed to view.com,Default branding is changed from ioTium to View.

2.2. Enhancements

• Users can filter devices by IP address.
• Users can transfer file upto 7.5GB in RDP connection.
• Admin users can change email address of users.

2.3. Bug Fixes

Some of the notable bug fixes:

• File upload screen language will always be in english.
• After applying branding, change takes effect without browser reload.

3. Issues

3.1. Limitations

1. A new user may need to wait a few minutes after user creation to change the password.
2. SSO supports OpenID Connect (OIDC) 2.0 and SAML 2.0.
3. When a user performs password change, the notification response takes about 10 sec.
4. When a user is associated with multiple devices, then onboarding as well as deleting of the user takes a long time. For a user with 50 associated devices, it approximately takes 8 minutes.
5. SSH to ubuntu 18.04 and higher version fails, need to allow ssh-rsa in the sshd config.
6. Associating 1000 groups to an user will result in user login failure.
7. For SSO with encryption enabled SAML IDP, support is not available.

3.2. Known Problems

1. Portal login with external IDP can fail with error "too many redirects". This happens when the user is not logged into the external IDP or the portal url is https://<customer>.remoteaccess.view.com/userprofilepage. Changing the url to https://<customer>.remoteaccess.view.com will login to the portal successfully.
2. Sometimes a user delete can take longer (upto 10 min) to reflect across systems. This issue can be hit when deleting a user and creating a user with the same email id immediately.
3. In the password reset screen, if the old password is set as the new password and a login is attempted immediately sometimes the password reset screen is presented again.
4. In a rare occurence, user logout action gets redirected to userprofile page and not log out.
5. If an existing user is deleted and recreated, then email verification is not triggered.
6. Single Logout (SLO) will not logout the session also at external identity provider.

Release Notes v22.10

1. Introduction

This document provides information on the features, improvements, and known issues in this release.

2. Changes in this Release

2.1. New Features

• Verify email will now get triggered on user creation unlike earlier when it was triggered on user login. Admin users have the ability to resend email verification.
• Ability to export as CSV Device, User, Group, User associated to Group, Endpoints associated to Group, Audit log and Access log is available to the portal admin users.
• Users can integrate password authenticator (external browser plugins like 1password) to login to OTA portal.
• Ability to add content-type rules per connection to potentially fix http(s) device connection failures.
• Admin user can change the org’s password policies and MFA.
• Support for TELNET device type

2.2. Enhancements

• Custom Branding of OTA portal - Customers can now customize their organization’s OTA portal by uploading images.
• Admin user can now filter users on email verification and MFA statuses.
• Configurable page size (25, 50, 100), search on all columns, sort on all columns is now available on all listing pages. Also, goto page number is available.
• Audit log now supports multi-select in type and target columns.
• Multiple User Interface look-and-feel improvements.
• Optimised backend applications for better performance.

2.3. Bug Fixes

Some of the notable bug fixes:

• Disabling a user will immediately auto logout any existing user session.
• Password change via forgot password is not logged in the audit logs.

3. Issues

3.1. Limitations

1. A new user may need to wait a few minutes after user creation to change the password.
2. SSO supports only OpenID Connect (OIDC) 2.0.
3. When a user performs password change, the notification response takes about 10 sec.
4. When a user is associated with multiple devices, then onboarding as well as deleting of the user takes a long time. For a user with 50 associated devices, it approximately takes 8 minutes.
5. SSH to ubuntu 18.04 and higher version fails, need to allow ssh-rsa in the sshd config.
6. Associating 1000 groups to an user will result in user login failure.

3.2. Known Problems

1. File exchange is supported for files with size upto 250 MB. When you try to transfer a file size greater than 250 MB, the transfer may fail. When this happens, you need to logout and login again; otherwise all subsequent file transfers may continue to fail.
2. Portal login with external IDP can fail with error "too many redirects". This happens when the user is not logged into the external IDP or the portal url is https://<customer>.remoteaccess.view.com/userprofilepage. Changing the url to https://<customer>.remoteaccess.view.com will login to the portal successfully.
3. Sometimes a user delete can take longer (upto 10 min) to reflect across systems. This issue can be hit when deleting a user and creating a user with the same email id immediately.
4. In the password reset screen, if the old password is set as the new password and a login is attempted immediately sometimes the password reset screen is presented again.
5. In a rare occurence, user logout action gets redirected to userprofile page and not log out.
6. If an existing user is deleted and recreated, then email verification is not triggered.

Release Notes v22.07

1. Introduction

This document provides information on the features, improvements, and known issues in this release.

2. Changes in this Release

2.1. New Features

• Trouble shooting wizard to trouble shoot, and potentially fix http(s) device connection failures.
• Ability to specify a sub-domain in the Device FQDN for http(s) connections. This facilitate human readable Fully Qualified Domain Names for accessing devices.
• Ability for users to modify the IP Address and Port in the Device configuration settings.
• Support for VNC device type.
• Custom Branding of OTA portal - Customers can now customize their organization’s OTA portal to match their company’s branding standards.
• Infrastructure to put up a Maintenance Site Notice in OTA portal, while performing iNode upgrades.

2.2. Enhancements

• Multiple User Interface look-and-feel improvements.
• Optimised backend applications for better perfromance.

2.3. Bug Fixes

Some of the notable bug fixes:

• HTTPS connection with TLSv1.3 protocol version.
• RDP support for legacy windows like xp and 7.
• Phone number not editable.
• Portal login with external IDP can fail with error "too many redirects". This happens when the user is not logged into the external IDP or the portal url is https://<customer>.remoteaccess.view.com/userprofilepage. Changing the url to https://<customer>.remoteaccess.view.com will login to the portal successfully.

3. Issues

3.1. Limitations

1. A new user may need to wait a few minutes after user creation to change the password.
2. SSO supports only OpenID Connect (OIDC) 2.0.
3. When a user performs password change, the notification response takes about 10 sec.
4. When a user is associated with multiple devices, then onboarding as well as deleting of the user takes a long time. For a user with 50 associated devices it approximately takes 8 minutes.
5. There is no mechanism available for an Admin user to know if a user email is verified or not.
6. SSH to ubuntu 18.04 and higher version fails, need to allow ssh-rsa in the sshd config.
7. Associating 1000 groups to an user will result in user login failure.

3.2. Known Problems

1. File exchange is supported for files with size upto 250 MB. When you try to transfer a file whose size is greater than 250 MB, the transfer may fail. When this happens, you need to logout and login again; otherwise all subsequent file transfers may continue to fail.
2. Portal login with external IDP can fail with error "too many redirects". This happens when the user is not logged into the external IDP or the portal url is https://<customer>.remoteaccess.view.com/userprofilepage. Changing the url to https://<customer>.remoteaccess.view.com will login to the portal successfully.
3. Sometimes a user delete can take longer (upto 10 min) to reflect across systems. This issue can be hit when deleting a user and creating a user with the same email id immediately.
4. In the password reset screen, if the old password is set as the new password and a login is attempted immediately sometimes the password reset screen is presented again.
5. In a rare occurance, user logout action gets redirected to userprofile page and not log out.
6. Password change via forgot password is not logged in the audit logs.

Release Notes v22.02

1. Introduction

This document provides information on the features, improvements, and known issues in this release.

2. Changes in this Release

2.1. New Features

• Save RDP/SSH device login credentials for the connection. This will allow users to login seamlessly to their devices without having to enter the credentials again.
• Allow users to set custom RDP resolution for the RDP device access.
• Access user related pages are mobile/ tablet responsive. This will allow access users to access end devices from their mobile/tablets including ability to use the keyboard.
• Audit trail view is enabled for all the configuration changes done on the OTA portal.
• Ability to associate device and user from group details page.

2.2. Enhancements

• Login using either username or user email to the portal.
• Users can edit the device name.
• Configurable MFA for SSO users.
• To enable easy device addition, autofill of City / State / Country name options made available.

2.3. Bug Fixes

Some of the notable bug fixes:

• Order of devices listing in the user profile is addressed from random to alphabetical order. Search using connection name is enabled in the user profile page.
• Addressed issues related to http device access like Milestone, Powermeter applications.
• Unable to create user with long email / last name is now addressed.

3. Issues

3.1. Limitations

1. A new user may need to wait a few minutes after user creation to change the password.
2. SSO supports only OpenID Connect (OIDC) 2.0.
3. When a user performs password change, the notification response takes about 10 sec.
4. When a user is associated with multiple devices, then onboarding as well as deleting of the user takes a long time. For a user with 50 associated devices it approximately takes 8 minutes.
5. There is no mechanism available for an Admin user to know if a user email is verified or not

3.2. Known Problems

1. File exchange is supported for files with size upto 250 MB. When you try to transfer a file whose size is greater than 250 MB, the transfer may fail. When this happens, you need to logout and login again; otherwise all subsequent file transfers may continue to fail.
2. Portal login with external IDP can fail with error "too many redirects". This happens when the user is not logged into the external IDP or the portal url is https://manage..smartsentry.io/userprofilepage. Changing the url to https://manage..smartsentry.io will login to the portal successfully.
3. Sometimes a user delete can take longer (upto 10 min) to reflect across systems. This issue can be hit when deleting a user and creating a user with the same email id immediately.
4. In the password reset screen, if the old password is set as the new password and a login is attempted immediately sometimes the password reset screen is presented again.
5. Removing phone number associated to an user using the edit user is not removed.

Release Notes v21.07

1. Introduction

This document provides information on the features, improvements, and known issues in this release.

2. Changes in this Release

2.1. New Features

• Email Verification and Password Reset – Starting with this release, users can reset their own passwords in case they have forgotten it.

2.2. Enhancements

• In the search filter the search icon is made bigger, so it is easier to locate.
• Serviceability: During upgrades, a static maintenance page will replace the regular login page, to indicate that the environment is being updated.
• User guide and Release notes documentation is now available in the portal.
• General User Interface look-and-feel improvements.
• Performance: Improved Dashboard page loading.
• Various general serviceability and performance improvements.

2.3. Bug Fixes

Some of the notable bug fixes:

• HTTP and HTTPS device access details are now updated in the audit logs.
• Verified users locked out of accounts because of too many failed password attempts can now reset their passwords using the “Forgot your password?” flow.
• Setting new passwords is inline with the secure password policy.

3. Issues

3.1. Limitations

1. After Muti-factor Authentication (MFA) setup and login, it may take a few minutes before you can edit your user profile information.
2. A new user may need to wait a few minutes after user creation to change the password.
3. SSO supports only OpenID Connect (OIDC) 2.0.
4. When a user performs password change, the notification response takes about 10 sec.
5. When a user is associated with multiple devices, then onboarding as well as deleting of the user takes a long time. For a user with 50 associated devices it approximately takes 8 minutes.
6. There is no mechanism available for an Admin user to know if a user email is verified or not.
7. Password reset via forgot password option can be exercised only using user id (no support to use email id to trigger password resets right now).

3.2. Known Problems

1 .File exchange is supported for files with size upto 250 MB. When you try to transfer a file whose size is greater than 250 MB, the transfer may fail. When this happens, you need to logout and login again; otherwise all subsequent file transfers may continue to fail.
2. Portal login with external IDP can fail with error "too many redirects". This happens when the user is not logged into the external IDP or the portal url is https://<customer>.remoteaccess.view.com/userprofilepage. Changing the url to https://<customer>.remoteaccess.view.com will login to the portal successfully.
3. Sometimes a user delete can take longer (upto 10 min) to reflect across systems. This issue can be hit when deleting a user and creating a user with the same email id immediately.

Release Notes v21.03

1. Introduction

This document provides information on the features, improvements, and known issues in this release.

2. Changes in this Release

2.1. New Features

• Single Sign-on (SSO) with external Identity Provider (IDP) - Login is now integrated with external IDP to support single sign-on functionality.
• HTTP and HTTPS self-onboarding - You can self-onboard remote HTTP and HTTPS devices similar to RDP and SSH devices.

2.2. Enhancements

• Device and user onboarding now have status indicators. Onboarded status indicates the resource is now ready to use.

2.3. Bug Fixes

Some of the notable bug fixes:

• Group details may be removed from the user and device inventory list pages.
• Page loading may be slow in all listing pages

3. Issues

3.1. Limitations

1. After Muti-factor Authentication (MFA) setup and login, it may take a few minutes before you can edit your user profile information.
2. A new user may need to wait a few minutes after user creation to change the password.
3. SSO supports only OpenID Connect (OIDC) 2.0.

3.2. Known Problems

1 User will be locked out for a period (default is 30 minutes) after a certain number of failed login attempts. The error message about wrong credentials is incorrect; in reality you are locked out and need to wait for your account to automatically get unlocked.
2. File exchange is supported for files with size upto 250 MB. When you try to transfer a file whose size is greater than 250 MB, the transfer may fail. When this happens, you need to logout and login again; otherwise all subsequent file transfers may continue to fail.
3. HTTP and HTTPS device access details are not updated in the audit logs.
4. Password change is accepted even if the password does not have at least one number 0-9.