Home / Blog / Product Updates

OneSigner 2026.11.4: Token Certificates Without a Linked Key, Quieter Folder Signing, and Per-Upload Profiles

Code-signing certificates whose private key is not linked (often YubiKey) now appear and are re-linked with one click; folder signing stops repeated smart card prompts; /api/upload takes a profileId; re-issued licenses arrive automatically.

OneSigner 2026.11.4 is out. It fixes a problem some YubiKey users ran into: a code-signing certificate that clearly sits on the token, but never shows up in the Config app. It also stops repeated smart card prompts from folder signing, lets API callers choose the signing profile per upload, and makes license changes reach your machine without re-entering a key. It includes everything from 2026.10.12, which shipped without a write-up, so that is covered below too. It is a free update; the Config app shows an Update available banner on next launch.

1. Token certificates without a linked private key now show up, and one click links them

Windows keeps a certificate and its private key as two separate things. When a certificate is imported from a .cer file, or a YubiKey is used without its smart card driver having registered the key, the certificate is in the store but Windows does not know which key belongs to it. The Config app used to list only certificates with a private key, so these certificates were simply missing from both the PDF/AKV and the Code Signing lists, even though the key was on the token.

Every certificate list now also shows code-signing certificates whose key is not linked, sorted last and marked NO PRIVATE KEY - click R. Clicking R (Refresh) asks Windows to find the key on the inserted token and link it (certutil -repairstore, the same fix an administrator would run by hand), then reloads the list. If a certificate still has no key, the app says which one and what to check: the token is plugged in, the Certificate Propagation service is running, or the vendor's smart card driver (for YubiKey, the YubiKey Smart Card Minidriver) is installed.

2. Folder signing no longer triggers repeated smart card prompts

When a PDF in a watched folder did not contain the profile's text anchor, the service opened the token key first and only then discovered there was nowhere to put the signature. On some setups this made Windows show Select a smart card device every few minutes. The service now finds the signature position first and only opens the token when there is something to sign. A file that fails stays where it is and is retried after 5 minutes, then less often (up to every 6 hours), or straight away when you replace it.

3. API: choose the signing profile for each upload

  • POST /api/upload accepts an optional profileId form field. It must be an enabled profile of the token's tenant; anything else is refused with 400 profile_invalid before a file is written.
  • New GET /api/tenant/profiles lists the profiles a tenant token may use (id, name, type, enabled). It returns no certificates, folders or PINs.
  • Behaviour change for integrators: if a tenant has more than one profile that could sign the uploaded file type and no profileId is sent, the upload is now refused with 409 profile_required and the list of candidate profiles, instead of a profile being picked silently. Tenants with exactly one matching profile sign exactly as before.
  • One file is signed by one profile: an upload is no longer signed a second time by a folder watcher on the same folder, and a folder watched by two profiles is reported in the log instead of being signed twice.

4. License updates reach your machine automatically

When we re-issue your license on onesign.sg (more tenants, portal users, an extended update period), the service now fetches the new key by itself at start-up and every 12 hours. The new key must pass the same checks as one you type in (signature, this computer, expiry) before it replaces the old one. License → Refresh in the Config app checks right away.

5. From 2026.10.12: security and languages

  • Default password must be changed. Signing in to the portal with the default admin/admin now goes straight to the account page, and nothing else works until the password is changed.
  • Stricter token check on the Azure Key Vault-compatible endpoint used by OneSignTool and AzureSignTool: the token must match exactly, and token prefixes are no longer written to the log.
  • Browser signing in 15 languages. The browser signing component used by the portal and the free signer at onesign.sg/sign now speaks English and 14 Asian languages. A signature uploaded on one tab and drawn on another no longer confuses the Sign button.

Upgrade

  • OneSigner-Setup 2026.11.4: run it over the existing installation. Your appsettings.json, profiles and PINs are kept. Or click Download & Install on the banner in the Config app.
  • If you call /api/upload for a tenant with several signing profiles, add profileId to your requests before upgrading (see section 3).

Nothing changes for keys and documents: the private key still never leaves the token, and files are still signed on your own machine.

Related: OneSigner 2026.10.11: free trial inside the app, trusted timestamps and LTV.

Have a question about this?

Email the team that wrote it, and we will reply directly.