Home / Blog / Product Updates
OneSigner 2026.11.6: signed PDFs are now valid in Microsoft Edge
LTV data now goes inside the signature, so Microsoft Edge shows signed PDFs as valid. Also: sign next to any text through the API, clear errors when signing is skipped, and a wrong PIN can no longer lock your token.
OneSigner 2026.11.6 is out. The headline fix: PDFs signed with long-term validation (LTV) now show as valid in Microsoft Edge, not only in Adobe Acrobat. It also lets API callers place a signature next to any text they name, makes failed signing visible instead of silent, and protects USB tokens from being locked by a wrong PIN. It is a free update; the Config app shows an Update available banner on next launch.
1. Signed PDFs are valid in Microsoft Edge too
With LTV switched on, OneSigner used to sign the PDF and then add the certificate's revocation data (OCSP/CRL) in a second, separate save. That is allowed by the PAdES standard and Adobe Acrobat accepts it, but the PDF viewer in Microsoft Edge treats any save after the signature as a change to the document and reports Invalid Signature: Document has modifications that are not allowed, even though the signer's identity is valid.
The revocation data now goes inside the signature itself, at the moment of signing. The signed file has no further saves after the signature, so Edge shows Valid Signature, Document modified: No, and the signature still carries what a validator needs years later. We confirmed both in Edge and with an independent PAdES validator. Nothing to change in your profiles: LTV-enabled profiles use the new method automatically after the update.
2. API: sign next to a text you choose, per request
/api/upload and /api/signing/sign accept textPattern (with optional patternMatch First/Last/All, textPosition Below/Above, offsetX/offsetY and box size). The signature uses the profile's certificate and appearance but goes next to the text you name, for example under For and on behalf of on a quotation, without creating a profile per document layout.
curl -X POST "https://your-server/api/upload?download=true" \
-H "Authorization: Bearer TENANT_TOKEN" \
-F "file=@quotation.pdf" -F "textPattern=For and on behalf of" -o quotation-signed.pdf
3. Failed signing is no longer silent
When a file could not be signed (for example the license expired or the plan limit was reached), an upload with download=true used to answer HTTP 200 with a JSON message, which a script could mistake for success. It now answers HTTP 409 with the reason. Plain uploads keep HTTP 200 and include a signingSkipped field that says why nothing was signed.
4. A wrong PIN can no longer lock your token
- When a token rejects the PIN, the signing profile is paused immediately. The folder watcher makes no further attempts, so a YubiKey, SafeNet or ePass token is not locked by repeated wrong PINs. The portal dashboard shows a red notice and
/api/signing/statuslists the paused profile. Correct the PIN and save the profile to resume. - PINs that were stored as plain text in
appsettings.json(for example after editing the file by hand) are encrypted automatically on the first start. A backup copy of the configuration is written first.
5. Smaller fixes
- Running
OneSignerService.exe --signwithout a request file now prints usage and exits instead of starting the service.
How to update
Download the installer from your OneSign portal and run it over your current version. Your configuration, profiles and portal data are kept. The installer and programs are signed by One Sign Pte. Ltd. If you sign through a watched folder, we recommend signing one test file after the update.



