Digital signature valid or invalid depending on the signing Windows user

I have a very strange problem and was not able to determine how to resolve it because I quite don't undestand the mechanisms of signing, it seems.
I have a digital signature issued by a member of the "Adobe Approved Trust List". If I sign a document with Adobe Reader XI or Adobe Acrobat XI Standard logged in with one Windows user account the signature appears valid on any other Windows user account. If I use another Windows user account and sign the document with the same digital signature the signature is invalid in this Windows user account and any other.
I didn't change any settings in any of the Adobe products. I use the standard configuration as present just after a fresh install.
One thing I already checked, which nevertheless doesn't explain this strange behavior, is to enable Windows-Integration in the signature configuration of the Adobe products. If this is enabled both documents (the one signed with the "good" Windows user account and the other signed in a "bad" one) show the signature as valid on any Windows account.
So I am wondering if, besides the signature itself, anything else is integrated into a document while being signed that could explain that behavior and, if this is the case, where the setting, trigger, whatsoever, is, to set up Adobe correctly.
Please help.

What do you mean by "signature is invalid"? Is it a a red X or is it Unknown? A problem with trust results in the "Unknown" status, not "Invalid".
In any case, inspect the signature, first in the Signature panel. It will tell you some info about what's wrong with this signature. Then right-click on the signature and select "Show Signature Properties". You'll get a dialog with more info. In this dialog select "Show Signer's Certificate". Check the chain (in the left pane) and "Revocation" tab for each certificate in the chain.
Compare this info for signatures created on a "good" account and "bad". My guess is that the "bad" account is lacking some certificate-related component.and the "good account has it. The fact that if you turn on Windows integration signature becomes valid tells me that it is something related to account.
Another thing to try is this. Go to C:\Users\<username>\AppData\Roaming\Adobe\Acrobat\11.0\Security folder and see if it has CRLCache folder. If it has, delete it and try to sign again.
Also compare the preferences. Check the Edit->Preferences->Signatures->Verification->More->Verification Time preference. Is it the same on both accounts? Is it "Time when the signature was created"? Is the "Include signature's revocation status" check box in Edit->Preferences->Signatures->Verification->More->Creation and Appearances->More checked in both accounts?

Similar Messages

Please help me with the digital signature validation problem?

Please help me with the digital signature validation problem?

Hi
Execute the program in the Debuggin mode.
In the Debugger Window
Select Breakpoint -> Break point at -> Breakpoint at source code Menu Item and enter the details of the program/include/line no..
Activate the System Debugger On from the Settings Menu.
Hope this would help you.
Murthy
Edited by: Kalyanam Seetha Rama Murthy on Jul 18, 2008 7:20 AM

Digital Signature validation issue in Adapter Module

Hi guys,
we have developed an adapter module for digital signature validation, unfortunately, it simetimes work, sometimes doesnt. Strange is, that the same adapter module works for one customer, while for another one doesn't.
We have sent through some "invalid" messages, which should have been valid at the client, where the module works and theu were flagged as valid. It seems the problem is caused by "special" spanish characters, because validation works for the messages where are only standard chars.
Any idea, what to check? Java version, system encoding?
Any help appreciated,
Olian

Hi,
Not really sure about what causes such issues, but if your module coding uses String and byte[] manipulation, are you using explicite encoding when declaring such types ? I remember facing strange issues with XML field values, and "forcing" encoding to "UTF-8" when appropriate, it solved all my errors (string typed object, when converted internally by the JVM, were not always represented by the same bytes object)
Hope this helps
Chris

Report parameter startdate has a defaultvalue or a valid value that depends on the report parameter startdate forward dependencies are not valid

Hi,
Am trying to develop a report the parameter has an issue, it gives me an error.
There are 2 parameter (1st is Date range like start and end date and 2nd is Loan number)
When ever I select date range the Loan number parameter should go blank. If I input a loan number then date range should go blank.
What should I do. Please help
ERROR --report parameter startdate has a defaultvalue or a valid value that depends on the report parameter startdate forward dependencies are not valid

