ICEGATE Guide
Some ICEGATE functions require DSC-based authentication at login, not just at signing time.
While basic ICEGATE access uses your username and password, certain secure functions, particularly submitting or amending Bills of Entry and Shipping Bills, require DSC-based authentication as an additional security layer, confirming it's genuinely you performing the action.
This needs to be active in the background before attempting DSC login.
Plug it in and confirm your system detects it.
On the ICEGATE login page, choose to authenticate via DSC rather than password alone, where prompted.
This authorizes your certificate to complete the login.
Most DSC login failures on ICEGATE trace back to the same causes as signing errors, PKI component not installed or not running, browser blocking the local connection, or an outdated token driver. See our full ICEGATE signing errors guide for detailed fixes.
We provide remote troubleshooting support for ICEGATE DSC login and signing issues.
No, basic browsing and tracking typically only needs your username and password, DSC is required for secure filing actions.
Yes, as long as your token remains connected and your PKI component is running, no need to re-verify constantly.
They use the same underlying certificate and PKI component, but apply at different points, login authentication versus document signing.