Developer Section

Sample Data:

<OfflinePaperlessKyc referenceId="925020190122165455195">
<UidData>
<Poi dob="02-11-1995" e="076586c63449b7bd6be397...." gender="male" m="b6ecbb2c0f9b5678de8bce3bcd8155..." name="Madhu n"/>
<Poa country="#COUNTRY" dist="kozhikode" house="valanattu house update1" loc="malaparamba update1" pc="673009" po="malaparamba" state="32" street="malaparamba update1" subdist="005420" vtc="malaparamba"/>
<Pht>/9j/4AAQSkZJRgABAgAAAQABAAD.....</Pht>
</UidData>
<Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
<SignedInfo>
<CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/>
<SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
<Reference URI="">
<Transforms>
<Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
</Transforms>
<DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/>
<DigestValue>WYqBFc...</DigestValue>
</Reference>
</SignedInfo>
<SignatureValue>fUledlM0faNmeJiDrZc2/...</SignatureValue>
<KeyInfo>
<X509Data>
<X509SubjectName>CN=hcl-aua,OU=hcl-aua...</X509SubjectName>
<X509Certificate>MIIDjTCCAnWgAwIBAgIEYhPg...</X509Certificate>
</X509Data>
</KeyInfo>
</Signature>
</OfflinePaperlessKyc>

This can be verified by using the below public key

NOTE: This code is contributed by Geodesic team and is available on as-is basis. Sample C application to test Aadhaar authentication can be downloaded from here.

A sample C client with source code is provided to help the community rapidly develop applications that use Aadhaar authentication. This sample application is written in C for the GeoAmida device and it demonstrates various features of Aadhaar authentication. This application is provided on an "AS-IS" basis and should not be considered as a supported, production strength software. This chapter covers details about downloading and setting up development environment.

Setting up Development Environment

When you download the source distribution from the link above, you get "c-auth-client-source-1.5.zip". Please follow steps below to setup the client as a development environment. These directions are for Linux OS and ARM devices. If you are using Windows or other OS, you may make appropriate modification to the instructions below.

Unzip "c-auth-client-source-1.5.zip" into a directory. You should now see a directory named "c-auth-client-source-1.5" there

Navigate to "c-auth-client-source-1.5" directory. You should see the following listing.

Dependency Libraries:
libxml >= 2.7.6
openssl >= 0.9.8
Digital Signature Generation requires an additional libraries:
libXslt >= 1.1.24
libxmlsec1 >= 1.2.9

The below DEFINES values are need to modify before compiling:
LICENCE_KEY
UIDAI_PUBLIC_CERITIFICATE
AUA_PRIVATE_CERTIFICATE - Required for Digital Signature

Auth Xml API documentation is available under the doc folder

You may use any editor tool (Eclipse, emacs or vim) installed on your development machine and setup the environment variable, LD_LIBRARY_PATH in order to find libraries.

Within "Command Prompt", change directory ("cd") to "c-auth-client-source-1.5

Sample Makefile included in the build for Geoamida and gcc version.
CC = arm-xscale-linux-gnueabi-gcc

On a successful make, you should see the executable file AuthClient.

Run AuthClient. It will generate Auth-XML. During compilation if the "-D XML_SECURITY" flag is set, then the Digital Signature will be created along with Auth Xml.

As explained in previous chapter, sample Java client with source code is provided to help the community rapidly develop applications that use Aadhaar authentication. This application is written in Java and demonstrates various features of Aadhaar authentication. This application is provided on an "AS-IS" basis and should not be considered as a supported, production strength software. This chapter covers details about downloading and setting up development environment.

Sample Java application (both binary and source code zip files) to test Aadhaar authentication can be downloaded from here.

Setting up Development Environment

When you download the source distribution using downlink above, you get "auth-client-source-1.5.zip". Follow steps below to setup the client as a development environment. These directions are for Windows OS. If you are using Linux or other OS, you may make appropriate modification to the instructions below.

You need

Java 1.6.20 or above, Apache Maven 2.2.1 or above, and Eclipse Java IDE installed on your computerto setup environment based on this page.

You can use the source code and setup environment if you want it in other IDEs and build environments.

Unzip "auth-client-source-1.5.zip" into a directory. You should now see a directory named "auth-client-source-1.5" there

Navigate to "auth-client-source-1.5" directory. You should see the following listing.

Within "Command Prompt", change directory ("cd") to "auth-client-source-1.5"

