Digitally Signing

Hi
This is Amar i want to know how to create a digital signature in sap, what are requirements for creating. if possible send me any link or if have any document please
amarsap fico g
Regards,
Amarnadh

Hi,
Digital signatures are developed through Smartforms, Contact your ABAP Team to develp this activity.Basically it is required for Certificate printing.
Regards
Maruthi.

Similar Messages

How to Digitally sign a PDF report/Mail automatically?

Hi experts!
I have cron'ed shell script that runs a report (Oracle Reports 6i) and the output the report is a PDF document which i send it as an attachment to a mail recipient on my MS. Exchange server.
This is working fine!
Now, i wish to digitally sign either the message or the PDF document it with a Digital Certificate (from Verisign).
Can you please guide me on how this can be done? Should I do it at the Database level, Application server level or the OS level (sendmail)
[Assume i already have already received my certificate from Verisign]
Thank you in advance for your precious time and replies.
Best Regards
Yogeeraj

Please see this video from Acrobatusers.com's Donna Baker (there is no audio)

After upgrading to iOS 5, my iPhone 4 takes a very long time to open digitally signed emails. I've tried with the SMIME settings enabled, but that doesn't help either. Any ideas on how to resolve this? Thanks in advance.

After upgrading to iOS 5, my iPhone 4 takes a very long time to open digitally signed emails. I've tried with the SMIME settings enabled, but that doesn't help either. Any ideas on how to resolve this? Thanks in advance.

I suspect you may have a corrupt photo or image that is causing the sync to fail or quit. You might want to try removing all of your photos by deselecting them in iTunes then sync - and try adding them by each sub-folders until you are able to nail down which sub-folder of photos, that causes the sync to stop or gives you errors.

Email cannot be read when it is only digitally signed

I, and my boss (using a Curve) have been having continuous trouble with reading emails that have been digitally signed. Now, before people start running down the basics, here's what I have done so far:
1. Installed latest ROM for both devices, still waiting on 4.5 for my 8830...
2. Installed S/MIME application on both devices
3. Installed latest Desktop OS on both machines and synchronized certificates from desktop to device and back
Here is the systems we are using:
1. Exchange 2003
2. BlackBerry Enterprise Server (version unknown, not my department)
3. Verisign certificates, managed on-site
Here are some of the caveats we are experiencing.
1. We can read signed and/or encrypted messages from Outlook (03/07), Entourage (04/08), and Thunderbird problem-free
2. We can read signed AND encrypted, or encrypted ONLY, messages from Mulberry, but we cannot read signed ONLY messages from Mulberry
There is no error message, in fact everything "looks" normal, we are just unable to view the body of the emails. What we do see is similar to this:
Received Using: <mailbox> (S/MIME)
Message Status: Opened
To: <me>
Sent: <date>
From: <Mulberry User>
Subject: <subject>
<img><img> Trusted
[1 Attachment]
application: Unknown (2K)
The <Mulberry User> did some research and sent me the following information:
This is a signed message sent from Outlook:
MIME-Version: 1.0
Content-Type: multipart/signed;
        boundary="----=_NextPart_000_00CE_01C99022.D841F9A0";
        protocol="application/x-pkcs7-signature";
        micalg=SHA1
This is a signed message sent from Mulberry:
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=sha1;
protocol="application/pkcs7-signature";
boundary="==========45CF5864B8BBBF80D9D4=========="
See any difference between those two?
According to the RFC, the "application/x-pkcs7-signature" MIME type is supposed to be handled, by clients, the same as the "application/pkcs7-signature" MIME type, which is the "correct" MIME type. So Mulberry handles it correctly. Outlook does not. And neither does the Blackberry. Because *all* clients *should* honor both types.
http://www.ietf.org/proceedings/05nov/RFCs/rfc2311.txt
"C.1 Early MIME Types
Some early implementations of S/MIME agents used the following MIME types:
   application/x-pkcs7-mime
   application/x-pkcs7-signature
   application/x-pkcs10
