1 Reply Latest reply on Jan 15, 2015 5:04 PM by IsakTen

    ARX CoSign and Signature Appearances

    kjmacon

      We are using a digital signature product called CoSign to create digital signatures using a Topaz signature pad.  The Topaz signature pad is just like a what you see at a retail store.  It captures your handwritten signature and puts it into a graphical image format. After creating the signature you can 'update Acrobat'.  This creates an 'Appearance' in Acrobat Standard 11 which describes how you want your digital signature formatted.  Appearances can have the date, time, and could contain an image.  The image that CoSign updates Acrobat with is their handwritten signature captured via the Topaz signature pad. So it may look like this (handwritten signature, name of person signing, date, time):

      Capture.JPG

      At this particular computer, we have a generic login account for Windows so that we don't have to setup a Windows profile for every user.  When the person that is using that computer has to sign a .pdf document in Acrobat, CoSign will prompt the user for their network credentials so that only they can sign.  The problem is that even though CoSign prompts for network credentials, Adobe will show every 'Appearance' from any user that has logged in via the CoSign prompt.  Therefore, everyone's handwritten signature is available to choose from. And then, even though you signed in, you could get someone else's handwritten image and it could look something like this:

      Capture1.JPG

      Ideally, we want only the 'Appearances' that user 'X' created when he created his signature and not be able to see all 'Appearances'.  The only way that I know to 'fix' this problem is to have each user login to Windows with their own profile.  That way the user will only see the 'Appearances' that he set up in his Windows session.  If we went with that solution we would have to setup ~600 profiles to set up between the two of us IT guys.  We are pretty lazy and would rather not have to do that.  One possible solution was to use Remote Desktop Connection to remote back to the PC at their desk and sign the document.  The problem with that is each PC has two monitors and Remote Desktop Connection doesn't allow you to use both monitors unless you have Windows Ultimate or Enterprise.

       

      Some possible solutions that we would like to avoid are:

       

      1)  use Roaming Profiles

      2)  using Group Policy objects to simulate Roaming Profiles.

       

      Any suggestions would be very much appreciated! Thanks!!!