- Copy and register wClient.dll on IIS server.
- Create and copy .asp, .html, and .css files to physical directory
on IIS server. Your employees will log into this site to set up their strong authentication credentials.
- Set appropriate NTFS privileges on physical directory.
- Create IIS virtual directory corresponding to physical directory.
- Set appropriate authentication for virtual directory.
- Copy or download the appropriate certificate file from the WiKID Network Client page to the IIS server.
- Edit Default.asp and change both domain name variables to reflect the Domain Names you have configured.
- Edit done.asp and change the certificate, passphrase and servername variable declarations near the top of the page.
- Edit wlogin.asp and change the certificate and passphrase variable declarations near the top of the page.
- Navigate to Default.asp and begin.
Once you have set up the ASP site, you can e-mail your employees instruct them to WiKID two-factor authentication token client and point them to your intranet site where they can validate themselves.
To set up strong authentication, your users will start their WiKID
client, enter in the appropriate 12-digit Domain identifier, choose
their PIN and get a registration code back from the WiKID Strong
Authentication server. Once the user enters that registration code into
your intranet site, they have completed the WiKID registration process
and can generate valid one-time passcodes that will be accepted by the
WiKID Strong Authentication Server (Unregistered Users can generate
one-time passcodes, but they won't be accepted by the WiKID server for
authentication.)