In each case, the "x-" subtypes correspond to the subtypes described in this document without the "x-"."
"This memo also discusses how to use the multipart/signed MIME type defined in [MIME-SECURE] to transport S/MIME signed messages. This memo also defines the application/pkcs7-signature MIME type, which is also used to transport S/MIME signed messages. This specification is compatible with PKCS #7 in that it uses the data types defined by PKCS #7."
3.4.1 Choosing a Format for Signed-only Messages
There are no hard-and-fast rules when a particular signed-only format should be chosen because it depends on the capabilities of all the receivers and the relative importance of receivers with S/MIME facilities being able to verify the signature versus the importance of receivers without S/MIME software being able to view the message.
Messages signed using the multipart/signed format can always be viewed by the receiver whether they have S/MIME software or not. They can also be viewed whether they are using a MIME-native user agent or they have messages translated by a gateway. In this context, "be viewed" means the ability to process the message essentially as if it were not a signed message, including any other MIME structure the message might have."
This means that the Blackberry is required, by RFC, to be able to read a signed message even without the aid of S/MIME capable software. The fact that it does not is a failure of the Blackberry.
The above email was in reference to the fact that all of these emails that cannot be read on the devices, can be read in Outlook, and when a signed message is sent from Outlook, it can be read on the devices. Furthermore, this is not to say that the information above is 100% valid and correct, but I am hoping that it sparks some discussion and hopefully a resolution can be found.
Thanks for your time in reading this.
Andrew
BB8830

Well not 100% sure but in my experience the following setting is the problem "Enable S/MIME Encryption on Signed or Weakly encrypted messages". This setting is a per server setting and is found in the general options of the server.
When this is set to true the BES encryptes the message again over the signed message...but then for some reason unknown it doesn't decrypt it back when the client reads it.
Maybe you could ask your admins and try it out and see if it works...

Unable to digitally sign and save a PDF document

I am currently using ADOBE ACROBAT 8.0 Professional (Ver 8.1.0). I provide proofreading service for a client. The client provides me with a PDF which I use the comment and mark up tool to indicate required changes. Once all of the comments are complete, I mark the document approved or disapproved and attach a digital signature.
Recently, many files that I have recieved from the client will not allow me to sign and save the PDF. I can save the PDF without the signature but not when it is digitally signed. The error reads:
"The document could not be saved. A number is out of range"
I queried my client to find out if they have made any changes. They have recently upgraded to Illustrator 4 and they create the PDF's for me from the Illustrator files they work from. There are four teams using the same Illustrator program but not all of them are producing files that I cannot sign and save.
Can anyone tell me what the error indicates? Is there a property assigned to the document that I can not recognize that refers to this problem.
Since the files I work on contain proprietary information, I prefer not to attach them to this forum. If anyone is interested in helping, I will share a file to fully explain my problem.

I will try that, thank you.
Jim Dodge
English Proofreading Coordinator
ASIST Translation Services
4891 Sawmill Road, Suite 200
Columbus, OH 43235-7266
www.ASISTtranslations.com
Tel: 937-596-6649
NOTICE: This electronic mail transmission is for the use of the named
individual or entity to which it is directed and may contain information
that is privileged or confidential. It is not to be transmitted to or
received by anyone other than the named addressee (or a person authorized
to deliver it to the named addressee). It is not to be copied or forwarded
to any unauthorized persons. If you have received this electronic mail
transmission in error, delete it from your system without copying or
forwarding it, and notify the sender of the error by replying via email or
by calling ASIST Translation Services, Inc. at (614) 451-6744, so that our
address record can be corrected.

Can no longer digitally sign PDF's with Adobe Reader 9

On our government network some of us have been upgraded to Adobe Reader 9 but now we can no longer digitally sign some PDF files.
People with Adobe Reader or Pro 8 can. Here is a link to one of the documents:
www.unl.edu/nrotc/Nc3065.pdf
I'm also attaching the document.
The document security shows as "Digital signing allowed" in Adobe Reader 8 but "Not allowed" in Adobe Reader 9.
Is there something wrong with Adobe Reader 9 or something we need to change?
Any constructive advice would be appreciated.

I cannot say for sure, but some of the technology the government uses (like the IRS) uses older technology that is no longer support in version 9. For example the IRS tax forms cannot be fillied in and saved using Reader 9. My bet your seeing a similar problem. There is no workaround. You will need to go back to Reader 8 or get Acrobat 9 Pro or Standard.

