Almost every digital signature problem is a driver problem, a Java problem, or a browser problem. Here is how to tell them apart.
Token not detected
Start with the obvious: try a different USB port, ideally a direct port rather than a hub. If it is still not detected, reinstall the token driver supplied by the token manufacturer. Windows sometimes needs a restart before the driver registers.
Certificate not appearing in the portal
Open the token management utility and confirm the certificate is actually present on the token and has not expired. If it is there but the portal cannot see it, the portalu2019s signing utility is usually the culprit — reinstall it and run it as administrator.
Java errors on government portals
Several portals still depend on a specific Java version. Installing the newest Java often breaks them. Check the portalu2019s stated requirement and match it exactly.
Browser blocking the signer
Modern browsers block the local signing components some portals rely on. Where a portal names a supported browser, use that one rather than fighting the default.
macOS specifics
Tokens work on macOS, but the driver is a separate download and Gatekeeper will usually need to be told to allow it under System Settings, Privacy and Security.
Still stuck
Call us. We install and test tokens for clients regularly and can usually resolve it while you are on the phone.