This is the place where you can find all the necessary information to enable swekey
authentication in your web site or applications.
How does Swekey authentication work?
Swekey authentication is based on a very simple and efficient client/server architecture.
The client is the Swekey device itself. Each Swekey contains a unique
id (the Swekey Id) and is able to generate a One Time Password (OTP)
from a given Random Token (RT).
The Authentication Server (AS) is hosted and managed by Musbe, it
generates the Random Tokens and verify the authenticity of the Swekey
generated One Time Passwords.
What should my site do to authenticate a user?
When a user opens your login page, you need first to check that a
Swekey is plugged into the user's computer, and if it is the case, you
have to grab its Swekey Id.
Once the Swekey has been identified, you have to authenticate it. To do
it you have to ask the Authentication Server to generate a Random
Token, and then pass this RT to the Swekey in oredr to let it calculate an OTP.
To authenticate the Swekey, send the calculated OTP to the AS; if the
verification is successful, you are sure that the Swekey that generated
the OTP is physically plugged into the user's computer.
How can my web page talk with the Swekey and the Authentication Server?
When plugged, the Swekey installs a plugin and an ActiveX. You
can then query the id of the plugged Swekey and ask it to calculate OTP
with only a few lines of Java Script.
Your site has free access to the Authentication Server using simple
HTTP requests. For obvious security reasons, the queries should be done
from your web server. Depending on the technology you use for your
site, it will be done using CGI, PHP, Java or .NET.
Where should I start?
Documentation for integrators is provided using Tech Notes
Make sure to read Tech Note # 1
, it contains the essential information.
A development kit
and FAQs are also available.
How can I get support?
A public forum is available. You can also contact directly firstname.lastname@example.org