1 Correct answer
+++ EDITED REPLY, FIXED SOME TYPOS
Hi,
It looks like in the governement the common name of the user, as it appears in the digital signature after it is applied, is taken from the Distinguished Name of the certificate.
This makes things easier for us to figure out because when you get the value from cert.subjectDN.cn that is contained in sigInfo.certificates OR Info.name that is contained in signatureInfo you will get the same result : SMITH.JOHN.UNK .
If this wasn't the case, then when you extr
...
6
Replies
+++ EDITED REPLY, FIXED SOME TYPOS
Hi,
It looks like in the governement the common name of the user, as it appears in the digital signature after it is applied, is taken from the Distinguished Name of the certificate.
This makes things easier for us to figure out because when you get the value from cert.subjectDN.cn that is contained in sigInfo.certificates OR Info.name that is contained in signatureInfo you will get the same result : SMITH.JOHN.UNK .
If this wasn't the case, then when you extract this information to another text field it should read: John Unk Smith
The long answer to your issue is that you don't need to use an array to get this to work. Using the array method doesn't necessarily apply in your case because what you're dealing with is more related to international standards that are enforced with the use of digital signatures.
Some cultures use more than one first name, in other cultures the last name is also the surname, and in other cultures they have no last name at all.
The digital certificate standards that define the 'common name' schemas are not for the user(s) to choose a preferred method of signing, but an international standard as defined in RFC 1485 and the X.509 specifications for public key infrastructure certificates, cryptographic keypair association, and the Internet Engineering Task Force ( IETF ) Request For Comments (RFC) specifications.
These standards also encourage users to keep it as close as possible within the defined schemas of the international standards to aviod these problems when customizing a common name that will be used in a self-signed certificate.
For example, in order to get a specific string of text that is contained in a digital signing certificate, those special characters is what we use as guides to perform ".split" or ".join" methods from the Distinguished Name public component or from the user's identity key attributes.
Therefore, the employment of special characters, such as spaces (" "), dashes ("-"), periods(".") or less than / greater than ("<", ">") symbols, just make make our life easier.
See slide below:
See key attributes here: https://datatracker.ietf.org/doc/rfc1485/?include_text=1
Basics of Digital Certificates:
https://www.sites.google.com/site/ddmwsst/digital-certificates#TOC-CA-Hierarchy
Examples of key attributes:
http://certificate.fyicenter.com/717_Distinguished_Names_on_Certificates.html
Short Anwser:
You'll be fine just taking the first character strings from the First and Last name in order to compose the initials.
However, I did spotted some errors in my initial reply. Use the following instead:
var f = event.target;
var sigInfo = f.signatureInfo();
var cert = sigInfo.certificates[0];
var firstName = cert.subjectDN.cn.split(".")[1];
var lastName = cert.subjectDN.cn.split(".")[0];
//THIS LINE OF CODE WILL TRANSPOSE LAST AND FIRST NAME STRINGS
this.getField("FULL NAME").value = cert.subjectDN.cn.split(".")[1]+" "+ cert.subjectDN.cn.split(".")[0];
//THIS LINE OF CODE WILL PULL THE INITIALS AS DECLARED IN THE firstName AND lastName VARIABLES ABOVE
this.getField("INITIALS").value = (firstName.charAt(0)) + (lastName.charAt(0));
//THIS LINE WILL GET THE SAME DATE AS THE SIGNING TIME. IT WILL AVOID PROBLEMS WITH INCORRECT SYNCHRONIZATION BETWEEN THE SYSTEM CLOCK AND BROWSER TIME ZONES WHEN USING Info.date, USE new Date() INSTEAD
this.getField("Date").value = util.printd ("yyyymmdd", new Date());
// AND THIS LINE WILL GET THE CORRECT TIME AS DISPLAYED IN THE SIGNED CERTIFICATE. AS MENTIONED THIS WILL AVOID TIME ZONE SYNCHRONIZATION PROBLEMS IF YOU USE Info.date. USE new Date() INSTEAD
this.getField("TIME").value = util.printd("hh:MM:ss", new Date());
//AND SOMETHING LIKE THIS SHOULD GET THE EMAIL BUT I MAY BE WRONG
this.getField("EMAIL").value = Info.name.split(" <").join("<");
NOTE: These scripts should be executed as an action during signing time and only from the signature field. If you run these scripts independently on spearate text fields, keep in mind that you'll need to include a signature status validation to meet a condition. The signature security properties of a blank signature field are different before a signature is applied on it, it will change its status and also the properties of the signature field once the digital signature is applied and the document is saved.
Last, to resolve your other issue, about how the user will interact with the initial boxes, if you prefer to autopopulate the Initials text fields programatically, then you may want to consider an listening event with an on-click getAction method.
This would allow the user to click on the text fields to enter the initials but it will trigger the signature field. Signing the signature field will populate the initials text field.
The trick is how to make this work when the user have to initial more that one text field before signing; but this is just another idea that then you should consider implementing with the array methods as explained in Thom Parker's excellent tutorials.
AdChoices