How to automate digital signing PDF Files in batch

I am trying to find a way to automate as much as possible the placing of a digital signature on a set of PDF documents. We have Adobe Acrobat Pro 8.1 and the machine has MS Office 2003 with Vista Business. Here's a scenario: A set of documents exist in a TO-BE-SIGNED folder, each unsigned. The user uses MS Access 2003 form with a button with VBA code to open and show the first document in the folder. The AcroExch.App, AcroExch.AVDoc, and AcroApp.Show APIs are used to do this. I found code on the internet to do that. Rather than having my client now have to go through all the manual steps to place a digital signature on the document, I want to streamline it to a single click if possible. Right now he has to click Advanced > Sign and Certify > Place Signature > then click and drag > then enter his password > then click sign > then save and close the doc. Can all this be automated? An added bonus would be automatically saving or moving the signed doc to a different folder when it is signed.
I have created a stamp that allows me to add a stamp with just two clicks. Can such be done to add a digital signature? Is it possible to add a button to the toolbar to do this? Can it be done in Access VBA using some Acrobat API calls? Another feature I want to include is moving quickly from one document to the next in the TO-BE-SIGNED folder. Like the arrow buttons take you from page to page, can a button be added to the Acrobat toolbar to take you from doc to doc in a particular folder? Or can that be done using VBA and some Acrobat API calls? To maintain the security of the password protection and yet cut down on clicks and keystrokes, I would like to input the password just once at the beginning of the session and have it remembered or applied to all the docs that get signed as long as that session is open.
I've found some software that purports to do much of the above, but they are all very expensive and assume a big business with big bucks. If anyone knows of inexpensive software that will REALLY do this, I'm open to that as well, though I'd like to control the process myself if possible. I consider myself a beginner with Acrobat and using API calls and would appreciate any help anyone can give. Is the above clear and even possible?
PS: I'm new to this site and using SDK. I posted this under Security (thinking digital signatures) and was asked to post it here, which I'm glad to do.
Thanks much!

Our workflow is such that on infrequent occasions, we have a digitally signed PDF file and the doctor wants to append a scanned note to it. In the past, we could do this, but not now. In the past, when we added the scanned doc, we received a message saying that the doc is already signed and asking if we want to overrwrite the doc. If we respond Yes, then Acrobat would allow it and the signature would indicate that the original part of the document was not modified, but that something had been changed--namely, a doc had been appended. The signature indicated that something had changed since it was added, but it still allowed the append. The signature would have an exclamation point in a yellow triangle indicating the doc had been updated since signed. For our purposes, that was okay because we know what the change is based on the original doc and we know what is appended. Now, however, we cannot append at all. The only thing that is different that I know of is that the doc was signed with software that is not Adobe Acrobat, even though the other software uses an Adobe Acrobat self-created digital signature.
I hope I've explained that clearly enough.
Thanks for your help.

Digitally signing using Acrobat XI and Mac OS 10.9.2- won't let me type signature- the box appears but can't adjust font or any other aspect of text.

I just purchased Acrobat XI pro for Mac. I have OS 10.9.2 When I got to digitally sign, it only allows me to sign using certificate- which does not render a legible name- and is an apple authorization certificate. Or if I go to "type text" the only type showing in the box is Helvetica 12. I can't adjust that. then I put my name in and that's it. It does not look like a signature. I was hoping to insert an image
or at least have it look like a signature.
What can fix this?
Darcy

When I click "place signature" I only have one option.
It asks me "How would you like to create your signature?
The only option available to me is "use a certificate- When I attempt to use another option there are some but they are not available to me."use an image" draw my signature, or type my signature
are not available.
For that reason I went to preferences to see what I could do to change the settings- and all I could do was manage the certificate signature- so that it looks better than it did.
As an aside- after doing that- the document went on and the person couldn't sign because it had an "open password" If you also know about that- that would be great.
This is the only reason I purchased the Adobe XI so I could draw my signature or type it and have it appear as a signature.

Error 2148073513 When Attempting To Digitally Sign In Acrobat 11 Standard