Run "mvn eclipse:eclipse" command. If "Maven\bin" is not in path, please add it. Otherwise "mvn" command will not run.

You should see "Build Successful" message like below.

Launch Eclipse and create a new workspace (or use current workspace if you prefer)

Choose "File->Import" menu. This lanuches an import dialog.

Choose "Existing Projects into Workspace" option and click "Next"

Click "Browse" button next to "Select Root Directory"

Navigate to "auth-client-source-1.5" and select the directory

This will list 4 projects - "uidai-auth-client", "uidai-auth-xsd-model", "uidai-biometric-integration-api", and "uidai-sample-gui-app"

Make sure all projects are selected. See screen below.

Click "Finish" to import all 4 projects into workspace

If you have project that provides biometric integration API implementation, you will have to add it to the class path of the "uidai-sample-gui-app" project.Also, update the value of field, biometricAPIImplementationClass, in the SampleClientMainFrame.java to the value of the class that implements the API.

Select "SampleClientMainFrame.java" under project "uidai-sample-gui-app" (src/main/java/in/gov/uidai/auth/sampleapp folder) and choose "Run->Run COnfigurations" menu or click "Run" icon on toolbar and choose "Run COnfigurations".

Click "New Launch Configuration" icon on left top corner within the dialog. This created a new default run configuration for the sample application.

In order to use Indian name matching, it is required that the java apps run in UTF-8 character encoding mode. For that, in Java, following VM arguments has to be passed "-Dfile.encoding=UTF8". Within "Run Configurations" doalog, add this to VM arguments

Click "Run" button on the bottom right within the "Run Configuration" dialog to run the application. you should see the sample application GUI window.

