Authentication & Verification
Classic 2FA / MFA
MFA for AD, LDAP, Databases
Wi-Fi Authentication
Electronic Visit Verification
Popular Integrations
Popular Integrations
Programmable hardware TOTP token in a card format that fits any authentication system
 
            Classic hardware TOTP token with SHA-1 algorithm support
 
            Programmable hardware TOTP token in a key fob format that fits any authentication system
 
            Classic hardware TOTP token with SHA-256 algorithm support
 
            Programmable hardware TOTP token in a card format that fits any authentication system
 
            Classic hardware TOTP token with SHA-1 algorithm support
 
            Programmable hardware TOTP token in a key fob format that fits any authentication system
 
            Classic hardware TOTP token with SHA-256 algorithm support
 
            A free 2FA authenticator app with cloud backup, easy token transfer to a new phone, PIN and biometric authentication protection
Free OTP delivery with chatbots in messaging apps
Delivery of one-time passwords via SMS messages
Free delivery of one-time passwords via email
Free one-time passwords delivery via push notifications
A free 2FA authenticator app with cloud backup, easy token transfer to a new phone, PIN and biometric authentication protection
Free OTP delivery with chatbots in messaging apps
Delivery of one-time passwords via SMS messages
Free delivery of one-time passwords via email
Free one-time passwords delivery via push notifications
Get Started
Classic 2FA / MFA
API Documentation
Software Development Kits
Get Started
Classic 2FA / MFA
API Documentation
Software Development Kits
The Protectmus DSPA (Dynamic Strong Password Authentication) component allows integrating Protectimus two-factor authentication solution with Microsoft Active Directory or any other user directory (AD/LDAP, DBMS). After that, the 2FA dynamic passwords will be requested on all services connected to this directory (for example on Winlogon, RDP, ADFS, and OWA at once).
Protectimus DSPA adds six-digit time-based one-time passwords onto users’ static passwords. The resulting passwords look somehow like this: P@ssw0rd!459812. Where:
- P@ssw0rd! is the fixed part;
- 459812 is a TOTP one-time password that changes within a set time interval.
The administrator sets the one-time password change interval, which must be a multiple of 30 seconds.
There is also an option to set passwordless authentication with ONLY a TOTP one-time password.
From the end-user side, authentication will look like this: to access their accounts, a user must enter their fixed password and a one-time code in one line. To generate OTPs, users should use the app Protectimus SMART.
 
 
 
 
 
 
| Field | Value | Note | 
| Connection URLs | URL to connect to your LDAP server | Example: ldaps://dc1.domain.local:636 For DSPA, you need to use the LDAP connection, and you also need to import the SSL certificate.A standard way:  | 
| Base DN | Full DN of the directory in which your users are stored | Example:  | 
| Password | The password of the specified user | |
| User DN | DN or userPrincipalName of the administrator or user who has access to user information | Example: For DSPA, the user must have rights to change passwords | 
| Timeout (ms) | Connection timeout | 
 
 
 
     
 
 
(&(telephoneNumber=*)(mail=*)) 
 
 
 
 

 
PLEASE NOTE! You can activate the Users’ Self-Service Portal so that your users could add their passwords to the system themselves. Read how to set up a Users’ Self-Service Portal in the Users’ Self-Service Portal Setup Instructions.
 
 
 
So far, the Protectimus DSPA component is only compatible with the in-app 2FA tokens Protectimus Smart OTP, available on iOS and Android, therefore we recommend activating the User Self-Service Portal so that your end users could issue tokens on their own. Read our Self-Service Portal Setup Guide for detailed instructions.
 
 
 
 
     
    Please note: You can enable passwordless authentication for your users, which means they will log in using ONLY one-time passwords (OTPs).
By default, Protectimus DSPA combines the user’s static password with a six-digit time-based one-time password (TOTP). For example, P@ssw0rd!459812, where: P@ssw0rd! is the fixed part, and 459812 is a TOTP one-time password that changes at regular intervals.
With passwordless authentication enabled, your users will only need to enter the TOTP part.
 
 
 
 
 
 
 
To establish LDAPS (LDAP over SSL/TLS) and import the necessary SSL certificate into a Java keystore, you need to obtain the certificate from the LDAP server itself.
Here’s how to get the SSL certificate and import it.
keytool -printcert -sslserver <hostname>:<ssl_port> -rfc > ldap_server_certificate.cerReplace <hostname> with the LDAP server’s hostname and <ssl_port> with the LDAPS port (commonly 636 or 3269 for Active Directory Global Catalog).
keytool -importcert -alias <unique_alias> -file ldap_server_certificate.cer -keystore <path_to_cacerts> -storepass <keystore_password>After importing the certificate, your Java application will be able to establish a secure LDAPS connection to the LDAP server, as it will now trust the server’s SSL certificate. Remember to restart any applications that use this JRE to ensure the new certificate is loaded.
 
 
 
 
 
 
 
 
 
 
 
 
            Protectimus Ltd
Carrick house, 49 Fitzwilliam Square,
Dublin D02 N578, Ireland
Ireland: +353 19 014 565
USA: +1 786 796 66 64
Protectimus Ltd
Carrick house, 49 Fitzwilliam Square,
Dublin D02 N578, Ireland
Ireland: +353 19 014 565
USA: +1 786 796 66 64


