The following is a list of recent changes and improvements made to i2Pass. Most changes are made as the direct result of a customer request. If you have changes you would like to see made to i2Pass, send E-mail to us and we'll add your change to our list of possible implementations.
Register your E-mail address to receive automatic notification whenever there are changes to i2Pass.
Index:
i2Pass Updates:
Release 3:
Release 4 of i2Pass adds support for mobile authenticator applications. Support for DUO is available for this release with other applications to be added soon. This feature requires a kConnect license. V4.0 also includes an implementation of Kisco's Bluescape native web UI.
Release 4 is available for free to all i2Pass customers who are current on annual maintenance support. Contact Kisco Systems for upgrade instructions.
Release 3:
Release 3 of i2Pass adds a self-activation feature as part of the user registration. When enrolling new users, the administrator no longer needs to know every email address. If a user is registered with the email address set to *NONE, then the first time they sign on after registration to i2Pass, they will be prompted for the email address (or addresses) that they want to use and complete a validation process.
Also new for Release 3, the specific email addresses are now split up into three different fields. This eliminates the previously confusing method of stacking multiple email addresses in a single field.
Release 3 is available for all current customers who are current on annual maintenance support. Contact Kisco Information Systems for upgrade instructions.
Release 2:
Release 2 of i2Pass adds optional IP address controls for 5250 terminal sessions. You can limit access for a specific user profile to a single IP address or a range of addresses. Release 2 also captures the source IP address for each terminal session and shows it in the i2Pass activity log.
Release 2 is available for all current customers who are current on annual maintenance support. Contact Kisco Information Systems for upgrade instructions.
Release 1:
Update for Initial Program settings added.
When i2Pass is activated for a user profile and that user profile has an initial program associated with it, the initial program setting is saved and stored in i2Pass. This update provides the customer with the capability of making changes to, or removing, the initial program setting for a user without having to remove them from i2Pass.
This update is available as a PTF. This PTF can only be installed on a Release 1.14 version of i2Pass. The correction is available in PTF package IEPTF115. E-mail us and request the PTF package.
New application security model adopted.
When i2Pass was first made available, only security officer profiles, either *SECOFR or *SECADM, could administer the software. With the change announced here, other user profiles with lesser security in their profiles can be granted access to administer i2Pass. A list of authorized users has been established. Only users with *SECOFR or *SECADM can make changes to the authorized list of users.
This update is available as a PTF. This PTF can only be installed on a Release 1.13 version of i2Pass. The correction is available in PTF package IEPTF114. E-mail us and request the PTF package.
Notification subject text now variable.
Prior to this change, all alert notifications issued by i2Pass had the same subject identification on them. Now, with this change, you can customize the subject text. For customers running i2Pass on multiple partitions or on different IBM i systems, this lets you identify which system is issuing the alert.
This update is available as a PTF. This PTF can only be installed on a Release 1.10 version of i2Pass. The correction is available in PTF package IEPTF111. E-mail us and request the PTF package.
Option added to encrypt stored 2FA codes in i2Pass.
For customers looking for maximum security, an option has been added to i2Pass that causes all 2FA codes issued to be encrypted before being stored in i2Pass.
This update is available as a PTF. This PTF can only be installed on a Release 1.09 version of i2Pass. The correction is available in PTF package IEPTF110. E-mail us and request the PTF package.
Email debug option added for testing.
To help with initial email configuration issues, a debug option has been added to the test email function.
This update is available as a PTF. This PTF can only be installed on a Release 1.08 version of i2Pass. The correction is available in PTF package IEPTF109. E-mail us and request the PTF package.
Optional requirement for user password entered concurrent with 2FA code.
Some customers have a requirement that the user's password be authenticated concurrently with the 2FA code. i2Pass now has an option that supports this requirement for 5250 logon processing.
This update is available as a PTF. This PTF can only be installed on a Release 1.06 version of i2Pass. The correction is available in PTF package IEPTF107. E-mail us and request the PTF package.
Optional maximum signon controls added.
Optional maximum signon controls have been added to the 2FA validation process. These mirror the system values QMAXSIGN and QMAXSGNACN and let you suspend a user profile and/or a signon device when a given number of validations have failed even though a valid user profile/password combination was used.
This update is available as a PTF. This PTF can only be installed on a Release 1.05 version of i2Pass. The correction is available in PTF package IEPTF106. E-mail us and request the PTF package.
Option to only ask for 2FA validation once per day from a given 5250 terminal.
When initially installed, i2Pass will always require a 2FA code when performing a 5250 terminal signon. With this new option, you can configure i2Pass to only require it the first time a user signs on from a given 5250 terminal device. After that, the 2FA code is no longer required for the rest of the day. This feature can be implemented globally or on a user by user basis.
This update is available as a PTF. This PTF can only be installed on a Release 1.04 version of i2Pass. The correction is available in PTF package IEPTF105. E-mail us and request the PTF package.
Second factor authentication code formatting options.
As initially released, i2Pass showed the second factor authentication code to the user as a 9 digit number. At the request of a current customer, we have added some options to the way this is presented so that it can optionally be shown and three 3 digit number separated by a separation character selected by the customer. This improves readability for the customer, especially from a text message.
This update is available as a PTF. This PTF can only be installed on a Release 1.03 version of i2Pass. The correction is available in PTF package IEPTF104. E-mail us and request the PTF package.
Based on a customer request, we have now updated i2Pass to allow for stacking up to three email addresses to be used for code notification purposes. This will allow for the code to be sent to both a users email account and by text to their cell phone. This provides for backup delivery of the code. The code can still only be used once.
This update is available as a PTF. This PTF can only be installed on a Release 1.01 or 1.02 version of i2Pass. The correction is available in PTF package IEPTF103. E-mail us and request the PTF package.
© 2021 KISCO SYSTEMS LLC
54 Danbury Rd. | Suite 439 | Ridgefield, CT 06877
