Digital signature with messaging server 6

Hi all,
I want to implement the following with my messaging server or even with the communication express.
Just as outlook, where users can use a digital signature; Is this possible to be done in the messaging/communication express.
If yes, can you please provide me with the procedure?
Regards,
Scotty

There is full documentation for how to set up and use "S/MIME" in CE.
http://docs.sun.com/app/docs/doc/819-2650/6n4u4dtul?q=S%2FMIME&a=view

Similar Messages

Digital Signatures with SmartCards.

Hi guys,
Has anyone implemented in R/3 digital signatures with smartcards?
Currently I'm at customer side trying to implement digital signatures within workflow processes using ABAP SSF functions. The smartcard devices are already installed, but I can't read the data inside the smartcard, moreover, I can't link the smartcard device with R/3 and I don't know how to do it
I read in some Weblogs and documents that it is necessary a SAP-certified external security product. I believe this external security product is the software that comes inside of smartcard drivers CD. It is something like a little application on which we can sign in data and put our fingerprint.
I guess it is not supposed to develop an interface application between smartcard and R/3! When I started these developments I thought that I only needed to configure some environment variables to connect these devices with R/3 and then develop the ABAP flow logic with SSF Functions - Am I right?
Can anyone provide me some guidelines for this issue?
Thanks in advance,
Ricardo.

The SmartCard device is present at the frontend PC - and that's the place where the digital signature operation has to take place. Important is the "What You See Is What You Sign" principle: it has to be ensured that the data that is to be signed (using the private key stored on the SmartCard) is exactly the same as the one that is displayed to the user.
Notice: there is a different scenario where the server is signing the data (after prompting the user for userID and password and validating that information).
The signed data is then transported back to the server where it is stored (to ensure auditibility); usually you'll have to keep the (archived) data for years; the public key need to be archived as well.
Notice: it is possible to attach the certificate (-> public key) which has been used to sign the data to the signed data.
Regards, Wolfgang

Digital Signature with Password

I created a digital signature with a password. Now, I've forgotten my password. How do I reset it so I can use it?

You can't reset it. Create a new signature.

Digital Signatures with Smart Cards

Hi folks,
It is my first time with digital signatures on R/3 system. Im at customer that uses smart cards (hardware cryptography). We are doing the SAPCRYPTOLIB and front end installations. After finish these tasks, we need to implement the signatures into 3 workflow processes. I already read the SSF programmers guide, API specifications and SSF user guide. But I still have some doubts:
The SSF profile is stored into smart card with private key information, but where are the public keys stored? (PAB Private Address Book of my trusted circle).
Do I need the CRLs? Note: this is only for workflow processes that run inside of customer landscape; this is not a B2B scenario.
We dont have clear yet how we sign the data; we are thinking sign a BOR object. Create an attribute and use it to pass the signer data. Note: for the customer, the objective is user authenticity guarantee.
The BOR object instance ends when the flows finish, so wee need to store the signed data for auditable reasons. A database table can be a good approach or there is another standard way?
P.S.: anyone have documentation about this subject, something like how-to with guidelines?
Thanks in advance,
Ricardo.
Message was edited by:
Ricardo Quintino

The SmartCard device is present at the frontend PC - and that's the place where the digital signature operation has to take place. Important is the "What You See Is What You Sign" principle: it has to be ensured that the data that is to be signed (using the private key stored on the SmartCard) is exactly the same as the one that is displayed to the user.
Notice: there is a different scenario where the server is signing the data (after prompting the user for userID and password and validating that information).
The signed data is then transported back to the server where it is stored (to ensure auditibility); usually you'll have to keep the (archived) data for years; the public key need to be archived as well.
Notice: it is possible to attach the certificate (-> public key) which has been used to sign the data to the signed data.
Regards, Wolfgang

Verifying a Digital Signature using message digest

