Autenticazione forte
2FA / MFA tradizionale
MFA per AD, LDAP e database
Self-Service Password Reset (SSPR)
Autenticazione Wi-Fi
Registrazione delle visite
Per iniziare
2FA / MFA tradizionale
Documentazione API
Kit di sviluppo software (SDK)
Token hardware TOTP programmabile in formato tessera, compatibile con i sistemi di autenticazione che supportano TOTP
Token hardware TOTP tradizionale con supporto dell'algoritmo SHA-1
Token hardware TOTP programmabile in formato portachiavi, compatibile con qualsiasi sistema di autenticazione
Token hardware TOTP tradizionale con supporto dell'algoritmo SHA-256
Integrazioni più richieste
App 2FA gratuita con backup cloud, trasferimento semplice dei token su un nuovo smartphone e protezione tramite PIN e autenticazione biometrica
Ricezione gratuita di codici OTP tramite chatbot nelle app di messaggistica
Invio di password monouso (OTP) tramite SMS
Invio gratuito di password monouso (OTP) tramite email
Invio gratuito di password monouso (OTP) tramite notifiche push
Please Note:
- The certificate of Certification Authority (CA) has to be installed on the clients machines in your domain to integrate the On-Premise Platform with such solutions as OWA.
- The Common Name (CN) for which the certificate was issued has to be accessible in your domain to integrate the On-Premise Platform with such solutions as OWA.
Prerequisites:
- AD CS installed with Web Enrollment feature.
- You need to have access to the Web Server template in certsrv.
- Keytool and OpenSSL tools are required.
openssl genrsa -out test-server.key 2048
openssl req -new -key test-server.key -out test-server.csr
http://CA-Server-Name/certsrv


To import the issued certificate, follow the instructions in the “2. How to Import Trusted SSL Certificate” section.
openssl pkcs12 -export -in test-server.cer -inkey test-server.key -out test-server.pfx
keytool -importkeystore -srckeystore test-server.pfx -srcstoretype PKCS12 -destkeystore “C:\Program Files\Protectimus\Platform\keystore.jks” -deststoretype JKS
Then you need to update the protectimus.platform.properties file to apply changes.| PROPERTY NAME | PROTERTY STANDS FOR |
|
Port on which your application listens for HTTPS requests. Typically, platform uses port 8443 by default. |
|
Type of keystore used to store SSL certificates and private keys. Types: JKS, PKCS12. |
|
Password required to access the keystore. |
|
Full path to the keystore file containing SSL certificates and private keys. Please note that the keystore file should be located in the ..\\Protectimus\\Platform folder, in the same place as the .war and .properties files. The path should be indicated with double backslashes, for example C:\\Program Files\\Protectimus\\Platform\\keystore.jks. |
https.port = 8443
https.keystore.type = JKS
https.keystore.password = **********
https.keystore = C:\\Program Files\\Protectimus\\Platform\\keystore.jks
| PROPERTY NAME | PROTERTY STANDS FOR |
|
SMTP server’s hostname or IP address. |
|
Port number for SMTP server. |
|
Username or email account for authentication. |
|
Password associated with the username or email account. |
|
Allows you to set the address from which emails will be sent to the user. |
smtp.host = smtp-server.com
smtp.port = 25
smtp.user = user@example.com
smtp.password = **********
PLEASE NOTE! Additionally, you can configure settings for SMSC and ALIBABA as well.
| PROPERTY NAME | PROTERTY STANDS FOR |
|
SMPP server login. |
|
SMPP server password. |
|
Host or IP address of the SMPP server. |
|
Port for the SMPP server. |
|
Encoding for SMPP messages. |
|
Source or sender address for SMPP messages. |
smpp.server.login = login
smpp.server.password = **********
smpp.server.host = smpp.example.com
smpp.server.port = 12000
smpp.message.encoding = UTF-8
smpp.from.address = Protectimus
If you have other questions, contact Protectimus customer support service.