Yes, you can sign a PDF using a DSC token with any PDF reader that supports certificate-based signatures — the process takes a few minutes once your token is set up, and it produces a signature that’s cryptographically tied to your identity, tamper-evident, and verifiable by anyone who opens the document. This guide walks through the process from start to finish using Adobe Acrobat/Reader, the most widely used PDF software supporting this workflow, though the same general steps apply across most certificate-based signing tools worldwide.
If you’ve never signed a document this way before, the process is more approachable than it looks — plug in your token, pick your certificate, sign, and you’re done.
Content Table
- What You Need Before You Start
- Step 1: Confirm the Certificates on Your DSC Token
- Step 2: Open the Digital Signing Tool
- Step 3: Choose Your Signing Certificate
- Step 4: Customize the Signature Appearance
- Step 5: Choose Where to Save the Signed PDF
- Step 6: Enter Your Token PIN
- Step 7: Let the Software Verify Certificate Validity
- Step 8: Confirm the Signature Is Valid
- Common Issues and How to Fix Them
- Conclusion
- FAQs
1. What You Need Before You Start
Before opening any software, make sure you have these three things ready.
A DSC token with a valid signing certificate. This is typically a USB hardware device issued by a certificate authority, containing your Digital Signature Certificate along with the full chain of trust back to the issuing CA. (For more on how this trust chain works, see our guide: What Is PKI?)
Token driver software installed on your computer. Your certificate authority or token manufacturer provides this software, and it’s what allows your operating system — and any PDF reader — to actually detect and communicate with the token.
PDF software that supports certificate-based signing. Adobe Acrobat and Adobe Reader both support this natively, as do a number of other PDF applications worldwide. This guide uses Adobe’s workflow since it’s the most widely used, but the underlying steps translate closely to other certificate-based signing tools.
2. Step 1: Confirm the Certificates on Your DSC Token
Before signing anything, it’s worth confirming your token’s certificates are properly installed and visible to your system. Most token manufacturers provide a management tool for this — opening it shows your signing and encryption certificates, along with the complete chain of trust back to the root certificate authority.
If your certificates appear here correctly, your PDF software should be able to detect them without any additional setup. If they don’t appear, that’s the first thing to troubleshoot before moving forward — see the common issues section below.
3. Step 2: Open the Digital Signing Tool
With your token plugged in and its certificates confirmed, open the PDF you want to sign.
In Adobe Acrobat or Reader, navigate to All Tools → Use a Certificate, then select Digitally Sign from the available options.
Once selected, you’ll typically click and drag to indicate where on the document you want your signature to appear, then the software moves into the certificate selection step.
4. Step 3: Choose Your Signing Certificate
A dialog box appears listing the Digital IDs available on your system, including the one on your DSC token. Select the correct certificate — pay attention to the issuing authority and expiration date shown, especially if you have more than one certificate installed.
Click Continue once you’ve confirmed the correct certificate is selected.
5. Step 4: Customize the Signature Appearance
Next, you’ll see a preview of how your signature will look on the document, along with options to customize its appearance — some software lets you choose between a standard text format or a custom design, and some allow adding a scanned image of your handwritten signature alongside the certificate details.
This appearance is cosmetic — it doesn’t affect the underlying cryptographic signature, which is embedded in the document regardless of how the visible signature block looks. Once you’re satisfied with the appearance, click Sign.
6. Step 5: Choose Where to Save the Signed PDF
Clicking Sign immediately prompts you for a save location — the software asks where to store the finished, signed document before it actually applies the signature.
Give the file a clear name and choose your destination folder. It’s good practice to save the signed version with a distinct filename from the original unsigned draft, so you always have a clear record of which version carries the actual signature. Once you confirm the save location, the software moves on to authorizing the signature itself.
7. Step 6: Enter Your Token PIN
After confirming where the signed file will be saved, you’ll be prompted for your token’s User PIN — the password you set when your certificate was issued. This step confirms it’s genuinely you authorizing the signature, not just anyone with physical access to the token.
Enter your PIN and confirm. Most tokens allow a limited number of incorrect attempts before locking, so it’s worth double-checking before submitting if you’re unsure.
8. Step 7: Let the Software Verify Certificate Validity
After your PIN is confirmed, the software performs a live check to confirm your certificate hasn’t been revoked, contacting the certificate authority’s OCSP (Online Certificate Status Protocol) responder in real time.
This step requires an active internet connection, since it’s checking your certificate’s current status directly against the issuing authority rather than relying on locally cached information. It typically completes within a few seconds, after which the signature is finalized and written into the file you saved in the previous step.
9. Step 8: Confirm the Signature Is Valid
Once the validity check completes, the PDF reopens showing your applied signature, along with a confirmation banner indicating the signature is valid.
For a closer look, open the Signature Panel, which shows detailed validation information: whether the signature’s trust originates from a recognized trust list (such as Adobe’s Approved Trust List), whether the document has been modified since signing, and exactly when the signature was last checked.
This panel is what any recipient sees when they open your signed document — a clear, verifiable confirmation that the file is genuinely from you and hasn’t been altered since you signed it.
10. Common Issues and How to Fix Them
The token’s certificate doesn’t appear in the signing dialog. This usually means the token driver isn’t properly installed, or the token isn’t detected by the operating system. Reopen your token management tool to confirm the certificate is visible there first, then reinstall the driver if needed.
The OCSP validity check fails or times out. This step requires an active internet connection to reach the certificate authority’s servers. Confirm your connection, and check whether a firewall or network restriction might be blocking the specific OCSP endpoint.
The signed PDF shows a warning instead of a valid confirmation. This typically means the certificate’s issuing authority isn’t recognized by your PDF software’s trust list. According to Adobe’s own documentation, certificate-based signatures rely on a trust relationship between the signer and the recipient’s software, so confirming your CA is included in a recognized trust program avoids this issue for your recipients.
The token PIN is repeatedly rejected. Double-check for caps lock or an unintended keyboard layout issue before retrying, since most tokens lock after a limited number of failed attempts, requiring a reset through your certificate authority.
11. Conclusion
Signing a PDF with a DSC token follows the same basic pattern across most certificate-based signing software worldwide: confirm your token is recognized, select your certificate, choose where to save the signed file, authorize with your PIN, and let the software validate everything before finalizing the signature. Once you’ve done it once, the process takes a couple of minutes and produces a document with a genuinely stronger guarantee than a scanned signature ever could — proof of who signed it, and proof it hasn’t changed since.
If you’re setting this up for the first time, the biggest time investment is getting your token and its drivers properly installed. Everything after that is a quick, repeatable process every time you need to sign.
12. FAQs
1. What is a DSC token used for when signing a PDF?
A DSC token holds a Digital Signature Certificate that lets you apply a certificate-based digital signature to a PDF, cryptographically confirming your identity and the document’s integrity.
2. Do I need an internet connection to sign a PDF with a DSC token?
Yes, most certificate-based signing workflows require an internet connection during signing to perform a live validity check against the certificate authority’s OCSP responder.
3. Can I use a DSC token to sign PDFs in software other than Adobe?
Yes, many PDF applications worldwide support certificate-based signing with a DSC token, though the exact menu steps will vary from the Adobe workflow shown in this guide.
4. Why does Adobe ask where to save the file before entering my PIN?
Adobe confirms the save location first so the destination is set before the signing process authorizes and finalizes the signature, keeping file placement separate from the authentication step.
5. What happens if I enter the wrong PIN too many times?
Most DSC tokens lock after a limited number of incorrect PIN attempts, typically requiring a reset process through your certificate authority to regain access.
6. Does the visible signature appearance affect the actual security of the signature?
No, the visible signature block is a cosmetic display; the underlying cryptographic signature is embedded in the document independently of how the visible appearance is styled.
7. Why does my signed PDF show a warning instead of a valid confirmation?
A warning instead of a valid confirmation usually means the certificate’s issuing authority isn’t recognized by the recipient’s PDF software trust list, even if the certificate itself is legitimate.
8. Can someone tamper with a PDF after it’s been digitally signed?
If a signed PDF is altered after signing, the cryptographic signature breaks and the document will show as invalid or modified when reopened.
9. Is a DSC token the same as a password-protected PDF?
No, a DSC token produces a certificate-based signature that verifies identity and integrity, while password protection on a PDF simply restricts who can open or edit the file.
10. Can I remove or replace a digital signature after applying it?
Digital signatures cannot be edited once applied; if changes to the document are needed, the document must be re-signed after those changes, which will show a new, separate signature.