Agent Key File and Additional Deployment

Agent Key File

The SafeNet server API uses an encrypted key file to secure communication with the server. To accomplish this, a key file is loaded and registered with the agent, and a matching key is registered with the authentication server.

API Example

See the sample code in TestAPI.java for an example of how to call the Authenticate and VerifySignature methods.

To use the API example, the following components are required:

• BSIDJavaAPI.jar
• NetBeans IDE or Eclipse or any other Java development tool

Deploying on Additional Computers

To deploy your completed application to another computer, the following files are required to support the SafeNet server API:

Windows

• Program Files\Thales\JavaSDK\bsidkey\Agent.bsidkey
• Program Files\Thales\JavaSDK\ini\JCryptoWrapperWin.ini
• Program Files\Thales\JavaSDK\jar\BSIDJavaAPI.jar

For 32-bit operating systems, the following files are required:

• Program Files\Thales\JavaSDK\bin\x86\lib\bc-fips-1.0.2.jar
• Program Files\Thales\JavaSDK\bin\x86\lib\BSIDJavaAPI.jar

• Program Files\Thales\JavaSDK\bin\x86\lib\ini4j-0.5.4.jar   For 64-bit operating systems, the following files are required:

• Program Files\Thales\JavaSDK\bin\x64\lib\bc-fips-1.0.2.jar

• Program Files\Thales\JavaSDK\bin\x64\lib\BSIDJavaAPI.jar
• Program Files\Thales\JavaSDK\bin\x64\lib\ini4j-0.5.4.jar

Linux

• /usr/local/Thales/javasdk/lib/BSIDJavaAPI.jar
• /usr/local/Thales/javasdk/lib/bc-fips-1.0.2.jar
• /usr/local/Thales/javasdk/lib/ini4j-0.5.4.jar
• /usr/local/Thales/javasdk/bsidkey/Agent.bsidkey
• /usr/local/Thales/javasdk/ini/JCryptoWrapper.ini

HTTP Proxy

If your organization uses a proxy server to access an extranet or intranet, you need to also configure proxy settings in the INI file. The agent can work with an HTTP proxy only with basic or anonymous authentication.

USE_PROXY=0 (to use a proxy server, set 1)
PROXY_SERVER=127.0.0.1
PROXY_PORT=8080
PROXY_USER=User (optional)
PROXY_PASSWORD=Password