Getting digital signatures working again on NREGA and VBGRAMG

There is a specific kind of stuck that anyone signing documents on NREGA or VBGRAMG will recognise. The portal loads, you reach the signing step, and nothing happens. No error worth reading. The applet box is blank, or it is a grey rectangle, or the page just waits. Your DSC token is plugged in and its own software sees it fine.

The portal is not broken. Your browser is simply too new.

Why signing stopped working

These portals sign documents using a Java browser applet — a small Java program the page loads and runs inside the browser. That was a normal way to build this fifteen years ago.

Browsers have since removed the plugin mechanism applets depend on. Chrome dropped it, Firefox dropped it, Edge never had it. The applet is still there in the page, but nothing is left to run it. So the signing step fails silently, because from the browser's point of view there is nothing to report — it simply does not load that kind of content any more.

Which leaves one workable route: run the browser and runtime combination that still supports applets. Specifically Firefox 43.0.1 and Java 8, both 32-bit.

Doing that by hand is where people lose an afternoon. You need the right Firefox from an archive, the right Java, both in 32-bit even on a 64-bit machine, and then you have to stop Firefox from updating itself — because the moment it does, applet support disappears again and you are back where you started.

What the tool installs

Software	Version	Source
Firefox	43.0.1 (32-bit)	Mozilla's official release archive
Java 8 JRE	Oracle Java 8 (32-bit)	Oracle, via java.com

Both come from the vendors' own archives rather than being bundled, so you are installing the same binaries you would have downloaded yourself.

Then the part that makes it stick: Firefox auto-update is permanently disabled. Without that step the fix has a shelf life of days.

Why Oracle's Java specifically

This question comes up reasonably, because Oracle's Java 8 is awkward to obtain and there are well-maintained open-source builds — Azul Zulu, Eclipse Temurin, Amazon Corretto — that are usually drop-in replacements.

Not here. The applet needs the Java browser plugin, which is a specific library: npjp2.dll. Only Oracle's Java 8 ships it. The open-source builds include the Java runtime itself but deliberately omit the browser plugin, because the browser plugin is exactly the thing the whole industry spent a decade removing.

So the requirement is not a preference for Oracle. It is that npjp2.dll exists in one distribution and not the others, and the portal's applet cannot load without it.

Using it

It is a one-click setup tool: run it, and it fetches and installs both components in the right architecture, then applies the update lockdown. After it finishes, open the pinned Firefox, go to the portal, and the signing applet loads.

Keep that Firefox for the portal and use your normal browser for everything else. Which is also the security posture you want, for reasons worth being blunt about.

Limitations, and one real caveat

• You are running a deliberately outdated browser. Firefox 43 is from 2015 and has years of unpatched vulnerabilities. Use it for the signing portal and nothing else — no general browsing, no email, no downloads.
• Same for Java 8 with the plugin enabled. The browser plugin is disabled everywhere else for good reason. This setup re-enables it because the portal gives you no alternative.
• Windows only, and 32-bit builds specifically, even on 64-bit Windows.
• It will need re-applying. A Windows update, a profile reset, or an IT policy that reinstates Firefox updates can undo it. Re-run the tool.
• It cannot fix your token. If the DSC drivers or the token middleware are the problem, this addresses a different layer entirely.

The honest framing

This is not a good solution. It is the only available one, and the difference matters. The right fix belongs on the portal side — replacing applet signing with something that works in a current browser, as most of the world's signing infrastructure already has.

Until that happens, the people who have to submit these documents need a way to submit them today. The tool makes that a single run instead of an afternoon of archive-hunting, and documents plainly what it is doing to your machine and why.

VBGRAMG DSC Setup on GitHub · Project page