Hi Kay_MD,
If there are only two parameters, we can use first parameter charge the second one, but the second one cannot charge the first one in turn. Because parameter forward dependencies are not valid. To achieve your requirement, we can create another parameter
to control Date_range and Loan_number parameters. For more details, please see:
Add a parameter named ReportParameter1 with two available values: Date_range and Loan_number.
Use the following expression as the default value in Date_range parameter:
=iif(Parameters!ReportParameter.Value="Date_range",1,"") (1 means a useless value)
Use the following expression as the default value in Loan_number parameter:
=iif(Parameters!ReportParameter.Value="Loan_number",1,"") (1 means a useless value)
Please note that the Date_range and Loan_number parameters should enable Allow blank value (“”), and the blank values should also be contained in available values.
If there are any other questions, please feel free to let me know.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

VBA: Valid digital signature is deemed invalid

I have a valid 3-year code-signing digital certificate recently issued by Symantec. The trouble I'm having is, when I sign my Word macro template (*.dot) with this cert, Word 2007 deems the signature to be invalid.
Word 2007's "Microsoft Office Security Options" dialog says "This digital signature is invalid and cannot be trusted", with no option to trust the publisher. This is not the case in Word 2010 and Word 2013
This is from the same *.dot macro template on all PCs.
Does anyone know of versioning issues regarding the signature validation between Word 2007 and later Word versions? Could it be related to the deprecation of SHA1?
I've already tried the hotfix available from https://support.microsoft.com/en-us/kb/967732, with no success. The version of Word 2007 in question is 12.0.6700.5000.
I would greatly appreciate any help.
Thanks
-cc

Hi Clint,
Thanks for posting on MSDN forum.
This forum is for developers discussing developing issue involve Word product. Since the issue is more relative to end-user, I would like to move it to
Technet forums - Word IT Pro Discussions - Microsoft to get more effective response.
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us.
Thanks for your understanding.
Regards & Fei
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

How do I control the certificate chain construction performed by Acrobat Reader during digital signature validation?

I work in the federal government where there are many certificate authorities and cross certified certificate authorities. Acrobat Reader is building hundreds of certificate chains in attempting to find a trusted root for the signers certificate. It is taking 4 minutes to validate the signature!
The image is the 15th screen shot showing three chains per screen shot. The window elevator has barely moved!

I am now using Adobe Acrobat Reader 11. Signature validation is much better! Perhaps 10 seconds. The only issue I see that the detail pages have misleading messages. The Signature Properties window has no complaints about the signature but the Show Signer's Certificate page still complains about not valid trust anchor.

Digital Signature validation

I have been using digital certificates to sign pdf documents for approximately a year. The signatures can be checked against a CRL which is provided on the internet. So far Adobe Acrobat Reader has worked fine, retreiving CRLS and validating certificates.
Today I found out that since renewing expired certificates ( the default lifetime was set to 1 year) the signatures on old signed documents are unverified . The local time of the computer was stored in the signature not a timestamp.
I found that reader defaults to using the local time of the computer to validate an old signature when a timestamp is not used, this has been rectified in 9.1 so that it uses to date that the signature was generated (why on earth would it use anything else!). I now have the signatures validated by changing this setting providing the date range of the CRL in the reader encompases the end date of the certificate.
However, when the reader updates the CRL in the cache and the new CRL date range does not include that of the original signature the reader throws up an error stating that the CRL is invalid or expired.
How can I get it to agree pass the validation without turning off revocation checking? I have the CRLs that were in force at the time of the signing but there is no way I can provide them to the reader. How can I make the reader apply the current and valid CRL to the old documents. The expiry date of the old certificates are still in there?
I always thought that not having to keep a CRL history for expired certificates was a dumb idea when I read the documents, but I didn't imagine that old signatures would become invalid when the certificate expired (mine have become invalid less thant 5 days after the documents were signed. What were the developers thinking.
This is pushing toward creating certificates with lifetimes of 100's or thousands of years so that they can always be validated.
Anybody have a working solution.

