Home > Products > SafeSign Identity Client

SafeSign Identity Client

Strong authentication with cryptographic smart cards and USB tokens

When tokens (either in the form of a smart card, USB token or SIM card) are to be deployed in an organisation, stable software that is based on industry standards and protocols is required. This software should provide either a standards-based PKCS #11 and/or Microsoft CryptoAPI (CSP) implementation, fully compliant with leading industry standards and protocols, while being so flexible that it can be used with multiple smart cards / USB tokens, multiple Operating Systems and multiple smart card readers.

The SafeSign Identity Client middleware is designed to integrate digital signature tokens into numerous certificate-enabled applications in order to provide secure two-factor authentication on all major platforms.

Basically any application that either supports PKCS #11 and/or CSP to work with tokens on any of the supported platforms can make use of the benefits and features of SafeSign Identity Client!

SafeSign IC offers the most comprehensive support available on the market for card operating systems, smart cards, USB tokens, languages and functions. SafeSign IC currently supports more than 80 smart cards and USB tokens. This means you have sustainable and permanent freedom of choice in your purchasing policies when it comes to manufacturer independence. Whether you decide to use IBM, G&D, Siemens, Oberthur or Gemalto products.

It is obvious from the above that SafeSign IC supports absolutely all standard software interfaces no matter which PC operating system you or your individual employees, however diverse they may be, prefer. But even here we want to be completely sure. Extensive compatibility testing in combination with a strong support team guarantees the correct and continuous operation of smart cards, readers or USB tokens and SafeSign IC.

SafeSign® Identity Client Compatibility Proof

SafeSign IC offers flexibility and guaranteed compatibility, whether…

  • for administrators, system integrators, secretarial staff or other users.
  • you use smart cards with card readers or USB tokens.
  • Windows, MAC OS X, Sun or Linux is implemented.
  • browsers, e-mail clients, VPN clients, data encryption or Single Sign On are in place.
  • Chinese, German, English, Finnish, or many other languages are needed.
  • token initialization, PIN/PUK modification or individual adaptation are needed.
  • Microsoft CryptoAPI (CSP), minidriver, PKCS#11, PKCS#12 or PKCS#15 are used.