I'm attempting to use Acrobat 11 Standard to digitally sign a PDF document with a 2048 bit certificate from our internal certificate authority, and I'm receiving the following error:
Error encountered while signing:
The Windows Cryptographic Service Provider reported an error:
The requested operation is not supported.
Error Code: 2148073513
The operating system is Windows 7 Enterprise x64. When I remove Acrobat 11 Standard and install Acrobat 9 Standard on the same Windows 7 system, I am able to successfully sign the document using the same certificate that was giving the error with 11. Also we have been using Acrobat 9 on Windows XP with these same certificates for a long time and never encountered issues with digitally signing.
Any ideas of what might be causing this issue?
Thanks in advance
Josh

Hi Josh,
The error message comes from Windows (not Acrobat), but Acrobat 11 is probably asking Windows to do something that it can't. What it is I don't know because the error message is too vague. One thing we can do is to take Windows out of the picture and see if you can sign when Acrobat accesses the digital ID itself as opposed to asking Windows to do the work. This is a two step process, first, export the digital ID from Windows into a file, and then import the file into Acrobat (it's not really an import, but I'll leave it at that for now).
Step 1 - Export the Digital ID
Launch Acrobat
Select the Edit > Preferences menu item
Select Internet from the Categories list box
Click the Internet Settings button
Select the Content tab on the Internet Properties dialog
Click the Certificates button
Highlight your digital ID and then click the Export button
Click the Next button on the Welcome panel of the Certificate Export Wizard
Select the Yes, export the private key radio button, and then click the Next button. If this radio button is disabled you can stop here and let me know that the private key is not exportable
Select the Include all certificates in the certification path if possible checkbox & the Export all extended properties checkbox and then click the Next button. Only select the top and bottom checkboxes, DO NOT delete the private key!
Create passwords for the file and then click the Next button. You will need this password to sign with so make sure it is something you can remember.
Pick a file name and location. Browse for a location you can remember as you will need to know where you put the file in order to use it to sign with. Click the Next button.
Click the Finish button
Click the OK button on the confirmation dialog
Click the Close button on the Certificates dialog
Click the OK button on the Internet Properties dialog
Step 2 - Add the file to Acrobat
Select Signatures from the Categories list box
Click the More button in the Identities & Trusted Certificates group box
Click the Add ID toolbar button
Click the Next button
Click the Browse button
Navigate to and select the file you exported above and then click the Open button
Enter the password you used above and then click the Next button
Click the Finish button
You will see two items in the list box with the same name. Highlight the one whose Storage Mechanism is "Digital ID File"
Click the Usage Options toolbar button and then select Use for Signing
Close the Digital ID and Trusted Certificate Settings
Click the OK button on the Preferences dialog
The next test is to see if you can sign a file. Please let me know if it works or not.
Thanks,
Steve

Adobe PDF iFilter 9 for 64-bit platforms does not index my PDF files with Digital Sign

Adobe PDF iFilter 9 for 64-bit platforms does not index my PDF files with Digital Sign, why?

hi Phillip
i am not sure what you mean
I downloaded the ifilter and installed it
then configured everything as shown in the pdf file
I tried indexing from scratch exactly as i did successfully in the other computer
and got some errors in the log file
i checked the sql server log and the event viewer logs and got :
Error '0x80004005' occurred during full-text index population for table or indexed view '[Pirsumim_ext_ck].[dbo].[T_PUBLICATIONS]' (table or indexed view ID '2073058421', database ID '14'), full-text key value 0x0000027A. Attempt will be made to reindex it.
The component 'PDFFilter.dll' reported error while indexing. Component path 'C:\Program Files\Adobe\Adobe PDF iFilter 9 for 64-bit platforms\bin\PDFFilter.dll'.
Informational: Full-text retry pass of Full population completed for table or indexed view '[Pirsumim_ext_ck].[dbo].[T_PUBLICATIONS]' (table or indexed view ID '2073058421', database ID '14'). Number of retry documents processed: 1. Number of documents failed: 1.
Changing the status to MERGE for full-text catalog "Pirsumim_ext_catalog_ck" (5) in database "Pirsumim_ext_ck" (14). This is an informational message only. No user action is required.
Informational: Full-text Auto population initialized for table or indexed view '[Pirsumim_ext_ck].[dbo].[T_PUBLICATIONS]' (table or indexed view ID '2073058421', database ID '14'). Population sub-tasks: 1
the same dll worked fine in another computer...
how can i see more details what is wrong with this dll ?
meidad

