Kisco Systems
i2Pass
i2Pass : Support : Problem Reports

The following is a list of problems reported for i2Pass along with the solutions that we have developed for them. If you have a problem that is not covered here, ask us via E-mail and we'll address your problem.


Register your E-mail address to receive automatic notification whenever there are changes to i2Pass.


i2Pass Release 2 Problem Reports

Index:


i2Pass Release 1 Problem Reports

Index:


i2Pass Release 2 Problem Reports:

Under unusual circumstances, an expired 2FA code could be accepted as valid.

During QA testing in our test environment, we discovered that under very unusual circumstances, an expired 2FA code could be considered as valid. No current customers were affected, but installing this PTF is recommended.

As of release level 2.03 of i2Pass (PTF level IPPTF203), this has been corrected.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 2.02 version of i2Pass. The correction is available in PTF package IEPTF203. E-mail us and request the PTF package.


Option 8 on the INSTALL menu is not working with the *ALL option.

This option, when used with the *ALL option, could result in an internal program loop with no devices registered.

As of release level 2.02 of i2Pass (PTF level IPPTF202), this has been corrected.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 2.01 version of i2Pass. The correction is available in PTF package IEPTF202. E-mail us and request the PTF package.


i2Pass Release 1 Problem Reports:

Some users can bypass the 2FA signon by pressing the ESC key and taking the F9 command key option.

User profiles with *ALLOBJ authority could circumvent the Two Factor Authentication process in i2Pass by pressing the ESC key while waiting to enter the 2FA code issued by i2Pass. This brings up the ASSIST menu in the IBM i OS. From there, the F9 command key gave the user a command line where they could do anything on the system without having met the requirement of the second authentication process.

As of release level 1.12 of i2Pass (PTF level IPPTF112), this has been corrected. Users with *ALLOBJ authority can no longer bypass the 2FA signon process.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 1.11 version of i2Pass. The correction is available in PTF package IEPTF112. E-mail us and request the PTF package.


During an interactive terminal session, my library list was changed to include the I2PLIB library.

We have corrected this behavior and the product no longer changes a terminal session's library list.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 1.07 version of i2Pass. The correction is available in PTF package IEPTF108. E-mail us and request the PTF package.


Some i2Pass users are experiencing problems when using the system attention key.

Based on a report from a customer, we discovered that under certain circomstances, the system attention setting for a user was getting changed during the i2Pass signon process. This has now been corrected.

The fix for this problem 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.


After using the I2PSET command, we see strange messages in the QSYSOPR message queue.

We discovered some remnant debug code was causing this. It has now been corrected.

The fix for this problem is available as a PTF. This PTF can only be installed on a Release 1.00 version of i2Pass. The correction is available in PTF package IEPTF101. E-mail us and request the PTF package.