How to install the IRCTC digital signature dongle

Almost every dongle problem is an ordering problem. The hardware is usually fine, the certificate is usually fine, and the thing that went wrong was doing step three before step two.

So the order below is not decorative. Follow it exactly, once, and you will rarely think about the token again.

Install, in this order

1. Unplug the token. If it is already in, take it out. Installing a driver around a connected device is how half-configured installs happen.
2. Close every browser window. Not minimised — closed. The signing component is loaded when the browser starts, so a browser opened before the driver exists will not find it.
3. Install the driver supplied for your specific token. Tokens from different issuers use different drivers, and the wrong one will install cleanly and then not work.
4. Restart the computer if prompted. Do not skip this to save two minutes. You will spend twenty finding out why.
5. Now plug the token in. Windows should recognise it. Give it a moment the first time.
6. Open the token’s own management utility and confirm the certificate is listed and in date. If the utility cannot see it, the browser certainly will not.
7. Open your browser and sign in to the agent interface.
8. Sign one test transaction before you need it. A configuration that looks complete and fails at the signing step is the exact failure mode this order prevents.

Six reasons a dongle is not detected

Work down these in order. They are arranged by how often each turns out to be the cause.

The driver is not on this machine. The token travels between computers; the driver does not. This is the answer far more often than anything else.

The browser was open first. Close it completely and reopen after the token is connected.

The USB port changed. Windows reassigns ports silently, and a token that was working in one port can present as absent in another. Reseat it and restart the browser.

The certificate has expired. Class 3 certificates run for a fixed term. An expired one fails in a way that looks like hardware failure. Check the date in the token utility.

Pop-ups are blocked. The signing step frequently opens one. A blocked pop-up produces silence rather than an error, which sends people looking at the wrong thing entirely.

The token password is wrong. Some utilities reject it without saying so clearly. Stop after two or three attempts — many tokens lock permanently after a set number of failures, and a locked token is a re-issue rather than a reset.

Moving between computers

If you work from more than one machine — a counter and a laptop, say — install the driver on each before you need it.

The token itself moves fine. What does not move is the driver, the browser configuration or the pop-up permission. Discovering all three are missing while a customer waits is a bad afternoon that ten minutes of preparation prevents.

Dongle or OTP login?

Both are legitimate agent logins, and the right answer depends on your circumstances rather than on which is more modern.

A counter with poor mobile reception should be on a dongle. An agent who works from more than one place often prefers OTP. If you are unsure, tell us how you actually work and we will suggest one.

When to stop and call

Two situations are worth stopping rather than persisting with.

A token locking after failed passwords — stop immediately. Continuing turns a recoverable situation into a re-issue.

An expired certificate — no amount of reinstalling will help. It needs re-issuing, and the sooner that starts the sooner you are booking again.