Skip to main content
gernophil
Participant
August 3, 2026
Question

Password for e-signatures wrong until I re-add them

  • August 3, 2026
  • 1 reply
  • 9 views

I have a weird issue with version 2026.001.21745 and .21771. I'm using an e-signature from a .p12 file. It always worked before and so I wanted to use it again this afternoon, but it prompted the password being wrong. It drove me crazy and I verified the password is indeed correct using `openssl pkcs12 -info -in cert.p12 -noout`. Then I just re-added it to my Acrobat Reader and I could use it again. After I wanted to use it again this evening, it again didn't work. So I re-added it and it was working again, but only once. I also removed the whole certificate and re-added it, but it does not help permanently. Is this a known new bug or am I doing sth. wrong?

    1 reply

    Amal Jaiswal
    Community Manager
    Community Manager
    August 3, 2026

     Hi @gernophil ,

    Hope you are doing well, and thanks for reaching out. Sorry for the trouble here, especially since you have already ruled out the obvious cause with OpenSSL.

    A couple of quick questions since this looks like it could be version specific:

    • Are you on Windows or macOS, and is the .p12 file stored on the local disk, or in a synced folder like OneDrive, Dropbox, or a network share?

    • Does this happen only with this one certificate, or with any digital ID added the same way?

    • Have you tried rolling back to the prior release (26.001.21691, before .21745) to see if the behavior goes away?

    This combination (password verified correct outside Acrobat, works once after re-adding, then fails again) points less at the certificate itself and more at something in how Acrobat is caching or re-reading the credential between sessions. A few things worth checking:

    1. If the .p12 lives in a cloud-synced folder, file locking or a brief re-download by the sync client can make Acrobat read a stale or partially written copy of the file on the next launch, which would produce exactly this symptom. Moving a local copy of the .p12 to a plain local folder (not synced) and pointing Acrobat at that copy is worth testing.

    2. Since 26.001.21745 and .21771 are both very recent builds (July 23 and August 1, 2026), it is worth checking Adobe's Known and fixed issues page for anything matching this, since it is updated as new regressions are confirmed, and this one is not showing there yet as of this writing.

    3. Adobe's guide on managing digital ID passwords and the digital ID overview cover how Acrobat stores and validates these credentials day to day, in case there is a setting worth double-checking (for example, whether the ID is set as the default and how Acrobat is configured to prompt for it).

    If none of that explains it, this does sound like a genuine regression worth flagging directly. Let me know what you find with the sync folder test, which is the fastest way to rule in or out the most likely cause.

     

    ~Amal