I have found a solution.to this
Using a virtual machine I set the date on the system back to a point in time when the certificates were all valid. I then create a new crl with a lifetime which makes it valid for one month from the real date (today). I then set the date back and copy the crl to the distrubution point.
Hey presto, acrobat reader loads the crl and is quite happy to accept it even though it has events recorded in it that happened after the date on which it was created!.
Problem solved, but for how long?

Digital signatures Office 2013 invalid in 2010

We have pc's with Office 2010, Office 2007 and Office 2013.
When we sign a document(with a certificate issued by a local CA server) in Office 2013, and open that file in Office 2010 or 2007, it says 'invalid signature'. When we open that same document on another pc with Office 2013, the certificate is valid.
What i already tried:
-Another document(it happens at every document signed by Office 2013)
-setting the 'Do not include XAdES reference object in the manifest'
to enabled/disabled in GPO(by adding the office 2010, 2007 and 2013 ADMX templates).
-Setting the 'Legacy format signatures'
to enabled in GPO
If we sign a document in 2010 or 2007, it is valid in all versions of Office.

-setting the 'Do not include XAdES reference object in the manifest'
to enabled/disabled in GPO(by adding the office 2010, 2007 and 2013 ADMX templates).
We need to set the 'Do not include XAdES reference object in the manifest' to
Enabled. After that, sign a new document in Office 2013 and then try to open it in previous version to check the result. The settings may not apply to existing signed documents, you will need to sign a new document to test the result.
For more information about digital signature settings for Office 2013, please refer:
http://technet.microsoft.com/en-us/library/cc545900(v=office.15).aspx
Regards,
Steve Fan
TechNet Community Support

Digital Signature Validation process goes into unending state

Hi all
I am working Adobe Digital Signatures in Web Dynpro Java applications. I have been using [this|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/com.sap.km.cm.docs/media/streamingmedia/developer-areas/user-interface-technology/interactive-forms/securing%20online%20interactive%20forms%20by%20adobe%20(Session%208)/index.html?slide=] webinar to follow steps to configure SSL and validation of Digital Signatures.
After doing all necessary configurations, I am able to run my web dynpro applications containing interactive forms in secure mode.
But when I sign with digital signature and try to validate the form, the application keeps on processing and shows no result.
I tried debugging my application but control does not reach my button action code. I am clueless.
I would be thankful to receive any hints or pointers from you.
Thanks in advance.
Kapil

Following blog discusses solution to this prob
/people/kapil.kamble/blog/2009/07/08/experimenting-with-digital-signatures-in-sap-interactive-forms-by-adobe
Kapil

Digital Signature Validation Issue

Hi All,
I have a problem with my digital signature fields. Whenever the user digitally signs the form, there is a message that says that the form is "Signed and all signatures are valid, but with unsigned changes after the last signature". When I open the signature panel (in Adobe Reader or in the Preview PDF tab of Livecycle) the form indicates that a bunch of fields located on the Master Page were deleted and then added (see below). Does anyone know what is causing this or how to fix it?

I'm having the same issue as well. In addition to the additions/deletions to the master pages, the signature panel indicates that a field on the title page of my form was filled in after validation. I ran a temporary script on the signature field's postSign event, using Acrobat's signatureGetModifications() method, to narrow down where the updates are occurring, and it seems that they're taking place either at the same time the signature is validated or just after. The form is set to automatically preserve scripting changes when it is saved; switching to "manual" doesn't help. Turning field locking on/off doesn't work, either. Once the form has been saved and reopened, though, the problem disappears and the signature validates correctly.
UPDATE 30 DEC 14: The master pages that are being "modified" have separate content areas for navigation buttons; it's these CAs, and their associated subforms and buttons, that Acrobat reports as being modified. I tried commenting out the scripts on the buttons' click events without success.
UPDATE 15 APR 15: I've compared the preSign version of the XML for the field that's being modified with the postSign version and found that the XML is somehow being modified by the act of signing the document. To clarify: I need to fill in a date field on my form to indicate when the form is closed out. I have the signature field's preSign set up to add the current date to the date field. The preSign XML includes <value> and <date> tags, which are missing from the postSign version. Why would applying a signature modify the form's XML?

