Safenet Authentication Client Mac Os X Download

SafeNet Authentication Client customers who are planning to upgrade to MAC OS Yosemite 10.10, should be advised that there is currently a driver incompatibility preventing recognition of SafeNet eToken 5100 and eToken PRO tokens. To overcome this issue, please refer to Tech Note TE1542 on SafeNet’s Support Portal. The SafeNet Authentication client (SAC) must be installed on all MacOSX desktop computers on which the eToken will be used. This document describes the procedure for installing and configuring the MacOSX client.

Safenet Authentication Client Mac Os X Download

Safenet Authentication Client Tools Download

To use PKI, you must specify a PKCS#11 module for your PKI device. To do this, perform the following steps:

Safenet Authentication Client Mac Os X Download 10.11

Safenet authentication client windows 10AuthenticationSafenet authentication client windows 10Download
  1. Open the configuration file based on the operating system:

    • Microsoft Windows: C:ProgramDataNetIQDevice Serviceconfig.properties.

    • Linux: /opt/NetIQ/Device Service/config.properties.

    • Apple Mac OS X: For 6.3 Service Pack 1 and newer versions, open /Library/Application Support/NetIQ/DeviceServiceTool.app/Contents/Resources/config.properties. For prior versions, open /Library/LaunchDaemons/NetIQ/Device Service/config.properties.

  2. Remove the hash sign(#) before vendorModule to remove any comments from the parameter.

  3. Set the vendor module specific dll file name to the parameter.

    pki.vendorModule: <filename>.dll

    For example, pki.vendorModule: rtPKCS11.dll.

    NOTE:You can specify more than one PKCS#11 library with semicolon in the format: pki.vendorModule: eToken.dll;rtPKCS11.dll

    If a vendor module is not located in the system32 directory, use to specify the path. If there are any spaces in the path, ensure not to replace the space with in the path.

    For example, pki.vendorModule: C:Program FilesActivIdentityActivClientacpkcs211.dll.

    NOTE:If you have specified some pki.vendorModules separated by a semicolon, you must specify the same number of values for the parameter pki.blockingMode.

    For example, pki.blockingMode: true;false.

    PKI plug-in of the Device Service supports the automatic mode, where a few known vendor modules are auto-detected. You must specify: pki.vendorModule: auto.

  4. (Optional) Specify the additional parameters:

    Table 3-1

    Method

    Syntax

    Description

    Hash

    pki.hashMethod: SHA256

    The default value is SHA256 and you can specify this value, if a parameter is not presented. The following methods are also supported: SHA224, SHA384, SHA512. To set the methods, ensure that the PKCS#11 module supports the required hash method.

    Padding

    pki.padding: PKCS#1

    The default value is PKCS#1 and you can specify this value, if a parameter is not presented.The following options are also supported: PSS, OAEP.

    Key size

    pki.modulusBits: 2048

    The default value is 2048 bit. For example, eToken PRO 32k does not support it and you need to set 1024 to use it.

    Blocking mode

    pki.blockingMode: true

    This parameter is used to detect and monitor the token connected to your system. It is set to true by default. OpenSC does not support the 'waiting for card' mechanism and it requires to change the option to False. Most of the vendors module work appropriately in the default mode.

    NOTE:If you specify the pki.vendorModule: auto and pki.blockingMode parameters, the pki.blockingMode parameter does not overwrite a blocking mode that is pre-defined for an auto-detectable vendor module.

  5. Save the changes.

  6. Restart the Device Service.