Hi, i am new to java.
I have a Digitally signed document, i wanna verify this signed document against the original one.
i got the idea from this link:
http://help.sap.com/saphelp_45b/helpdata/en/8d/517619da7d11d1a5ab0000e835363f/content.htm
i signed a pdf doc with my SmartCard. the third party signing tool passed me the PKCS7 digital signature and i stored it in database. the problem arose when i retrieved this digital signature from DB and verified against the original doc using the message digest method. the base64 result strings are always not equal.
I am sure about this:
-the retrieved digital signature was GOOD.
-the original doc was GOOD.
but why i can't get the same 2 message digests? can somebody please help?
below is part of my code:
while (rsetDs.next())
     InputStream DSName2 = rsetDs.getBinaryStream(1);
     ByteArrayOutputStream byteStream = new ByteArrayOutputStream();
     byte[] myByte = Base64.decode(byteStream.toString());
     ByteArrayInputStream newStream = new ByteArrayInputStream(myByte);
     CertificateFactory cf = CertificateFactory.getInstance("X.509");
     Collection c = cf.generateCertificates(newStream2);
     Iterator i = c.iterator();
     while (i.hasNext())
          Certificate cert = (Certificate)i.next();
          X509Certificate cert1 = (X509Certificate)cert;
          try
               java.security.MessageDigest md = java.security.MessageDigest.getInstance("MD5");
               /*=============DB MD (BEGIN)==================*/
               byte [] pubkeyByte = cert1.getPublicKey().getEncoded();
               md.update(myByte);
               md.update(pubkeyByte);
               byte[] raw = md.digest();
               String db_md = Base64.encode(raw);
               /*============DB MD (end)============*/
               /*=============PDF MD (BEGIN)==================*/
               DataInputStream m_disFile = new DataInputStream(new FileInputStream("C:\\" + "original_doc.pdf"));
               int m_iNum = m_disFile.available();
               byte[] msgBytes = new byte[m_iNum];
               m_iNum = m_disFile.read(msgBytes, 0, m_iNum);
               md.update(msgBytes);
               byte[] digestMd = md.digest();
               md.reset();
               String pdf_md = Base64.encode(digestMd);
               /*=============PDF MD (END)==================*/
..thanks in advance.

PKCS#7 SignedData objects are far more complex then it looks like you are taking them. First the PKCS#7 SignedData object will contain the OID for the message digest algorithm used and for the encryption algorithm used. From the looks of your code you are simply assuming MD5.
It also contains all of the data that was signed which is typically much more than just the document. It also of course contains the public keys and signatures which singed the document. In your case it will probably only have one public certificate and one signature.
Also note that a signature is an encrypted hash. Looking at your code I do not see you use encryption at all or rather for verification decryption.
Here is the basic process a signature takes.
MessageDigest md = MessageDigest.getInstance(algOID);
byte[] digest = md.digest(message.getBytes(charEncoding));
Cipher c = Cipher.getInstance("RSA/2/PKCS1Padding");
c.init(Cipher.ENCRYPT_MODE, priKey);
byte[] signature = c.doFinal(digest);Note that the resulting byte array is not the message digest but the encrypted message digest. You must use the corresponding public key to decrypt the signature to get the message digest value. It is because the trusted public key can decrypt the correct message digest that we know it was encrypted by the holder of the private key. It is because the decrypted message digest value is equal to my computed message digest value that we know the document has not be altered...
Now PKCS#7 SignedData does not take the message digest of the document, in your case your PDF. It creates a message digest on an ASN.1 object which includes the bytes of your document plus a bunch of meta data.
For more info on the exact format of a PKCS#7 signature file check out
http://www.rsasecurity.com/rsalabs/pkcs/pkcs-7/index.html
Look through this doucment for SignedData as a starting place and follow through all of the sub objects that make up a SignedData object. This will give you an idea of what is involved.

How to validate XML Digital Signature with XML DB (o PL/SQL) in Oracle 11g

Hi,
Do you know if there is possibility to validate XML Digital Signature using XML DB (or PL/SQL) in Oracle 11g?
Let say I have CLOB/XMLType containing Digitally Signed XML, and I want to validate, that thsi is proper signature. I also have public key of signer (I could store it in CLOB or file or Oracle wallet).
Is it possible to do?
If there is need to install additional component - then which one?
Regards,
Paweł

