Why signData.inp File Downloads Repeatedly When Using DSC on Government eProcurement Portals

Users accessing Indian Government eProcurement portals (such as CPPP, GeM, eProcure, State eProcurement systems) frequently encounter an issue where a file named signData.inp (or signData(26).inp, signData(27).inp, etc.) keeps downloading repeatedly when attempting to use a Digital Signature Certificate (DSC).

This Knowledge Base article explains what this file is, why it keeps downloading, and how to permanently resolve the issue using correct system configuration and best practices.

What Is signData.inp?

signData.inp is a Digital Signature input file generated by government procurement portals during DSC-based authentication or document signing.

Purpose of the File

• Contains encrypted transaction or authentication data

• Must be processed and signed by a local DSC signing utility

• Acts as an input payload for cryptographic signing using the USB token

Key Characteristics

Why Does signData.inp Keep Downloading?

Repeated downloads indicate that the signing process is not completing. The portal retries by generating a new signing request each time.

Root Causes

1. DSC Signing Utility Not Running

The browser downloads the file, but no local signer is available to process it.

2. Incorrect or Multiple Signing Utilities Installed

Conflicting utilities prevent proper file handling.

3. Java Runtime Issues

Most DSC signers depend on Java 8 (32-bit).

4. Browser Security Restrictions

Modern browsers may block local system calls.

5. Token Driver Problems

USB DSC token is detected but not functional.

6. Antivirus or Endpoint Security Blocking Local Calls

Security software silently blocks signer communication.

Product / Component Features (DSC Signing Ecosystem)

DSC Token

• Hardware-based cryptographic device

• Stores private key securely

• Password-protected access

DSC Signing Utility

• Bridges browser and USB token

• Monitors .inp files

• Executes cryptographic signing

Java Runtime Environment

• Required runtime for legacy DSC applications

• Enables secure local execution

Technical Explanation (How DSC Signing Works)

1. User clicks "Login / Sign" on portal
2. Portal generates signData.inp
3. Browser downloads the file
4. DSC signer utility intercepts the file
5. User selects certificate
6. Token PIN is entered
7. File is signed
8. Signed response is sent back to portal

If Step 4 fails, the file remains unsigned and keeps downloading.

Common Use Cases

• Bid submission on CPPP portal

• Vendor login using DSC

• Contract document signing

• GeM portal authentication

• State government eProcurement portals

Step-by-Step Solution (Permanent Fix)

Step 1: Remove Existing DSC Software

• Uninstall all DSC signer utilities

• Uninstall token drivers (if multiple installed)

• Restart system

Step 2: Install Correct Token Driver

Install driver based on DSC token brand:

• ePass

• ProxKey

• WatchData

• SafeNet

Verify certificate visibility in token utility.

Step 3: Install Java 8 (32-bit)

⚠️ Mandatory requirement

• Install Java 8 Update (32-bit)

• Open Java Control Panel

• Add portal URLs to Exception Site List

Step 4: Install Official DSC Signing Utility

Install only one signer utility recommended by the portal:

• eSigner

• emBridge

• Other portal-approved signer

Run the utility as Administrator.

Step 5: Browser Configuration

• Use Google Chrome or Microsoft Edge

• Clear cache and cookies

• Disable extensions (ad blockers, script blockers)

• Allow pop-ups

• Avoid Incognito unless required

Step 6: System & Network Checks

• Disable VPN

• Use a single stable internet connection

• Avoid mobile hotspots

• Plug DSC token directly into USB port

Commands / Verification Examples

Java Verification

java -version

Expected:

Java version "1.8.x"
Java(TM) SE Runtime Environment (32-bit)

Common Issues and Fixes

Security Considerations

• Never share DSC token PIN

• Do not use DSC on public computers

• Remove Java exceptions after work

• Avoid third-party unverified signer tools

• Keep token drivers updated

Best Practices

• Always start DSC signer before opening browser

• Use one browser tab per portal

• Save work frequently

• Keep antivirus exclusions for signer utility

• Maintain a dedicated DSC workstation if possible

Conclusion

Repeated downloading of signData.inp is not a portal error, but a local system configuration issue. Once the DSC ecosystem (Token Driver + Java + Signing Utility + Browser) is correctly aligned, the issue is permanently resolved.

Proper setup ensures:

• Faster authentication

• Reliable bid submission

• Reduced login failures

• Improved compliance with government procurement systems

• 
  

#dsc #digitalsignature #etender #eprocurement #cppp #gemportal #dscerror #signdata #signfile #javads c #dsctoken #etendering #governmenttender #bidsubmission #dsclogin #epass #proxkey #watchdata #tenderhelp #dscsupport #ithelpdesk #tenderportal #digitalcertificate #dsctroubleshooting #signingerror #javaproblem #etenderissue #dscindia #governmentportal #bidsigning #tenderissue #dsctool #esigner #embridge #javasecurity #dscfix #signdataerror #tendersupport #itservices #dscsolution #tenderlogin #govtportal #dscrepair #tokenissue #javabug #dscsetup #dsclifecycle