	Login \| Contribute \| Search \| Careers \| Contacts
	Language

News

Partners

Support

IPSec VPN Client USB Tokens and SmartCards

IPSec VPN Client

Support

VPN Client Support VPN Client FAQs VPN Gateway Guides Auth. Server Guides VPN Documentation Supported USB Tokens Supported 3G Modems Supported languages Feature request

Online Store

IPSec VPN Client VPN Mobile CryptoMailer

Home > Products > VPN Client > USB Tokens and SmartCards

USB Tokens and SmartCards

TheGreenBow supports several VPN USB tokens

TheGreenBow IPSec VPN client supports USB Tokens as a mean to increase identify authentication, to enforce security policy while keeping it simple for users and IT managers.

Certify yours

USB Token and SmartCard List

The USB Tokens and Smart Card list below shows you the supported Tokens with TheGreenBow VPN Client.

Company	Token	Version
ActivIdentity	Activkey SIM - USB Token	4.0
Aladdin Knowledge Systems Ltd.	eToken PRO CardOS/M4	4.0
	eToken PRO 64k	4.1
	eToken PRO Java 72 k	4.1
Alios smart cards	SPKi72 / ASECard Crypto SmartCard	4.0
Authenex	A-Key® 3600 OTP Token	4.0
Billion	BiGuard OTP token	4.0
Feitian Technologies Co., Ltd.	ePass2000 USB Token	4.5
	ePass3000 USB Token	4.5
Gemalto (aka Axalto)	Gemalto Cryptoflex 32K (v1)	4.0
	Gemalto Cyberflex Access e-gate 32K	4.0
	Gemalto Cyberflex Access 64K (v2c)	4.0
	Gemalto Cyberflex e-gate 32K	4.0
	Gemalto .Net Smart Card	4.5
	Gemalto TPC IM CC	4.6
Oberthur Card Systems	ID-One Cosmo Smart Card	4.0
	AuthentIC Card v220 token USB	4.0
	AuthentIC Card v220 T series (e.g. T0 5.4)	4.0
Safenet	iKey 1000 USB Token	4.0
Zyxel	ZyWALL OTP token	4.0

	Successfully qualified with TheGreenBow IPSec VPN Client in our lab
	Should work with TheGreenBow IPSec VPN Client, scheduled to be certified.

New Token ATR Codes

The Token and SmartCard ATR Code list below are the new ATR Codes that have not yet been added the Generally Available software release of TheGreenBow IPSec VPN Client software.

Note: TheGreenBow IPSec VPN Client software requires only one "vpnconf.ini" file to be defined (see how to declare or to submit it below), so if you need to support multiple new ATR codes in the same time you can add them all into the same "vpnconf.ini" file, one after the others.

Download any ATR Code file below and rename it "vpnconf.ini".

Troubleshootings

Since release 4.6, the IPSec VPN Client may take into account new Token ATR Code as soon as they are declared in an initialization file called "vpnconf.ini". This file "vpnconf.ini" must be saved in the same folder as tgbike.exe (install folder). Create a new "vpnconf.ini" file here.

Unknow ATR

Follow these instructions to install "vpnconf.ini" on your computer:
1. Download

vpnconf.ini
2. Copy "vpnconf.ini" in "TheGreenBow VPN" install folder (the same folder as tgbike.exe)

The software can't find middleware

In case of the middleware was not found:
1. Check in the file "vpnconf.ini" that the keys "pkcs11DllName" and "registry" are correct (See How to declare a new Token ATR Code)
2. Check that the middleware inform in the file "vpnconf.ini" exists on the system

I can't find my token in Token list

Please fill the following form, so we can provide you help:

First Name		Last Name
Company		Phone
Email*

Token Name*
Manufacturer*
Message

How to declare a new Token

The syntax for declaring an ATR in the file "vpnconf.ini" is:

 [atr]

      mask="." 

      scname="." 

      manufacturer="." 

      pkcs11DllName="." 

      registry="."

atr: Token ATR code
mask: Token mask code
scname: Token name
manufacturer: Token manufacturer's name
pkcs11DllName: PKCS#11 middleware file.
registry: Value in the registry that points to the complete path of the DLL.

Note: This information is available from the Token manufacturer.

Exemple:

[3B:65:00:00:9C:02:02:07:02]

              mask="FF:FF:00:00:FF:FF:FF:FF:FF" 

              scname="My token" 

              manufacturer="Token Manufacturer" 

              pkcs11DllName="pkcs11.dll" 

          registry="HKEY_LOCAL_MACHINE:SOFTWARE\\Microsoft\\Windows\\

          CurrentVersion\\App Paths\\TgbIke.exe:DllPath"

Notes:

If the PKCS#11 DLL (here as pkcs11.dll) is not in c:\windows\system32\ then "registry" must be set.
Registry is the value in the registry that points to the complete path of the DLL. The syntax is HKEY_LOCAL_MACHINE:<registry key>:<value in the registry key>.
For example, if a value "DllPath" with content "C:\Program Files\TheGreenBow\TheGreenBow VPN\pkcs11.dll" is created in "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\App Paths\\TgbIke.exe", registry line is : "HKEY_LOCAL_MACHINE:SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\App Paths\\TgbIke.exe:DllPath".

Submit a Token

Your token works with TheGreenBow IPSec VPN Client, but it is not in our list: submit us your token