Digital Signature validation with expired TSA certificate

Hi,
I used Adobe Acrobat 8.2 to sign a PDF document with "certifying signature" (note: not approval signature) using a self-signed certificate and a remote TSA. I did NOT embed long term validation information as described here
http://help.adobe.com/en_US/Acrobat/9.0/Standard/WS934c23d7cc8877da1172e0811fde233c98-8000 .html
The TSA certificate expired on a few days ago and now I am getting "not time valid" error on the TSA certificate (see attached mage)
The signature validates fine since I get the ribbon icon at the top for certified document as described here:
http://www.adobe.com/devnet/acrobat/pdfs/validation_cheat_sheet.pdf
The problem is that I don't get the Clock symbol on the timestamp because Signature Properties says
"signature is timestamped but timestamp could not be verified"
The trust settings for all certificates are fine.
I also changed "Verification Time" in Edit-->Security-->Advanced preferences to be "Time signature was created".
I validated the signature using Adobe Reader 8 as well as 9 and got the same error.
What am I doing or expecting that is wrong ?
Appreciate any help!

Thanks. That worked! Back in the sunshine again
The message is as seen below : "signature is timestamped but TS has expired"
I am assuming this is the right message. If not, do respond.

I am unable to sign with Digital signature using a .PFX file. The button does not appear.

When I try to sign with a Digital signature using a .PFX file, the button to select the signature does not appear. I have JAVE SE 7 U11 10.11.2.21 platform in my add ons and JAVA Consol 6.0.33 and 6.0.35 in my extentions.
This problem is not encountered in Crome or IE-8
ASHISH

Regarding your first question about bookmarks, I think you discovered the answer in when you pressed the address bar. The second tab there has your bookmarks.
As for the keyboard, I'm not sure why your Firefox is reacting so slowly; mine seems to show keyboards even when I don't want them. If you have accumulated a lot of history, perhaps that's an issue?
Did you use any third party software to move your Firefox data from internal memory to the storage card?

Digital Signature only Release Status with 3(Approver) Signer

Hello SDN Folks
I have done all the basic settings for Digital Signature which is sawn in following link
http://wiki.sdn.sap.com/wiki/display/PLM/Digitalsignaturein+DMS
it is work fine with 1 RE (Release) status and 1 Signer
We have in process to implement Digital Signature with only two Status
our scenario is
Document Creator Create Document With Status CR
Document Approver Approve Document With Status RE
now we have scenario that For 1 Document we have 3 Approver and 3 approver must digitally sign on DIR
our status is
only CR(create)---->RE(release)
so how i can attached 3 digital signer with only 1 RE(Release) Status
is it possible to go with 3 digital signer with only 1 RE (Release) Status ????
Regards
Tushar Dave

Hi Tushar,
Your requirement of utilizing 3 different approvers for a single 'Release' status in a document type/s can be addressed via the approach proposed below:
1.Define 3 individual authorization groups
2.Define 3 individual signatures
3.Define a common signature strategy
4.Assign the above 3 individual signatures to the common signature strategy
5.Define the signature sequence(the order in which the 3 approvers must approve)
6.Define users and restrictions(signature assigned to relevant approvers/users)
7.For the document type in question for the 'Release' status,assign the above signature strategy and test.
For more detailed information on using digital signature effectively,refer the below link
http://help.sap.com/saphelp_470/helpdata/en/9f/857f3a1c7b11d294d200a0c92f024a/frameset.htm
Regards,
Pradeepkumar Haragoldavar