Choose "Edit->Preferences" menu option and ensure you choose appropriate path for public key file and keystore file (they are available under "auth-client-source-1.5\uidai-auth-client\src\main\resources" folder. Ensure license key, AUA code, Sub AUA code are as listed under "Testing Data" page

Enter "999999990019" in "Aadhaar Number" field and "Shivshankar Choudhury" in the "Name" field. Additional data is available on "Testing Data" page.

Click "Authenticate" button at the bottom right

You should see a green tick mark within the "Authentication Status" field. See the following screen

If you have issues, first ensure you have followed all steps correctly. If you face network or connection errors, please make sure your Internet connection is working well. If test server (auth.uidai.gov.in) is down or not reachable, try after some time.

If nothing works (!), please write to the Discussion Forum Page

UIDAI has created a fully working sample Java client application to help the community rapidly develop applications that use Aadhaar authentication. This application is written in Java and demonstrates various features of Aadhaar authentication. This application is provided on an "AS-IS" basis and should not be considered as a supported, production strength software. This chapter covers details about downloading, installing, and running the sample and setting up development environment with the source code.

Sample Java application (both binary and source code zip files) to test Aadhaar authentication can be downloaded from here.

Running Sample from Distribution

When you download the binary distribution using downlink above, you get "auth-client-bin-1.5.zip". Follow steps below to install and run the client. These directions are for Windows OS. If you are using Linux or other OS, you may make appropriate modification to build and run the client.

You need Java 1.6 or above installed on your computer and an Internet connection to run this sample.

Unzip "auth-client-bin-1.5.zip" into a directory. You will see the following contents.

Run "runclient.bat" to run the sample application.

In order to use Indian name matching, it is required that the java apps run in UTF-8 character encoding mode. For that, in Java, following VM arguments has to be passed "-Dfile.encoding=UTF8". This is already added to the "runclient.bat" file.

This opens a command promt asking for OS type, enter 1 or 2 (based on your OS) and press ENTER.

This opens the sample authentication client. See screenshot below.

Click "Edit->Preferences" menu to make sure you see following screen with values. Ensure license key, AUA code, Sub AUA code are as listed under "Testing Data" page.

Now you are ready to test!!

Enter "999999990019" in "Aadhaar Number" field and "Shivshankar Choudhury" in the "Name" field. See "Testing Data" page for details on test data for testing various combinations.

Click "Authenticate" button at the bottom right

You should see a green tick mark within the "Authentication Status" field. See the following screen

If you have issues, first ensure you have followed all steps correctly. If you face network or connection errors, please make sure your Internet connection is working well. If test server (auth.uidai.gov.in) is down or not reachable, try after some time.

If nothing works (!), please write to the Discussion Forum Page.

This page provides guidelines for handling API errors within the application. While developing applications, AUAs need to decide how to handle the errors gracefully and provide resident/operator friendly messages. Simply showing the error on screen is not helpful. This document is an attempt to provide guidelines for doing better error handling.

Follwing table desribes API error codes, suggestion for how to handle it, possible message to user, and probable reasons for the error.

Any other information regarding errors, please contact auth support team of UIDAI at यह ईमेल पता spambots से संरक्षित किया जा रहा है. आप जावास्क्रिप्ट यह देखने के सक्षम होना चाहिए..

The URL format for integration and testing Aadhaar authentication service by the external entities:

http ://<host>/<ver>/<ac>/<uid[0]>/uid[1]>/<asalk>

Test URLs: (remember to append AUA code and first two digits of Aadhaar number)

• Auth URL - http://auth.uidai.gov.in/1.6//<1st-digit-of-uid>/<2nd-digit-of-uid>/
• e-KYC URL - http://developer.uidai.gov.in/kyc/1.0//<1st-digit-of-uid>/<2nd-digit-of-uid>/
• OTP URL - http://developer.uidai.gov.in/otp/1.6//<1st-digit-of-uid>/<2nd-digit-of-uid>/
• BFD URL - http://developer.uidai.gov.in/bfd/1.6//<1st-digit-of-uid>/<2nd-digit-of-uid>/

URLs for other API versions:

• Auth2.0 - http://developer.uidai.gov.in/authrd/2.0
• Auth2.5 - http://developer.uidai.gov.in/authserver/2.5
• otp 2.5 - http://developer.uidai.gov.in/uidotp/2.5
• KYC2.0 - http://developer.uidai.gov.in/kyc/2.0
• KYC2.5 - http://developer.uidai.gov.in/uidkyc/2.5

URLs for other API versions [NEW VERSION]:

• Auth 2.5 - https://developer.uidai.gov.in/authserver/2.5
• e-KYC 2.5 - https://developer.uidai.gov.in/uidkyc/kyc/2.5
• OTP 2.5 - https://developer.uidai.gov.in/uidotp/2.5

Test Codes:

• AUA Code ("ac" attribute) : "public"
• Sub-AUA Code ("sa" attribute) - "public"
• License Key ("lk" attribute) : You can use any of the following license keys given below. Binary distribution of sample client is shipped with the first one below.
  • AUA License Key: MOw-DpjjHGxPlnKDXZlGh72zoPoryq4q5K1AhJL58HKfsoeCklXadcw  - allows usage of PI, PA, PFA, BIO-FMR, BIO-FIR, BIO-IIR, OTP, PIN, Indian Language, e-KYC
  • ASA License Key: MGL5DLfGSNT6Eam2Gq_CtHARsi8HML0GpYH5tU_kg7XJ8YpkdtaL9TA
• BFD URL - http://developer.uidai.gov.in/bfd/1.6//<1st-digit-of-uid>/<2nd-digit-of-uid>/
• Public key certificate - See chapter on certificates remember to use Staging/Test certificate for testing and production certificate for production
• Keystore for digital signature for "public" AUA - You can request p12 file by writing to यह ईमेल पता spambots से संरक्षित किया जा रहा है. आप जावास्क्रिप्ट यह देखने के सक्षम होना चाहिए..

Following are the test UIDs and their demographic data. All of them have same bio record as given above. If you have your own Aadhaar number (real one) then you can use that to test too.

uid=999941057058
name=Shivshankar Choudhury
dob=13-05-1968
dobt=V
gender=M
phone=2810806979
email=यह ईमेल पता spambots से संरक्षित किया जा रहा है. आप जावास्क्रिप्ट यह देखने के सक्षम होना चाहिए.
street=12 Maulana Azad Marg
vtc=New Delhi
subdist=New Delhi
district=New Delhi
state=New delhi
pincode=110002

uid=999971658847
name=Kumar Agarwal
dob=04-05-1978
dobt=A
gender=M
phone=2314475929
email=यह ईमेल पता spambots से संरक्षित किया जा रहा है. आप जावास्क्रिप्ट यह देखने के सक्षम होना चाहिए.
building=IPP, IAP
landmark=Opp RSEB Window
street=5A Madhuban
locality=Veera Desai Road
vtc=Udaipur
district=Udaipur
state=Rajasthan
pincode=313001

uid=999933119405
name=Fatima Bedi
dob=30-07-1943
dobt=A
gender=F
phone=2837032088
email=यह ईमेल पता spambots से संरक्षित किया जा रहा है. आप जावास्क्रिप्ट यह देखने के सक्षम होना चाहिए.
building=K-3A Rampur Garden
vtc=Bareilly
district=Bareilly
state=Uttar Pradesh
pincode=243001

uid=999955183433
name=Rohit Pandey
dob=08-07-1985
dobt=A
gender=M
phone=2821096353
email=यह ईमेल पता spambots से संरक्षित किया जा रहा है. आप जावास्क्रिप्ट यह देखने के सक्षम होना चाहिए.
building=603/4 Vindyachal
street=7TH Road Raja Wadi
locality=Neelkanth Valley
poname=Ghatkopar (EAST)
vtc=Mumbai
district=Mumbai
state=Maharastra
pincode=243001

uid=999990501894
name=Anisha Jay Kapoor
gender=F
dob=01-01-1982
dobt=V
building=2B 203
street=14 Main Road
locality=Jayanagar
district=Bangalore
state=Karnataka
pincode=560036

Test UID Creation Process

If you want to make use of your own UIDs (for testing services like e-KYC), you can request for creation of a test UID by writing to यह ईमेल पता spambots से संरक्षित किया जा रहा है. आप जावास्क्रिप्ट यह देखने के सक्षम होना चाहिए. from your registered e-mail id (email id registered for the UID – which is mandatory). You should not request for a test UID for another person. Please send filled-in consent form duly signed by the applicant.

Test UID creation process is time consuming and you should provide minimum 20 days for the activity to get completed. Any follow ups after 20 days, should be done to the above mentioned mail id ONLY. Please note that, the test UIDs will be created at UIDAI's discretion and UIDAI reserves the rights to deny any such requests for any reasons which will not be disclosed to the requester

Aadhaar authentication requires the identity data of the resident within the XML (PID block) to be encrypted. AES-256 session key is encrypted using UIDAI's 2048- public key. This page contains all certificates available for the ecosystem.

Sample Java application (both binary and source code zip files) to test Aadhaar authentication can be downloaded from here.

Production Public Key Certificates

Note: Latest production public key certificate (for PID Encryption) will always be available under link: https://uidai.gov.in/images/authDoc/uidai_auth_prod.cer

UIDAI Digital Signature

For validating & signature in the UIDAI response xml , you are requested to make use of the signature public key attached below. (Not required if you are not validating signatures in API responses or using the trust root validation for validating the UIDAI response xml signature)

Offline e-KYC public key certificates

Please find the Public key certificate details for Validating the digital signature of Aadhaar Paperless Offline e-KYC and Secure QR Code.

Paperless Offline e-KYC

Secure QR Code

Staging/Testing Public Key Certificates

Note: Latest staging/testing public key certificate will always be available under link https://uidai.gov.in/images/uidai_auth_stage.cer

PreProduction Signature/Encryption Public Key Certificates

Please find the keys below for validating the Digital Signature of UIDAI response XML, and encrypting the PID block of request XML in PreProduction Environment.

Authentication Sample Client (Java) kk

This is a sample authentication client software which works with authentication API. This software has the capability to authenticate demographic fiels, OTP,and provision to plug-in biometric capture. This is written in Java and requires Java 1.6. Source code along with Maven build files and Eclipse project files are also provided.

This is designed purely as a test tool to reduce the development time taken by the AUAs and device vendors. This is released as source code and developers are free to download, modify, enhance, and use it. THIS IS NOT A SUPPORTED SOFTWARE.

---------------------------------------------------------------------------------------------
User manual - See "Aadhaar e-KYC Basics" book.
----------------------------------------------------------------------------------------------

e-KYC API version 1.0 Sample Client - Full Source Code - updated 08 Jan 2014

e-KYC API version 1.0 Sample Client - Full Binary - updated 08 Jan 2014 (NOTE: Also download Fop and Batik and extract the jar files to "jar" directory for printing to work)

e-KYC API version 2.0 Sample Client - Full Source Code - updated 22nd Sep 2016

e-KYC API version 2.0 Sample Client - Full Binary - updated 22nd Sep 2016

Schema Files for Various APIs

XSD and Protobuf files for Aadhaar Authentication APIs Version 1.6

Authentication Clients and Samples in other Languages

Authenticaion client written in C/C++ is made available to the community by Geodesic team for their GeoAmida device. Full source is hosted at their Github repository. Please note that this software is neither created nor maintained by UIDAI. Aadhaar community is thankful to Geodesic for contributing this as open source to the community.

Authenticaion client written in Python and related tools are made available to the community by Venkata Pingali from TCS Labs, Pune. Full source is hosted at this Github repository. In addition, Aadhaar-based login module for Django is available here. Please note that this software is neither created nor maintained by UIDAI. Aadhaar community is thankful to the author for contributing this as open source to the community.

Authentication Tools

Biometric data formats (FMR, FIR, IIR) testing tool checks if formats are valid ISO formats and as supported by Aadhaar Authentication. Developers can use this tool to test if the biometric record is proper before testing it online.

Biometric Format Test Tool - Binary and Source - Released on 9 Aug 2012

Bulk demographic authentication tool facilitates Demo Auth, accepting demographic data of the residents through various input modalities. THIS IS A SAMPLE TOOL demonstrating the features of demographic authentication. Both source and binary are provided below.

Binary setup and user manual - Binary - Released on 9 Oct 2013

Source code project - Source - Released on 9 Oct 2013

KYR+ Sample Application (NEW VERSION)

This is a sample reference implementation of KYR+ software which works with Aadhaar Enrolment Client 1.2.x versions. This software has the capability to configure fields and capture additional fields specific to registrars. This is built using Visual Studio 2008 using Windows forms and C#.

This is designed purely as a productivity tool to reduce the development time taken by the registrars on the KYR+ aspect. This is released as source code and registrars are free to download, modify, enhance, and use it. THIS IS NOT A SUPPORTED SOFTWARE.

KYR+ sample application (New Version) - Full source code - released 15 March, 2011.

KYR+ sample application (New Version) - Binary - released 15 March, 2011.

KYR+ sample application document (New Version) - User Manual - released 15 March, 2011

Decryption Test Utility (1024-bit)

This test decryptor utility is developed to assist Registrars in decrypting the Registrar Enrolment Packets before go-live. This utility works with packets that are encrypted with 1024-bit key (see below for 2048-bit key tool)This utility supports only PFX and PEM formats for private key files. The private key files must be password protected. This tool also supports USB Token with .Net PKCS11 APIs at location "C:\WINDOWS\system32\aetpkss1.dll".

For all the other cases, a modification in the source code of Decryptor Utility is necessary for execution the decryption. Full source code is available below for download.

This is designed purely as a test tool along with source code provided for initial testing. THIS IS NOT A SUPPORTED SOFTWARE.

Decryption utility binary - last updated 16 Nov, 2010. 

Decryption utility source code - last updated 16 Nov, 2010.

Decryption utility "read me" document - last updated 16 Nov, 2010

Decryption Test Utility (2048-bit key)

This test decryptor utility is developed to assist Registrars in decrypting the Registrar Enrolment Packets before go-live. This utility works with packets that are encrypted with 2048-bit key (see above for 1024-bit key tool). This utility supports only PFX and PEM formats for private key files. The private key files must be password protected. This tool also supports USB Token with .Net PKCS11 APIs at location "C:\WINDOWS\system32\aetpkss1.dll".

For all the other cases, a modification in the source code of Decryptor Utility is necessary for execution the decryption. Full source code is available below for download.

This is designed purely as a test tool along with source code provided for initial testing. THIS IS NOT A SUPPORTED SOFTWARE.

Decryption utility binary - last updated 31 Oct, 2011. 

Decryption utility source code - last updated 31 Oct, 2011.

Decryption utility "read me" document - last updated 31 Oct, 2011.

KYR+ Sample Application

(OLD VERSION, see below for new version links) This is a sample reference implementation of KYR+ software which works with Aadhaar Enrolment Client 1.1.x versions. This software has the capability to configure fields and capture additional fields specific to registrars. This software saves the captured data into an embedded database. This is built using Visual Studio 2008 using Windows forms and C#.

This is designed purely as a productivity tool to reduce the development time taken by the registrars on the KYR+ aspect. This is released as source code and registrars are free to download, modify, enhance, and use it. THIS IS NOT A SUPPORTED SOFTWARE.

KYR+ sample application (Old Version) - Full source code for version 3.0 - released 15 Sept, 2010.

KYR+ sample application document (Old Version) - Version 3.0 documentation - released 15 Sept, 2010

FI - Bank Response XML Encryption Certificate

The below certificate should be used for encrypting the response XML before placing them in SFTP INBOX of UIDAI.  

Welcome to UIDAI Aadhaar Authentication discussion group. This group is created to facilitate Aadhaar Authentication related technical and integration discussions. By joining this group you automatically agree to the terms and conditions (user agreement) of this group mentioned below. All developer related content can be obtained at Aadhaar Developer Portal.

Please request through Group home page for memberships 

User Agreement for Discussion Groups

The following disclaimer and terms of use apply generally to all postings to the Aadhaar Authentication Discussion Group and any other public discussion groups hosted by UIDAI. If you do not agree to any of these terms, please unsubscribe from this group.

All content, information and opinions (collectively, the "Material") presented on Aadhaar Authentication Discussion Group (the "Discussion Group") are those of the authors of posts and messages (collectively, the "participants") and not UIDAI's. UIDAI does not guarantee the reliability, completeness,accuracy, timeliness or up-to-date-ness of the material presented on the Discussion Group. The material is published "as is", and does not represent the official views and opinions of UIDAI. Any reliance upon the Material presented on these forums shall be at User's own risk. UIDAI does not review the substance of the content posted by users on these forums and is therefore not responsible for any of such content. UIDAI is not responsible for the privacy practices of any user. All information that is disclosed in these areas becomes public information and users should exercise caution when deciding to share any of their personal information. However, UIDAI is authorized by you to remove or modify any data submitted by you to these forums for any reason we feel constitutes a violation of our policies, whether stated, implied or not.

UIDAI has no control over the content and cannot ensure it will not be offensive or objectionable. We will, however, remove links to material that we feel is inappropriate as we become aware of them

NOTICE THAT

by submitting the post(s) on the Discussion Group the participant grants UIDAI the copyright of the material submitted. Any solicited or non-solicited idea, suggestion, or comment that is mentioned in this discussion forum becomes the intellectual property of UIDAI and might end up in one of it's products or services without credit or monetary consideration given to the originator of the idea

It is hereby also understood that any person posting to UIDAI will have been presented with this disclaimer and terms of use prior to doing so and, as such, be subject to its terms:

CONDITIONS OF USE:

You are entirely responsible and liable for all postings, information and submissions made by you to this discussion group. You also agree that you will not post any copyrighted material that is not owned by yourself or the owners of these forums. In your use of the forum, you agree that you will not post any information which is unlawful, harmful, threatening, abusive, harassing, defamatory, vulgar, obscene, harassing, threatening, invading of others privacy, hateful, racially, ethnically or otherwise objectionable or violates any laws. Listed below are some, though not all, violations which may result in UIDAI deleting your postings. You agree not to do any of the following actions while posting to UIDAI: (1) harass, threaten, embarrass or slander any person or entity; (2) transmit any information, data, text, files, links, software, chat, communication or other materials ("Content") that UIDAI considers to be unlawful, harmful, threatening, abusive, harassing, defamatory, vulgar, obscene, hateful, racially, ethnically or otherwise objectionable; (3) impersonate any business or person, living or dead, famous or not yet so; (4) disrupt the normal flow of dialogue in the Discussion Group or otherwise act in a manner that negatively affects other users; (5) post or transmit any unsolicited advertising, promotional materials, or any other forms of solicitation; and (6) intentionally or unintentionally violate any applicable local, state, national or international law, including but not limited to any regulations having the force of law while using or accessing this forum or in connection with your use of this forum in any manner

INTELLECTUAL PROPERTY

You agree that you will not upload or transmit any Content to UIDAI and discussion boards that infringes any patent, trademark, trade secret, copyright or other proprietary rights ("Rights") of any party. You alone are responsible that you indeed have the right to submit Content to UIDAI/Forums.

CONTENT

You must evaluate, and bear the risk associated with, the accuracy, completeness or usefulness of any Content. UIDAI shall not be responsible for any Content. UIDAI does not prescreen or monitor all Content as a matter of policy, but UIDAI shall have the right, but not the responsibility, to remove Content which is deemed in UIDAI's sole discretion harmful, offensive, or otherwise in violation of this Agreement, national or international legislation or any rules UIDAI has in place at the time. UIDAI may elect at its sole discretion to monitor some, all, or no areas of UIDAI for adherence to this Agreement or UIDAI's rules. This email may contain virus or malware. You are advised to take necessary protection before reading, clicking any links, or opening any attachments.

WHAT TO DO

If you witness a posting that violates these terms, please report to administrators of this group or to UIDAI. UIDAI cannot guarantee that any action will be taken as a result of your email