Update 9.1.2 breaks digital signing documents in Adobe 9 Pro on Windows XP

I am able to digitally sign documents using an Aladdin eToken Pro 64k with a fresh copy of Adobe 9 Pro for Windows. However when I update to version 9.1.2 digital signing fails with an "error encountered while BER decoding". Signing still works on Vista and Adobe 9.1.2 Pro. I've checked to make sure none of the settings relating to digital signing changed during the update and none have. Anyone have any ideas on how to correct the problem?

Hi Nick,
First up, there was a small error in my previous post. I said the version of Acrobat (and whenever I say Acrobat I really mean both Acrobat and Reader, but I'm too lazy to type both) that was modified to fix the bug in SHA-1 fallback was 9.1.3, but I really meant 9.3. Sorry about that.
I saw your post from yesterday (http://forums.adobe.com/thread/563601) where you broached the BER decoding error, but in the post above you said signature creation isn't failing any more, so hopefully some update has fixed the problem.
Here's a little bit about the BER Decoding error. During the signing process Acrobat writes the entire file to disk (which is why you always get the Save As dialog as part of the signing process) in the signed state with everything but the actual signature. However, it does leave a hole in the file where the BER encoded cryptographic data will reside once it's be computed and formatted. One thing that is created before the actual signature is the signature appearance. The signature appearance in the form field isn't really the signature proper, but just a graphic representation of the actual signature. The reason that the signature appearance is written to disk before the signature is created is because it too is part of the signed data and must exist before the actual signature is created.
In a perfect world, after the file is written to disk, the cryptographic signature is created and written into the hole in the PDF file, and the signing process completes without any problem. However, if we get to the point that the file has been written out, but during the actual signature creation the process fails, that hole I mentioned isn't filled in. It's not really a hole per se, but a block of zeros that act as a placeholder for the BER encoded data. Because there was some sort of failure and Acrobat didn't get the signed data back from the hardware device what you end up with is a PDF file with a signature appearance, but no real signature in the file. When you click on the signature field Acrobat tries to validate the actual signature, it finds the block of zeros where the signed data was supposed to be, it tries to decode the zeros and gets (as you might well imagine) nothing back and displays the BER Decoding error.
Let leaves us with why didn't Acrobat get the signed data back. When using hardware devices, such as tokens or smart cards, the actual cryptographic signing (the encryption of of the digest with the users private key) takes place on the device. Acrobat (nor any other application) doesn't have access to the private key, which is what makes hardware devices more secure. It's up to the device to sign the data and send it back. If there is any kind of breakdown in that communication channel (which I mentioned in my previous post) the signature creation doesn't reach fruition and you're left with an unsigned file that looks like it was signed because there is a signature appearance.
This is a case where we are providing technically correct, and utterly useless information. It's true that we can't decode a bunch of zeros, but what we should be telling the user is there is no signature (it's kind of like the Matrix where there is no spoon ).
I hope this helps explain what you're seeing. If the the signing process breaks down again please make sure you are using the latest version of Acrobat/Reader and the token software is up-to-date. If everything is current and the problem returns please let me know.
Steve

Enable Adobe Reader to Digitally Sign PDF created with Acrobat Pro 9

Hi All,
I am trying to figure out how to enable adobe readers to digitally sign PDFs I create. I currently have Acrobat Pro 9.
Customer Support said that I need to save it as a "Reader Extended" format, but I cant find this option anywhere.
Any help would be appreciated.
Thanks
Matt

Thanks Ben,
Unfortunately, that video is for acrobat X or above and I cant find the "save as reader extended" option in Acrobat Pro 9.
Can this be done from this version?
Thanks again
Matt

Password protecting digitally signed documents in Adobe Acrobat X Pro

I am looking for the combination of steps to get my digitally signed documents to be password protected for secure distribution. My documents contain new "user password" information and a number of "areas" which require digital signatures to be added.
Any input as to how one would construct a document with :
one to three --> digitally signed signatures fields in one document
Password "opening" protection for the document containing the fields; both signatures and sensitive data fields
suggestions on how to make the document open to accepting more signatures without it demanding the creation of a newly saved document after being digitally signed by one signature
I have worked at this a couple of different ways but am having problems finding the right combination/sequence of steps to make it all come together.
Please assist.....
Thanks....

......meaning.......
I can't do locking of the printing or editing of the sheet after i have encrypted and signed it. Trying to do so, wipes out out signatures. Yes, it is a great fullproof to have people be unable to change something someone has signed but if there is an ammendment, can't the creator reserve that right and in an automated sense notify the signers of the rights of the author ?
Maybe I am looking for too much but, it would be great to know if that is the reality of the whole event.
Thanks,
Robert

Acrobat Pro 9.4.5 digital signing, menu gray but properties says allowed

I have a document that had the signing menu gray/disabled. I tried going to Advanced->Security->Remove Security.
The dialogue said "You Cannot change security on this document because the document enables extended features in Adobe Reader. You can save a copy without the xtended Reader features using File->Save A Copy."
I saved a copy, but in the new document the "Remove Security menu prompts for a password.
The new doc's Security properties are::
but the menu for signing is gray/disabled. Is there a way I can sign this document?

Thank you George. I've been using the digital signing facility for about a
year now, and never have seen a digital signature field. Usually I'm signing
PDF's that are not forms, but plain PDFs. I use the typewriter tool to type
over the PDF where there are lines or blank spots, then use the Place
Signature facility to draw the signature region/box and have Acrobat pop in
the JPG of my signature.
Which Document Restriction needs to be changed to "Allow" in order for this
document to be signed the way described above for other PDFs?

HELP - Can no longer digitally sign documents on Adobe Acrobat Pro ver 9 ?

Was able to for the last 8 - 10 months then 2 weeks ago it stopped (intermittently). Now when I go to sign I get through the process and can see my signature on the docuemnt but then I get this error "creation of this signature could not be completed" unknown error - support information CSigDict-1938" and cannot save it.
I deleted my signature and re did it but that has not helped. I am running Windows 7
thanks

Support information has a value as long as the product is supported. I believe Adobe ended Acrobat 9 support about a year ago. Even if there is a problem in the product (and the support information usually indicates a problem in the product) it will not be fixed since the support for this product has ended. Upgrade to Acrobat XI, it is so much better for digital signing than 9.

Cannot open digitally signed PDF's with Acrobat but can with Reader.

My users have PDF files that have been digitally signed by other users.
When opening these files with Adobe Acrobat Pro, it crashes the application.- a generic referenced memory error on some systems, a DDE server error on others, or a font capture error on others - not sure why the discrepancy there.
The files can be opened with Adobe Reader with no error.
We are at Acrobat 9.4.5 and Reader 9.4.5
I have uninstalled and reinstalled Acrobat Pro 9 and verified the same result with Pro 9.0 so it isn't the version or an update.
I have verified this on multiple machines. - I have even installed both pro and reader on one machine and verified that I could open the PDF file with Reader but not Acrobat Pro.
We can open other PDF files with no problem.
I have tried disabling as much of the security options as possible but still get the same result.
If I clear the PDF file fields (including the signatures) in Adobe Reader then it can be opened in Adobe Acrobat Pro.
Does Acrobat Pro authenticate the digital signatures differently than Adobe Reader?
Thank you in advance for your time.

Hi J.O.S.,
Regarding your question "Does Acrobat Pro authenticate the digital signatures differently than Adobe Reader" the short answer is no.
However, there are other things that Acrobat can do with a file that Reader cannot, so there could be an operation that Acrobat is trying to execute (other than signature validation) which is causing the crash. You don't see it in Reader because Reader doesn't know how to do whatever the offending operation is.
That said, can you send me the file that is crashing Acrobat to [email protected] and I'll see if I can figure out what is amiss.
Thanks,
Steve

Digitally Signing

Similar Messages

Maybe you are looking for