Drilldown depending on the oracle application user's securing attributes

Hi all,
I created a html table and I have a specific column that is allowed to drilldown to details but I would like also make this drilldown be depended on the user's securing attributes. If the person has permission the he will see the value and can enter in details, but if he doesnt have the permission he just see the value.
Any ideas?!?!
Thanks in advanced,
Adolfho

Hi Adolfho,
you could try binding the Read Only attribute of this item/region through SPEL. For example, if you have a profile and need to give permission only to users that have the "Y" value on this profile, you can add this to the select clause of your VO:
SELECT fnd_profile.value("profile_name") = 'Y' AS PROF_VALUE
and then you can put the following expression on the Read only attribute of the region:
${!ProfValue}
You can also do this on the controller by getting a reference to the respective OA Bean and calling setReadOnly(boolean) or setAttribute(READ_ONLY_ATTR, Object)...
Hope it helps
Thiago

How to reset the forgotten Windows user account password

I need Toshiba password reset! How do I reset Toshiba laptop? I would be appreciated if you help me Toshiba password recovery, etc. Well, so frequently to meet these problems in our lives. Today, we together share some ways to reset Toshiba password.
Solution1: Toshiba recovery disks help reset lost password
It only works if we created the recovery disks or CD before we forgot the password. The following listed are the steps to reset disk for Toshiba Windows 7 recovery:
a. Start PC, log on Windows 7 and insert an USB flash drive into the driver.
b. Start -> Control Panel -> User Accounts and Family Safety -> User Accounts -> Create a password reset disk.
c. In welcome screen click Next and select the inserted USB flash drive, click Next.
d. Input the login password in the password field and click Next. When progress indicator shows 100% complete, click Finish to exit. Remove the USB driver from PC.
The method is similar to create a Toshiba recovery CD. Now, the Toshiba Windows 7 password recovery disk is ok. Put it in a safe place for people may use it to reset your password.
Steps to recover password with created Toshiba password reset disk:
e. Click Reset Password in the Windows 7 logon window,
f. Insert the created Toshiba recovery USB disk into the USB driver interface, and click Reset password" to open Password Reset Wizard. Click Next to continue.
g. Choose this USB disk recovery Toshiba from the drop down box. Click Next to continue.
h. Input a new password and re-input it again to confirm. Click Next and then Finish to close the wizard.
Solution2: Reset Toshiba laptop by accounts with administrator rights
If there is default or built-in admin account or other accounts with administrator privileges and rights, we can use it for Toshiba password bypass. Take Toshiba XP recovery as example:
A. Boot system from Safe Mode by pressing F8 when PC stars.
B. Access PC with the available account with administrator rights and privileges.
C. Start - Local Users and Groups lusrmgr.msc in the Search box ENTER - Local Users and Groups - choose Users.
D. Right click the account with unlocked password, select Set Password and then input and confirm the new password.
Solution3: Reset Toshiba password with burned ISO image file
We can burn an .iso image file into a bootable USB disk or CD/DVD and reset the forgotten password easily and quickly. Take one of the most popular Windows password reset tool Ainorsoft Windows Password Recovery as example:
a. Download the program from an accessible PC;
b. Burn its .iso file to a blank CD/DVD or USB disk;
c. Bypass the lost Toshiba password with the burned CD/DVD on the locked PC.
Things will not be tricky if we know the methods for Toshiba password reset once we forgot Toshiba laptop password! Please also remember to share them with your friends!

Thanks for sharing this but you are talking always about Toshiba passwordthis is wrong and I think this could be a little confusing this is a workaround for windows user account password.
As far as I know there are no password set by Toshiba.
The user can set the windows user account password if necessary so this workaround describes how to delete a Windows user account password which is common for all computers with preinstalled Windows OS.
However, thanks for posting ;)

Digital signature valid or invalid depending on the signing Windows user

Similar Messages

Maybe you are looking for