We’ve identified what appears to be a limitation in the current IAFI rf IDEAS implementation that we’d like to request as an enhancement.
During testing, we confirmed that the rf IDEAS reader’s Card Data Hold Time and Lock-out Time for Repetitive Reads can be manually configured using the rf IDEAS Configuration Utility (for example, setting both to 9950 ms). The reader then behaves as expected by preventing a second badge read until the configured timeout expires.
However, whenever the reader is reinitialized by IAFI (for example, after a USB unplug/replug or any event that causes IAFI to reprogram the reader), those values are automatically reset to the defaults of:
Card Data Hold Time: 2000 ms
Lock-out Time for Repetitive Reads: 1000 ms
We’ve verified that these timing values are being programmed by IAFI during reader initialization, but we were unable to locate corresponding configurable registry parameters under app.iia.rfideas.
Enhancement Request
Please consider exposing these two rf IDEAS reader timing settings as configurable registry parameters within app.iia.rfideas, similar to the other programmable reader options that are already available.
Proposed parameters:
Card Data Hold Time (milliseconds) / app.iia.rfideas.icrddatahldtm or iDataValidTm
Lock-out Time for Repetitive Reads (milliseconds) / app.iia.rfideas.icrdrptlcktm or iLockoutTm
This would allow administrators to centrally manage these values through UMS and IAFI rather than having to manually configure individual readers.
Business Justification
In our healthcare shared workstation environment using IGEL OS 12 + IAFI AuthOnly + Imprivata + Citrix, we’ve identified a race condition where a second user can badge into a workstation while the first user’s Citrix authentication and application enumeration are still in progress. Because the reader accepts another badge after only one second, this can result in the second badge being processed before the first login workflow has completed.
Allowing administrators to increase the reader’s hold and lock-out timing (for example, to 8–10 seconds) would prevent additional badge reads while the initial authentication completes, significantly reducing the possibility of user crossover and incorrect Citrix application launches on shared clinical workstations.