Desktop Software Integration

How desktop browsers invoke SecureSign Desktop Software on Windows, Linux, and macOS.

Flow

 Desktop Browser Flow Sequence diagram + SecureSign Desktop Software UI PORTAL (BROWSER) YOUR SERVER SECURESIGN DESKTOP SOFTWARE DSC TOKEN 1 Sign with DSC clicked 2 hashBase64 + requestId SHA-256 document hash 3 DEEP LINK securesign://sign? requestId&hashBase64& callbackUrl&apiKey 4 Detect token, cert, PIN 5 5 Sign hash on token CALLBACK 6 callbackUrl?ss_result={base64 JSON} Inside Desktop Software DSC Sign Certificate + PIN only in app Windows / Linux / macOS desktop UI {"success":true,"signatureBase64":"MEUCIQD...","certificate":{"subjectCN":"Rajesh Kumar"}} No Java | No extension | No token driver
Desktop browsers use securesign:// deep link on all supported OSes

SecureSign Desktop Software

  • Windows: Download installer from Admin Console
  • Linux: sudo apt install securesign-desktop
  • macOS: brew install --cask securesign-desktop
  • Registers securesign:// so browsers can launch the software
  • Runs in the background; user connects DSC token via USB

Desktop browsers redirect to securesign://sign?requestId={uuid}&hashBase64={sha256}&hashAlgo=SHA256&documentType=hash&callbackUrl={encoded}&apiKey={ss_live_xxx} — identical to mobile. See Desktop Browser Flow and Deep Link Protocol.

JavaScript

const params = new URLSearchParams({
  requestId: crypto.randomUUID(),
  hashBase64: sha256Base64,
  hashAlgo: 'SHA256',
  documentType: 'hash',
  callbackUrl: 'https://portal.example.gov.in/sign/callback',
  apiKey: 'ss_live_abc123xyz'
});
window.location.href = `securesign://sign?${params}`;