We’ve introduced a new feature in Protectimus Dynamic Strong Password Authentication (DSPA): Passwordless Authentication. With this option, administrators can set up login with OTPs only. This removes the risks linked to static passwords while keeping authentication strong and simple for users. In this article, we’ll explain how Protectimus DSPA works by default, what changes with the new “Allow Passwordless” option, and when it makes sense to use passwordless authentication in your systems. Get Started with Protectimus DSPA How Protectimus DSPA Works by Default Protectimus Dynamic Strong Password Authentication (DSPA) solution integrates directly with user directories such as Microsoft Active Directory, LDAP, or any other supported database. It appends a six-digit one-time password (OTP) to each user’s static password. The six digits are generated using the TOTP algorithm and change at fixed time intervals. This makes the final password look like: P@ssw0rd!767815 Here, P@ssw0rd! is the static part, while 767815 is the dynamic OTP that constantly refreshes. Administrators can define how often the OTP changes – from every 30 seconds to longer intervals (the interval must be a multiple of 30). The change frequency can be set individually for each user, and administrators can also choose which groups require DSPA protection and which do not. Importantly, only the last six digits are updated according to the configured schedule, keeping management simple and predictable. In practice, user authentication works like this: to log in, users enter their fixed password and the six-digit OTP together as one string. OTPs can be generated with the Protectimus SMART mobile app, via chatbots in Telegram, Viber, or Facebook Messenger, or using hardware tokens supported by Protectimus DSPA. | Read also: Two-factor authentication for Windows 7, 8, 10 What Changes with “Allow Passwordless” With the “Allow Passwordless” option turned on, users log in only with one-time passwords (OTPs). Static passwords are no longer part of the process. Instead of using a permanent password along with an OTP, authentication depends entirely on dynamic codes that change with each login attempt. This method makes the user experience simpler while also greatly improving security. Weak, reused, or stolen passwords, which are a common cause of breaches, are completely eliminated. At the same time, OTPs make sure that every login is confirmed with a unique, time-limited credential. Administrators can choose how widely to apply this setting. Passwordless authentication can be...