Hi,
this is what i got from someone...
but the links he gave are not opening up...
u have to place a picture there and have to load the digital signatures as Jpegs on to the server to OA top
and have to refer them in the XML for dynamically get the signature on the reports
when u select the properties of the picture placed in the XML template,
there will be one tab with "URL"... in that u have to give the path for that jpegs
Pls refer the following documents for enabling digital signature on pdf documents.
http://iasdocs.us.oracle.com/iasdl/bi_ee/doc/bi.1013/e12187/T421739T481159.htm#5013638 (refer section 'Adding or Designating a Field for Digital Signature'
http://iasdocs.us.oracle.com/iasdl/bi_ee/doc/bi.1013/e12188/T421739T475591.htm#5013688
(Implementing a Digital Signature
Is the BI Publisher installed on your instance of version 10.1.3.4 or higher?
Pls procure a digital signature as soon as possible. The process can take time. OR we could use any certificate that you already might have OR generate a certificate using Oracle Certificate Authority for demo.

How to set up the digital signature for xi server

dear all,
these days i need to implement a interface using the digital signature technology to enable it's security transition.
we are going to use the digest sign with partner.
Could anyone of you tell me the detailed steps concerning the seting up at xi server for this pupose ?
Thanks a lot !

This is a really urgent request,
does anyone have the experience on this, please give me some hints ,thanks !!
BR
ZhouHui

Digital Signature error message

I am using Windows 7 64bit, Adobe Acrobat XI and have imported my personal digital signature certificate as well as the certificate from the signing authority. They both show in preferences, but mine has a yellow triangle with an exclamation point before it. When I try to sign a pdf document I get the following error message: "You do not have any digital IDs suitable for signing this document". Anyone know what the missing pieces are? Thanks

Investigating the issue there is indeed a “signing private key lifetime” that Adobe seems to be using. This is a setting on our vendor site and is set to 70% of the Public Key Lifetime (which is 5 years). As a result – despite the fact the key can be used to sign messages it would appear that signing documents is set to 3 years and 6 months by virtue of this setting.

Digital signatures with different versions of Reader

I have created a form which requires a digital signature for approval. Typically, an employee will complete the form in Reader and forward it to a supervisor for approval. The supervisor needs to sign it digitally and forward it to me.
The issue we are having is with those employees who are completing the form in Reader and the supervisor (or someone thereafter) has a more updated version of Reader and cannot sign the document. What can we do to stop this from happening? There is no practical way to keep everyone on the same version of Reader. We will have many more forms which require a signature, and we need this issue resolved. (I am using Adobe Acrobat 9 Pro to create the forms.)
Also, is there a way to verify the digital signature without using a third-party source? At this point, we know anyone can create a digital signature using someone's hand-written signature they found on another paper and we would like to prevent this from happening. We need to validate the person who used the digital signature is really that person.
Any help is appreciated! Thank you!

If you are creating your forms in Acrobat 9 Pro. and then Reader-enabling them for digital signatures, then recipients of the form will need to use at least version 8 of the Adobe Reader. Also, you'll need to do a few things during the authoring stage of your form, if your form changes by role (i.e., additional data is entered, annotations, or multiple signatures). Mainly you'll need to use a certification sig. for the first signature and set permitted changes after certifying.
You can find a lot more detail on best practices on developing forms for multiple signatures in the Digital Signature User Guide at:
http://www.adobe.com/devnet/acrobat/pdfs/acrobat_digsig_userguide_90.pdf
The guide also explains how to validate documents (authenticity validation and document integrity validation).

Digital Signatures with Adobe Reader

So i created an adobe form with acrobat 9 and sent it out for all to digitally sign. about half are getting an error when they try to sign it. "The credential selected for signature is invalid"
We are a government agency and use Common Access Cards (CAC) certificates to digitally sign with.
i was hoping someone out there could either point me to a good recource for adobe and digital signatures or to a possible fix.
now we have narrowed it down to the problem being with the specific machine. the user can digitally sign the document on another machine, but not on thier own machine. Also, no one else can sign the doc on thier machine either.
Thanks in advance!

issue still exists. ive been searching for some info on how adobe handles digital signatures, like what folders are created on the machine. im thinking maybe i can clear out the app data for acrobat or something. im at a loss at the moment.

Integrating calendar server with messaging server

hi all,
i have installed messaging server but am not able to bind messaging server and calendar server together.the calendar server does not start with ./start-cal command.i am attaching the ics.conf file below.
!!!! ics.conf Parameter Specification: You can have three kinds of records
!!!! #1) Uncommented Key: Starts with alphabet [a-z] and in the form a="b"
!!!! #2) Commented key: Start with !!<alphabet> OR !![a-z]
!!!! And in the form !!a="b" (min 7 chars length)
!!!! #3) Commented Lines: Starts with ! But not with !![a-z]
!!!! #4) Records other than types #1, #2, #3 will be ignored or won't be
!!!! processed e.g. blank lines, lines starting with non-alphabets etc..
!!!! All these parameters are SINGLE valued
!!!! Imaginary Domain Names siroe.com, varrius.com, florizel.com, and sesta.com
!!!! are used in the examples below.
! Description sent with insufficient disk space messages.
alarm.diskstat.msgalarmdescription = "percentage calendar partition diskspace available"
! Number of seconds between monitoring disk space.
alarm.diskstat.msgalarmstatinterval = "3600"
! Percentage of available disk space that triggers sending a warning message.
alarm.diskstat.msgalarmthreshold = "10"
! Whether alarm.diskavail.msgalarmthreshold is above or below percentage. -1 is below and 1 would be above.
alarm.diskstat.msgalarmthresholddirection = "-1"
! Number of hours between sending warning messages about insufficient disk space sent out.
alarm.diskstat.msgalarmwarninginterval = "24"
! Specifies the SMTP host for server alarms.
alarm.msgalarmnoticehost = "sonlinux.bg2iop.com"
! Specifies the SMTP port for server alarms.
alarm.msgalarmnoticeport = "25"
! Who are server alarms sent to?
alarm.msgalarmnoticercpt = "[email protected]"
! When server alarms are sent, who is the sender?
alarm.msgalarmnoticesender = "[email protected]"
! Default is "From: %s\nTo: %s\nSubject: ALARM: %s of \"%s\" is %u\n\n%s\n"
alarm.msgalarmnoticetemplate = ""
! Description sent with no service response messages.
alarm.responsestat.msgalarmdescription = "calendar service not responding"
! Number of seconds between monitoring services.
alarm.responsestat.msgalarmstatinterval = "3600"
! Only trigger sending a warning message if no service response.
alarm.responsestat.msgalarmthreshold = "100"
! Whether alarm.responsestat.msgalarmthreshold is above or below percentage. -1 is below and 1 would be above.
alarm.responsestat.msgalarmthresholddirection = "-1"
! Number of hours between sending warning messages about no service response sent out.
alarm.responsestat.msgalarmwarninginterval = "24"
! Enable (yes) or Disable (no) browser cache for performance reasons.
browser.cache.enable = "no"
! Retry time in seconds after a recoverable alarm delivery error.
caldb.berkeleydb.alarmretrytime = "300"
caldb.berkeleydb.archive.enable = "0"
! Interval between hotbackup or archivebackup in seconds
caldb.berkeleydb.archive.interval = "120"
! Maximum number of days of archivebackup
caldb.berkeleydb.archive.maxdays = "6"
! Minimum number of days of archivebackup
caldb.berkeleydb.archive.mindays = "3"
caldb.berkeleydb.archive.path = "/var/opt/sun/calendar/csdb/archive"
! Percentage threshold of allowable disk space usage
caldb.berkeleydb.archive.threshold = "70"
! Seconds between checkpointing.
caldb.berkeleydb.checkpointinterval = "60"
! Remove checkpoint files after synchronized? (yes/no)
caldb.berkeleydb.circularlogging = "yes"
! Milliseconds between checking database deadlocks.
caldb.berkeleydb.deadlockinterval = "100"
! Enable more advanced notifications - replyevent/refreshevent/replytodo/refreshtodo considered
! as advanced topics. By default, all these notifications will be published to
! modifyevent and modifytodo respectively. If it is enabled modifyevent will get only
! organizer updates to components and attendees replies and the refreshes triggered by replies
! to components will be published to the respective topics. (yes/no)
caldb.berkeleydb.ensmsg.advancedtopics = "no"
! Create an ENS message when a calendar is created? (yes/no)
caldb.berkeleydb.ensmsg.createcal = "no"
! Create an ENS message when an event is created? (yes/no)
caldb.berkeleydb.ensmsg.createevent = "no"
! Create an ENS message when a task is created? (yes/no)
caldb.berkeleydb.ensmsg.createtodo = "no"
! Create an ENS message when a calendar is deleted? (yes/no)
caldb.berkeleydb.ensmsg.deletecal = "no"
! Create an ENS message when an event is deleted? (yes/no)
caldb.berkeleydb.ensmsg.deleteevent = "no"
! Create an ENS message when a task is deleted? (yes/no)
caldb.berkeleydb.ensmsg.deletetodo = "no"
! Create an ENS message when a calendar is modified? (yes/no)
caldb.berkeleydb.ensmsg.modifycal = "no"
! Create an ENS message when an event is modified? (yes/no)
caldb.berkeleydb.ensmsg.modifyevent = "no"
! Create an ENS message when a task is modified? (yes/no)
caldb.berkeleydb.ensmsg.modifytodo = "no"
! Initial size of the in-memory Event Notification Server message queue. This queue stores all ENS messages other than alarm reminders.
caldb.berkeleydb.ensmsg.qsize = "10000"
! Create an ENS message when an event is refreshed? (yes/no)
caldb.berkeleydb.ensmsg.refreshevent = "no"
! Create an ENS message when a task is refreshed? (yes/no)
caldb.berkeleydb.ensmsg.refreshtodo = "no"
! Create an ENS message when an event is replied? (yes/no)
caldb.berkeleydb.ensmsg.replyevent = "no"
! Create an ENS message when a task is replied? (yes/no)
caldb.berkeleydb.ensmsg.replytodo = "no"
! Create an ENS message when a scheduling request written to the calendar is deleted? (yes/no)
caldb.berkeleydb.ensmsg.schedreq = "no"
! Physical path location of database event, task, and alarm files.
caldb.berkeleydb.homedir.path = "/var/opt/sun/calendar/csdb"
caldb.berkeleydb.hotbackup.enable = "0"
! Maximum number of days of hotbackup
caldb.berkeleydb.hotbackup.maxdays = "6"
! Path for archivebackup
!caldb.berkeleydb.archive.path
! Path for hobackup
!caldb.berkeleydb.hotbackup.path
! Enable/disable of archivebackup feature, yes/no
!caldb.berkeleydb.archive.enable
! Enable/disable of hotbackup feature, yes/no
!caldb.berkeleydb.hotbackup.enable
! Minimum number of days of hotbackup
caldb.berkeleydb.hotbackup.mindays = "3"
caldb.berkeleydb.hotbackup.path = "/var/opt/sun/calendar/csdb/hotbackup"
! Percentage threshold of allowable disk space usage
caldb.berkeleydb.hotbackup.threshold = "70"
! Max megabytes of checkpoint file.
caldb.berkeleydb.logfilesizemb = "10"
! Max threads of database.
caldb.berkeleydb.maxthreads = "10000"
! Megabytes of shared memory.
caldb.berkeleydb.mempoolsizemb = "4"
! Time before which to purge deletelog
caldb.berkeleydb.purge.deletelog.beforetime = "86400"
! Time interval between auto purge of deletelog
caldb.berkeleydb.purge.deletelog.interval = "86400"
! If "yes", open the database in readonly mode
caldb.berkeleydb.readonly = "no"
! Email of calendar database administrator.
caldb.calmaster = "[email protected]"
! Seconds between checkpointing.
caldb.cld.cache.checkpointinterval = "60"
! Remove checkpoint files after synchronized? (yes/no)
caldb.cld.cache.circularlogging = "yes"
!service.calendarsearch.ldap.primaryownersearchfilter = "(&(|(uid=*%s*)(cn=*%s*))(objectclass=icsCalendarUser))"
! Enables ("yes") or disables ("no") cld db cache
caldb.cld.cache.enable = "yes"
! Physical path location of cache database
caldb.cld.cache.homedir.path = "/var/opt/sun/calendar/csdb/cld_cache"
! Max megabytes of checkpoint file.
caldb.cld.cache.logfilesizemb = "10"
! Max threads of database.
caldb.cld.cache.maxthreads = "1000"
! Megabytes of shared memory.
caldb.cld.cache.mempoolsizemb = "4"
! Type of Calendar Lookup Database plugin to use ("local" "algorithmic" or "directory").
caldb.cld.type = "local"
! Count data base statistics? (yes/no)
caldb.counters = "yes"
! Maximum number of calendars with counters.
caldb.counters.maxinstances = "100"
! Maximum number of backlogged requests before the server obtains a new network connection.
caldb.dwp.connthreshold = "1"
! Initial number of connections for DWP client to make to each DWP host.
caldb.dwp.initconns = "2"
! Initial number of threads for handling DWP requests.
caldb.dwp.initthreads = "2"
! Maximum number of connections allowed to a DWP server.
caldb.dwp.maxcons = "1000"
! Maximum number of threads to service HTTP requests in csdwpd.
caldb.dwp.maxthreads = "1000"
! Specifies if the server performs MD5 hash checking of all DWP requests.
caldb.dwp.md5 = "n"
! IP address of a specified DWP server.
!!caldb.dwp.server.[hostname.xyz.com].ip = "a.b.c.d"
! Port number of a specified DWP server (Algorithmic CLD only).
!!caldb.dwp.server.[hostname.xyz.com].port = "59779"
! Default DWP server (LDAP CLD only), used if user's icsDWPhost value does not exist.
!!caldb.dwp.server.default = "hostname.xyz.com"
! Stack size for DWP threads.
caldb.dwp.stacksize = "65536"
! Process alarms on the alarm queue -- that is, store them in the alarm queue when an event/todo is saved
caldb.serveralarms = "1"
! Timeout for contacting ENS. If no response, we assume ENS is not running
caldb.serveralarms.acktimeout = "30"
! Dispatch -- that is, enable alarm dispatching. When an alarm trigger time arrives send out email or ENS message.
caldb.serveralarms.dispatch = "yes"
! Enable binary alarms. Used by csnotifyd and csadmind. (default: yes)
!caldb.serveralarms.binary.enable = "yes"
! Binary alarm url. Used by csnotifyd and csadmind. (default: enp:///ics/alarm)
!caldb.serveralarms.binary.url = "enp:///ics/alarm"
! Custom alarm url. Use this to get xml or calendar mime type contents
!caldb.serveralarms.url = "enp:///ics/customalarm"
! Custom alarm url contenttype. (text/xml or text/calendar)
!caldb.serveralarms.contenttype = "text/calendar"
! Dispatch type for Calendar Server alarms ("ens" o "smtp").
caldb.serveralarms.dispatchtype = "ens"
! Initial number of threads for the Event Notification Server.
caldb.serveralarms.initthreads = "0"
! Specifies how long, in seconds, the server will continue to try reconnecting to ENS before giving up. -1 means forever.
caldb.serveralarms.maxretrytime = "-1"
! Maximum number of threads for the Event Notification Server
caldb.serveralarms.maxthreads = "10"
! Time to sleep, in seconds, after a timeout connecting to ens before making another attempt to connect to ens
caldb.serveralarms.retryinterval = "5"
! Stack frame size for Event Notification Server threads.
caldb.serveralarms.stacksize = "65536"
! Total time, in seconds, to retry connecting to ENS on startup.
caldb.serveralarms.startupretrytime = "30"
! Send alarms to this SMTP host.
caldb.smtphost = "sonlinux.bg2iop.com"
! Specifies the directory in cal/bin/config containing the localized version of the files used to format email notifications.
caldb.smtpmsgfmtdir = "en"
! Specifies the SMTP port.
caldb.smtpport = "25"
! Event reminder format file.
calmail.eventreminder.fname = "mail_eventreminder.fmt"
! Event cancellation format file.
calmail.imipeventcancel.fname = "mail_eventcancel.fmt"
! Event CANCEL NOTIFICATION message format file
calmail.imipeventcancelnotification.fname = "mail_eventcancelnotification.fmt"
calmail.imipeventcancelnotificationrecur.fname = "mail_eventcancelnotificationrecur.fmt"
! Event NOTIFICATION message format file
calmail.imipeventnotification.fname = "mail_eventnotification.fmt"
calmail.imipeventnotificationrecur.fname = "mail_eventnotificationrecur.fmt"
! Event notification format file.
calmail.imipeventpublish.fname = "mail_eventpublish.fmt"
! Event REPLY message format file
calmail.imipeventreply.fname = "mail_eventreply.fmt"
! Event REQUEST message format file
calmail.imipeventrequest.fname = "mail_eventrequest.fmt"
! Task cancellation format file.
calmail.imiptodocancel.fname = "mail_todocancel.fmt"
! Task notification format file
calmail.imiptodopublish.fname = "mail_todopublish.fmt"
! Task REPLY message format file
calmail.imiptodoreply.fname = "mail_todoreply.fmt"
! Task REQUEST Message format file
calmail.imiptodorequest.fname = "mail_todorequest.fmt"
! Task reminder format file.
calmail.todoreminder.fname = "mail_todoreminder.fmt"
! Anonymous login CALID.
calstore.anonymous.calid = "anonymous"
! Does server support only two privacy types for components - PRIVATE (acts as confidential) /PUBLIC instead of PRIVATE/CONFIDENTIAL/PUBLIC
calstore.binaryprivacy.mode = "no"
! When creating new calendar of user, whether to lowercase calendar or not
! Also, when looking up calendar, whether to lowercase or not
calstore.calendar.create.lowercase = "n"
! For a newly created calendar, set the ACL to this
calstore.calendar.default.acl = "@@o^a^r^g;@@o^c^wdeic^g;@^a^fs^g;@^c^^g;@^p^r^g"
! Definition of the "owner" acl
calstore.calendar.owner.acl = "@@o^a^rsf^g;@@o^c^wdeic^g"
! Timezone ID used when importing files.
calstore.default.timezoneID = "America/New_York"
! Whether to filtering the private/confidential events on queries to server
calstore.filterprivateevents = "yes"
! Is user's default calendar included in user's freebusy-calendar-list or not
calstore.freebusy.include.defaultcalendar = "yes"
! Can user's default calendar be removed from user's freebusy-calendar-list or not
calstore.freebusy.remove.defaultcalendar = "no"
! Maximum number attendees to be allowed in a LDAP group when expanding event. Value of 0 means expand group entirely.
calstore.group.attendee.maxsize = "0"
! Maximum number of events created by recurrence
calstore.recurrence.bound = "60"
! Is user's default calendar included in user's subscribed-calendar-list or not
calstore.subscribed.include.defaultcalendar = "yes"
! Can user's default calendar be removed from user's subscribed-calendar-list or not
calstore.subscribed.remove.defaultcalendar = "no"
! For attendee calendar lookup, when encountering string that looks like (jdoe OR jdoe:tv), treat string as a userid (uid) when looking-up in Directory.
! Value can be {uid | cn | gid | res | mailto | cap}
calstore.unqualifiedattendee.fmt1.type = "uid"
! For attendee calendar lookup, when encountering string that looks like ([email protected]) (has @ sign), treat string as a mailto address when looking-up in Directory
! Value can be {uid | cn | gid | res | mailto | cap}
calstore.unqualifiedattendee.fmt2.type = "mailto"
! For attendee calendar lookup, when encountering string that looks like (John Doe) (has space), treat string as a common name (cn) when looking-up in Directory
! Value can be {uid | cn | gid | res | cap}
calstore.unqualifiedattendee.fmt3.type = "cn"
! Maximum number of results returned from LDAP lookup from user search. Value of 0 means no limit.
calstore.userlookup.maxsize = "200"
! Is Server in Virtual Domain mode or not (this affects 5.0p2 only)
calstore.virtualdomain.mode = "n"
! Enable (y) or disable (n) Access Control plugin.
csapi.plugin.accesscontrol = "n"
! Load only the plugin specified in csapi.plugin.authentication.name? (y/n)
csapi.plugin.authentication = "n"
! Enable (y) or disable (n) Calendar Lookup Database plugins.
csapi.plugin.calendarlookup = "n"
! Specifies the name of a specific Calendar Lookup Database plugin to load. If "*", load the plugins.
csapi.plugin.calendarlookup.name = "*"
! Load only the plugin specified in csapi.plugin.database.name or if not specified, load all database plugins in alphabetical order.
csapi.plugin.database = "y"
! Only load this specific plugin if csapi.plugin.loadall is no and csapi.plugin.database is yes.
csapi.plugin.database.name = "cs_caldb_berkeley10"
! Load only the plugin specified in csapi.plugin.datatranslator.name? (y/n)
csapi.plugin.datatranslator = "y"
! Only load this specific plugin if csapi.plugin.loadall is no and csapi.plugin.data translator is yes.
csapi.plugin.datatranslator.name = "cs_datatranslatorcsv10"
! Enable (y) or disable (n) database-to-output format plugins.
csapi.plugin.dbtranslator = "y"
! If "*", then load all the database-to-output format plugins. If a library name, only load that plugin. csapi.plugin.dbtranslator must be set to "yes" to load plugin
csapi.plugin.dbtranslator.name = "*"
! Load all plugins found in the plugins directory? (y/n)
csapi.plugin.loadall = "n"
! Load only the plugin specified in csapi.plugin.userprefs.name? (y/n)
csapi.plugin.userprefs = "n"
! Load only this plugin if csapi.plugin.loadall is no and csapi.plugin.userprefs is yes.
!!csapi.plugin.userprefs.name = "plugin_name"
! Enable the RSA Cypher Encryption Family Services for SSL
!!encryption.rsa.nssslactivation = "on"
! Define the Certificate name for the RSA Cypher Encryption Family
!!encryption.rsa.nssslpersonalityssl = "SampleSSLServerCert"
! Define the location of the RSA Cypher Encryption Family token
!!encryption.rsa.nsssltoken = "internal"
! Specifies if the auto refresh feature is enabled or disbaled. (yes/no)
gse.autorefreshreplystatus = "yes"
! Specifies (in seconds) how long to wait before the server scans the schedule queue for incoming jobs.
gse.belowthresholdtimeout = "3"
! Maximum number of concurrent threads the server uses to process the schedule queue.
gse.maxthreads = "10"
! Maximum length of time the server will retry to complete a group scheduling job.
gse.retryexpiredinterval = "86400"
! Specifies (in seconds) how often the server will retry a previous failing job.
gse.retryinterval = "300"
! Maximum stack size (in bytes) of a group scheduling thread
gse.stacksize = "65535"
! global flags to control notification for invitation and cancellation.
! Enable (yes) Disable (no), default is enabled. Notification will be sent.
ine.cancellation.enable = "yes"
ine.invitation.enable = "yes"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.basedir.path = "/opt/sun"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.betamajorversion = "0"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.betaminorversion = "0"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.caldbtype = "local"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.csinstalldir.path = "/opt/sun"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.csprodbasedir.path = "/opt/sun/calendar"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.csprodclassesdir.path = "/opt/sun/calendar/classes"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.csproddir.path = "/opt/sun"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.csprodjavadir.path = "???"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.csprodlibdir.path = "/opt/sun/calendar/lib"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.csprodtoolsdir.path = "/opt/sun/calendar/tools"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.csproduicustdir.path = "/opt/sun/calendar/uicust"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.fullversion = "6.0"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.majorversion = "6"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.minorversion = "0"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.osarch = "i386"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.osname = "linux"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.ostype = "unix"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.osversion = "2.6.9-22.el"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.patchversion = "0"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.serveruidpassword = "icsuser"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.startupafterinstall = "no"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.startupatboot = "no"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.userauthtype = "ldap"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.userprefstype = "ldap"
! WARNING: DO NOT CHANGE OR DELETE THE FOLLOWING CONFIGURATION FILE ENTRY.
! THIS ENTRY WAS AUTOMATICALLY GENERATED BY THE INSTALLATION PROGRAM.
! IT IS USED ONLY BY THE INSTALLATION AND UNINSTALLATION PROGRAMS.
! THIS ENTRY IS COMPLETELY IGNORED BY ALL OF THE INSTALLED PRODUCTS.
! IF YOU CHANGE OR DELETE THIS ENTRY, THE INSTALLATION AND UNINSTALLATION
! PROGRAMS COULD FAIL THE NEXT TIME THEY ARE RUN.
install.version = "6.0"
! Base DN for LDAP authentication. If not specified, use local.ugldapbasedn.
local.authldapbasedn = "o=bg2iop.com, dc=bg2iop,dc=com"
! Bind credentials (password) for user specified in local.authldapbinddn.
local.authldapbindcred = "admin123"
! DN used to bind to LDAP authentication host to search for user's dn.
local.authldapbinddn = "cn=Directory Manager"

Hi Venigalla,
You can implement a federated portal network (FPN) using the SAP NetWeaver platform to share content between portals.
A federated portal network allows organizations with distributed portal installations, both SAP and non-SAP, to provide a single portal access point per user to portal information, services and applications distributed on portals in the network.
WSRP-based application sharing (FPN Mode used for for integrating content between SAP and Non SAP portals) :-
--> Content administrators on a SAP NetWeaver consumer portal can integrate WSRP portlets (i.e. iViews) from remote non-SAP portals into SAP NetWeaver Portal.
--> SAP NetWeaver developers can create WSRP compliant iViews that can be consumed in non-SAP consumer portals.
You may kindly go through the below link, should be helpful:
http://help.sap.com/saphelp_nw70/helpdata/EN/43/23fb36cad10d23e10000000a1553f7/frameset.htm
Regards,
Anagha

A way to clear digital signatures with presence = "hidden"

LCD 9, Dynamic forms using digital signatures, Reader 9x
I discovered this by accident, so wondering if this is a design feature or a bug.
I have a dynamic form and have sub-forms throughout it. I create a flowed subform for my digital signature that has fields to collect information and then place a fixed subform inside that that actually contains the signature field.
Page1 (flowed)
- SignatureBlocks (subform - flowed)
                - Field1 (textfield)
                - Field2 (textfield)
                -InitSig (subform - flowed)
                                -Field3 (textfield)
                                -Field 4(textfield)
                                                -FixedSub (subform - fixed)
                                                                -DigitalSig (signature field)
                -ReviseSect1 (checkbox)
                -CALCchkRevise (checkbox – calculated read only)
DigitalSig locks down various fields in the form.
My problem has always been that when the form goes to the next person for review there was no option to push the form back a state and allow the prior user to change info that was locked by DigitalSig. Until I discovered this:
If I place a checkbox (ReviseSect1) outside of “InitSig” subform and then run a calculation checkbox (CALCchkRevise) that sets the PRESENCE to “hidden” for InitSig if ReviseSect1 == 1, then toggle ReviseSect1 back to 0 my digital signature is cleared and thus all fields that were locked are now un-locked!
CAR-1601-FM01.Section1.SignatureBlocks.CALCchkRevise::calculate - (JavaScript, client)
if(ReviseSect1.rawValue == 1)
    SignatureBlocks.InitSig.presence = "hidden";
else
    SignatureBlocks.InitSig.presence = "visible";
Is this a design feature or a bug? I like it as I now can have a reviewer toggle the ReviseSect1 checkbox which erases the digital signature and thus opens all those locked fields back up for editing. Before I push this throughout my form (which has many signatures and review cycles) I want to be sure this is not a fluke that will go away when Adobe pushes its 1,037th update for the week for Reader. If you hide a subform that contains a digital signature then un-hide it is it the design feature of hidden/visible to clear the signature? Or is this a bug that will be patched?

A better way is to set two codes on the ReviseSect1 checkbox. CLICK sets the subform invisible and also sets the value of the checkbox to 0 (so that the user does not come back to un-click it and wipe out the signature again). Then put a MOUSE EXIT code that sets the subform to visible. In that way the user clicks the box and the signature subform hides, erasing the signature and un-locking the fields. As soon as they mouse out of the checkbox the subform with the signature becomes visible again. Nice.

Digital signatures with Sapscript

Hello experts.
Had anyone worked with Sapscript using digital signatures?
Is this possible? I believe the Sapscript technology is old to support digital signatures.
The only solution in Sapscript would be to upload the signature images, wouldn't it?
Thank you in advance,
Andrés Sarcevic

Hi,
Is the digital signature in the form of a bmp or tiff ? If yes, then you can have a BDC of SE78(Graphics Management ), which will upload the graphics to the SAP system & then you can use it in your smart form or sap script dynamically.
Regards,
KK

Digital Signatures with PIX and MS IAS

Does the PIX support simple digital signatures? I would like to find a away for an IAS server and a PIX to exchange signed packets.
In particular I am trying to increase the security of the initial PAP shared key exchange during user authentication.
Any help is appreciated. I am coming at this from a windows background.
TIA - Willem

I believe PIX supports simple Dig Sig.

Digital Signature with Flex

Hi,
I'm developing a secure flex application in order to mantain user and password catalog, i need to create SSL Transport channel and a non-repudiation request mechanism. I already review that i could achieve first with HTTP Service for SSL and the second with XML Digital Signature but only i find java and .NET APIs for last. Is there an equivalent flex mechanism (or Action Script) to achieve XML Digital Signature?
Thanks in advance.

Some time ago I was researching for this but never fallowed through it... I can only give some hints I've found during the process, hope they help:
http://code.google.com/p/as3crypto/ (this is a lib that handles a lot of encryption methods including public encryption)
http://www.adobe.com/devnet/air/flex/quickstart/xml_signatures.html (this article talks about what your are trying to achieve, but with Air)
HTH
Gus

Digital signature with messaging server 6

Similar Messages

Maybe you are looking for