As of 6.2 and 5.4, we are including an SBOM in the WiKID RPM. It is located in /opt/WiKID.  We have embedded the process in our build system so we can quickly see if any of the libraries we use have any known vulnerabilities.  Needless to say, this greatly enhances the security of our product.  Even if you never look at the SBOM file, we do!   Please update to the latest!  If you have an older version, see how to move all your users to a new WiKID server ..read more

We are pleased to announce the release of Version 6 of the WiKID Strong Authentication server.  The new ISO is based on Rocky 9.  It offers unparalleled security and scalability.  All the supporting packages for WIKID have been upgraded as well. We have also released a tool "migrator.jar" which will easily allow current 5.x or earlier users to migrate to the new platform. WiKID's OTP-based system is not susceptible to "MFA Fatigue" attacks because the user must initiate the process, not the server. WiKID is ideally suited for companies that need two-factor authentication for AD ..read more

We are fairly confident that we are not vulnerable to the Log4J bug, but we will be releasing an update soon with an updated version of Log4J.  Stay tuned ..read more

We've recently had more questions about deploying WiKID for two-factor authentication for AD admins to thwart potential privilege escalation in ransomware attacks.  We've done a proof-of-concept showing that WiKID can make privilege escalation quite difficult.  We realized that we missed a key question about deploying two-factor authentication for admins:  how do I know I won't lock out all my admins?  That's a damn good question.  And here's the answer: When an admin requests a one-time password from WiKID, it overwrites the current AD password with the OTP.  The ..read more

If you woke up Monday morning to a number of upset and confused Anroid token users, we apologize.  We did too.  Over the weekend Google released an update the Chrome that included a bug that deleted other app's localstorage.  Unfortunately, the data is gone.  The users will need to be re-registered.  The new version was rolled out to 50% of Android users.  Google is still working on a fix.  They are not sure if the user data can be restored. We will update as we learn more ..read more

Our recent 5.0 release focused on speed and scalabilty, as well as adding a RESTful version of our API and other enhancements.  The speed improvements are truly impressive.  Here's a 2-CPU VirtualBox VM with 6 gigs of RAM running our previous 4.2 release: Transactions TX/Minute TX/Hour 10,000 558 33,495 10,000 627 37,667 10,000 654 39,256 10,000 647 38,847 Average 621 37,317   So, an average of 621 transactions per second.  A transaction here includes a small number of registrations of new users and a large number of authentications. Now, let's update the same server to 5.0: Transactions TX/Mi ..read more

We've officially released version 5.0 of the WiKID Strong Authentication Server.  There are numerous improvements in this release, most under the hood.  Speed is dramatically increased.  We have setup a separate logging system so that logs no longer go into the postgres database.  We have also fine-tuned the WiKIDAdmin web UI to increase speed and reduce overhead. For customers that use our API, we have released a RESTful version of it.  Please see /opt/WiKID/tomcat/webapps/WiKIDAdmin/exampleREST.jsp for a fully commented page with all the functionality. We also added the ability to run the po ..read more