 |
||
 |
||
| Verification can be done by | ||
|
||
|
|
Viewing the authentic signed document at the State Data Center by keying in ton the GoK website, the unique certificate ID. |
|
|
|
Using a barcode reader to read the 2-D bar code printed at the bottom of the certificate. This method shows the corresponding record on the Nemmadi website and also tells whether the signature on the certificate are of valid authority. However the user needs to compare te contents displayed on computer (of the authentic document stored on SDC) with the content on the print out.. |
|
|
Keying in the certificate details in a freely downloadable utility available on Nemmadi website and then comparing the digest of the keyed in certificate content with hash stored on digital signature. |
|
|
Getting the certificate verified through a Verifying Authority duly appointed by GoK. |
|
Certificate Verification
The RDS Certificates are signatureless documents. The certificate is printed on a uniquely numbered and water marked paper supplied by Government of Karnataka and also carries a uniquely numbered hologram. The signed hash of the certificate contents is printed as machine readable 2D barcode at the bottom of the certificate. Each certificate also carries 2 seal impressions and the signature of the Nemmadi operator in accordance with the provisions of IT Act 2000.
The genuineness of these certificates can be verified conclusively by any person or authority as follows:
1. Verify by Request ID:
Connect to http://nemmadi.karnataka.gov.in/certificateverification. Key in the unique Request ID printed on the certificate. This method shows the corresponding record on the Nemmadi website. However the user needs to compare the contents displayed on computer (of the authentic document stored on SDC) with the content on the print out. This procedure does not require a 2D barcode and therefore also does not tell who has digitally signed the contents of the document. It allows one to compare the authentic document on the government website with the contents on the print out. Click here to proceed.
2. Verify by BarCode:
Connect to http://nemmadi.karnataka.gov.in/certificateverification. Use a barcode reader to read the 2-D bar code printed at the bottom of the certificate. The verification process would show the corresponding record on the Nemmadi website and also tell whether the signature on the certificate are of valid authority. However the user needs to compare the contents displayed on computer (of the authentic document stored on SDC) with the contents on the certificate hardcopy. This method requires a computer, an internet connection and a 2D bar code reader. Click here to proceed.
3. Fully Independent Verification
(requires a computer and a 2D barcode reader)
This method does not require an internet connection for certificate verification. It also does not have dependence on the content on government website. The verifier can verify the certificate by just using the data printed on the certificate. This is a little involved process but is rugged of all the three processes. The user needs to download and install a verification utility custom developed for Nemmadi, from Nemmadi website. The user also needs to download the public key of the authorised taluka official. Pre-requites for executing verification application are .Net framework 1.1 and two COM components namely CAPICOM.dll and Cryptolib.dll.
Stepwise procedure to download and install the verification utility and supporting tools given as follows:
1. Download .Net Framework 1.1 by clicking on following link (Next version of the utility shall not have this dependency) http://www.microsoft.com/downloads/details.aspx?FamilyID=262D25E3-F589-4842-8157-034D1E7CF3A3&displaylang=en
A executable file named dotnetfx.exe can be download from above mentioned url
2. Double click on the downloaded executable to install .Net framework 1.1
3. Download verification application from this website. Filenames to be downloaded for different applications are as follows:
|
|||
|
|
||
|
|||
|
|
||
This download zip file will have
i) MSI file for installing application for the selected service
ii) CAPICOM.dll
iii) Cryptolib.dll
iv) Chain.p7b (certificate chain, both CCA and NICCA certificates)
These files should be unzipped in c: (root folder) as it will be easy for the user to give the path of these files in the next step.
Procedure for installation
A. Register the following dlls
(Go to command prompt and type regsvr32 <<actual path of the dll>> )
CAPICOM.dll
Cryptolib.dll
Please note that if the files have been saved as above then the command will be:
regsvr32 c:CAPICOM.dll
regsvr32 c:CryptoLib.dll
B. Install CCA and NICCA certificate using right click-install on file chain.p7b. This can also be downloaded from NICCA website by clicking on following link
Download certificates of the taluka for which you want to verify by clicking on the taluka from the list of talukas given under the link public keys in this website or by clicking here. These certificates are required for the purpose of verification. Installation of these certificates can also be done by right click – install procedure used in case of chain.p7b.
While only one certificate shall finally be used by the verification utility as any document is signed obviously by a person, all certificates are needed to be used because of two reasons:
1. There are different authorities each having their own key for signing.
2. As and when authorities get transferred, new authorities are given new keys for signing.
D. Install verification application by clicking on downloaded msi file and following the on screen instructions.
Procedure for installation
|
||
 |
Double click on the shortcut to installed verification utility on desktop to open the verification screen. By default, the shortcut shall be named after the corresponding certificate and created automatically on the desktop. |
|
|
Enter the particulars in the verification screen from the certificate. Particulars have to be entered only where the fields are empty. |
|
|
Click on “Generate XML” button to generate an xml file. |
|
|
||
|
The Application will give “XML Generated” message. If generated document is validated against XSD created by government for that document it will give “The document is valid” message. |
|
|
||
|
If data entry in any of the fields is not in proper format, the application shall give the message “The <field name> element is not as per its datatype”. |
|
|
||
|
Then the corresponding field should be reentered and again click the “Generate XML” button. |
|
|
||
|
Data in various empty fields of verification form should be typed EXACTLY as seen in the certificate. |
|
|
||
|
After you get the proper format message, read the bar code from the certificate using the 2D bar code reader. Ensure that Caps Lock is off when you are reading from the bar code. | |
|
||
|
Click on “Verify” button to verify the certificate. | |
|
||
|
If certificate is verified successfully, application will give a message “Certificate is verified………Found OK………..” If it is incorrect the message will be “Certificate is verified……Found Wrong………” The verified message guarantees three things: 1. The document was signed by the competent authority 2.The contents as shown on the document have not been tampered. 3. The issuing authority cannot disown the content of the document. |
|
|
||
|
Application may give “Found Wrong message” due to following reasons also | |
|
||
|
Required public key not available. 2. Contents of the certificates not typed properly. (XML data is case sensitive, spaces and special characters has to typed exactly as it is printed in the certificate) 3. The document has been tampered by somebody. 4. Document has not been generated by the Nemmadi system but fabricated outside the system. |
|
|
||
|
Click on the “End” button to end the application. | |
Our Project Partners : |
|
 |
|