1 DigiLocker Technology Specification DLTS Version 2.3 Abstract This document offers a standardized mechanism to issue government documents to Aadhaar holders in electronic and printable formats, store them, and make it shareable with various agencies. This allows government issued documents to be moved to electronic form and make it available for real-time access in a set of digital repositories. This solution also offers multiple DigiLocker providers and access gateways to co-exist to enable healthy ecosystem play. Usage of Aadhaar ensures that document owner is strongly authenticable eliminating document frauds. In addition to supporting new documents to be made electronic and online accessible, this solution also offers a way to digitize older documents. Proposal also offers a mechanism by which DigiLockers can be offered by service providers and suggestion to provide a default DigiLocker portal and mobile application to residents to view a consolidated list of documents using their Aadhaar number. Introduction Currently, in India, almost all of the government issued documents are in physical form across the country. This means every time a resident needs to share the document with an agency to avail any service, an attested photo copy either in physical form or on scanned form is shared. Use of physical copies of document creates huge overhead in terms of manual verification, paper storage, manual audits, etc. incurring high cost and inconvenience. This creates problem for various agencies to verify the authenticity of these documents, thus, creating loopholes for usage of fake documents/certificates. Due to the nature of these documents not having a strong identity attached to it, anyone with same name can indeed misuse someone else s document. Digital India Vision The Digital )ndia programme cleared by the cabinet in August 4 seeks to prepare India for a knowledge future. There are three key objectives; a to create a digital infrastructure for online digital identity, mobile phone and a bank account, (b) to service and govern a real-time online financial transaction platform, and (c) to digitize all documents and records of the residents and make them available on a real-time basis. This vision of electronic resident document system should address two key aspects:
2 Minimizing usage of physical documents (no scan/photocopies, no physical papers) via electronic formats and sharing across agencies; and Eliminating usage of fake documents (no fake govt/degree certificates, no fake usage of someone else s certificate via a mechanism to verify authenticity of government issued documents online. Provide a default DigiLocker for people to store and access Government issued documents in the Government cloud if they wish to subscribe. Solution Objectives Objectives of such digital repository solution are: Eliminate need for the residents to maintain hard copy of government issued documents. Eliminate need for the residents to produce (in hard format) government issued documents, while applying for services. Provide secure and consented access of government issued documents to user agencies. Reduce administrative burden, service fulfillment time, and costs by enabling paperless transactions. Ensure all the documents issued to the residents are available to him/her anywhere anytime, in a standard format which can be shared with any other department. Provide an open, interoperable, multi-provider architecture to ensure departments and states have flexibility to use best document repository for their purposes. Provide an architecture that can support well structured future documents as well as a mechanism to digitize older documents that may not have machine readable formats. Provide a default portal and mobile application for residents to view their documents in a consolidated way. Characteristics of Electronic Documents To meet the key goals and the solution objectives, architecture should ensure that all government issued electronic documents stored in digital repositories are: Machine Readable documents in electronic format should be machine readable eliminating human workflow for viewing and verifying the documents. Document structure should adhere to common XML structure for application usage and interoperability. Documents should have a common set of meta attributes such as issuer agency code, document )D, issue date, Aadhaar number s of the individuals to who the document is issued to, expiry if any along with document type (domain) specific sub data structure (e.g. school
3 certificates will have different data elements compared to marriage/caste certificates). Printable all electronic documents should have a printable format attached to it allowing continued printing of certificates for individuals and for backward compatibility with existing paper based systems. Shareable residents can easily share the documents with other agencies/departments just by proving the unique document URI without having to share photocopies, scan copies, document uploads, etc. Since all one needs is a small URI, such sharing can easily be done even on feature phones even via SMS and text based systems. Tamper Evident documents in electronic form should be digitally signed by the issuing department/agency which allows any tampering to be detected electronically. This also allows agencies to be compliant to IT Act. Verifiable most importantly, government documents and certificates issued can be verified online for authenticity validating if the document shared by an individual indeed was issued by appropriate authority) eliminating the use of fake documents/certificates. In addition, Aadhaar attached documents/certificates ensure ONLY the owner Aadhaar holder can indeed use the certificate, thus eliminating misuse of someone else s certificates. Secure it is critical that documents in the repositories are secure in terms of storage and access. In addition, specific documents (based on type of document) may only be shareable via owner authentication to ensure sharing and access is authorized by the document owner. It is highly recommended that government issued resident documents have the Aadhaar number(s) of the people. When digital documents/certificates are not attached to Aadhaar, it is important to note that, while those documents can be still made available online in electronic format, it can potentially be misused by another person who has same name/gender etc. It is impossible to verify if the certificate/document was issued to same individual without affixing a real identity using Aadhaar number. (ence it is important to mandate use of Aadhaar number in all resident documents to strongly assert ownership. Assumptions Considering states and various departments, solution should provide a scheme for multiple repositories to co-exist and interoperate seamlessly. This also avoids a design requiring a single central database for all across the country. Resident documents in electronic formats are stored in federated fashion (no centralized single document repository). Designated set of central repositories would be part of the system (e.g. central repositories dedicated to universities and educational institutions, a dedicated repository for health centres, etc). Each agency responsible for issuing documents/certificates in electronic form and storing them in a designated repository.
4 Departments/agencies should be able to digitize older existing documents and bring them into this common electronic document system and provide seamless access. All documents in electronic formats must be digitally signed by the issuing department/agency to be trustable by other agencies and be compliant with )T Act. In future, all documents must be issued to an Aadhaar holder to ensure ONLY that person can indeed claim ownership. If a strong identity is not attached, a government document may be misused by people with same demographics (name/age/gender). All future electronic documents are available in both machine readable and printable formats. Old documents that are digitized may or may not a corresponding machine readable form. This allows departments to easily start digitizing documents and gradually adopt a fully electronic form. Proposed Architecture This section covers solution architecture in detail including terminology used, high level architecture diagram, document identification scheme, document issuance lifecycle, document sharing scheme, and some examples. Key Terminology Electronic Document or E-Document A digitally signed electronic document in XML format issued to one or more individuals (Aadhaar holders) in appropriate format compliant to DLTS specifications. Examples: Degree certificate issued to a student by a university. Cast certificate issued to an individual by a state government department. Marriage certificate issued to two individuals by a state government department. Digital Repository A software application complying with DLTS specifications, hosting a collection (database) of e-documents and exposing a standard API for secure real-time access. While architecture does not restrict the number of repository providers, it is recommended that few highly available and resilient repositories be setup and encourage everyone to use that instead of having lots of repositories. DigiLocker- A dedicated storage space assigned to each resident, to store authenticated documents. The DigiLocker would be accessible via web portal or mobile application. Issuer An entity/organization/department issuing e-documents to individuals in DLTS compliant format and making them electronically available within a repository of their choice.
5 Requester An entity/organization/department requesting secure access to a particular e-document stored within a repository. Examples: A university wanting to access 10 th standard certificate for admissions A government department wanting to access BPL certificate Passport department wanting to access marriage certificate Access Gateway A software application complying with DLTS specifications providing an online mechanism for requesters to access an e-document in a uniform way from various repositories in real-time. Gateway services can be offered by repository providers themselves. While architecture does not restrict the number of repository providers, it is suggested that few resilient and highly available central gateway systems be setup and requesters can signup with any one of the gateways for accessing documents in the Digital repositories. Document URI A unique document URI mandatory for every document. This unique URI can be resolved to a full URL to access the actual document in appropriate repository. Document URI is a persistent, location independent, repository independent, issuer independent representation of the ID of the document. The existence of such a URI does not imply availability of the identified resource, but such URIs are required to remain globally unique and persistent, even when the resource ceases to exist or becomes unavailable. While document URI itself is not a secret, access to the actual document is secure and authenticated. Proposed Architecture at High Level In the diagram below, top side represents the issuance part and bottom side represents the real-time access part.
6 Diagram depicts the federated model of document storage via designated dedicated digital repositories. It also depicts the co-existence of highly available document access gateway(s) (one or two) that can be used to access these documents stored in these repositories. )ndividuals Aadhaar holders may be provided a default DigiLocker mechanism to directly access the repository via secure access scheme and viewing a consolidated list of URIs in their inbox. Core features of the architecture: Digital certified repositories and gateway providers Government provided or 3 rd party provided) using an interoperable DLTS compliant standard for scalability and to avoid one single central registry. Storage and access using unique document URIs and by Aadhaar numbers (access using a document URI points to one e-document while access via Aadhaar number can point to multiple e-documents issued to him/her). All access via auditable and non-repudiable mechanism (API access control to ensure no public anonymous access is allowed Access via document URI may or may not require Aadhaar holder authentication depending on the document type (some doc types may mandate Aadhaar authentication before every access while publicly available documents may not).
7 Access via Aadhaar number must ALWAYS be after authentication to ensure access is authenticated and authorized by owner (Aadhaar holder). Issuers can issue new e-documents in DLTS compliant format completely independently of each other issuers at their own pace. Issuers can also choose to digitize older documents without having a machine readable representation and allow a verifiable and secure access to older (legacy) documents. They can focus on new documents in DLTS compliant format while progressively providing digitization of older (existing) documents. Residents can also choose to convert their existing certificates using self signed or notary signed mechanism and store them in a DigiLocker. Acceptance of such documents will depend on the requester rules. Issuers can provide a printed copy of the document to the individual after storing them in their repository making it verifiable, shareable, accessible, and reprintable. Issuers can choose their own print formats and styles as they do today. Issuers can use their own document numbering scheme and introduce new scheme for new documents without having to stick with one numbering scheme for ever. Issuer can choose one of the designated repository provider for all their documents or choose separate repository providers for different document types. States can choose to use a common repository provider or build their own. Residents can share the document with other agencies/departments (e.g., sharing CBSE mark sheet with a university) just by sharing the document URI printed on their certificate instead of providing a photocopy or scanned copy. Sharing via simple URI allows document sharing via mobile, SMS, website, etc easily. Whenever owner authentication is required, Aadhaar authentication (OTP or biometrics) can be used to authenticate every access. Requesters can dynamically obtain the list of document types defined by issuers by querying the metadata of the repository allowing issuers to add new document types dynamically. Requesters to use highly available gateway system to access URIs of the required document. The requesters would get temporary access to the documents directly from the repositories for download. DLTS solution uses open standards and multi-provider ecosystem strategy. Both government and private players could play the role of repository and gateway providers so that issuers and requesters get the best choice that fits their needs. Solution addresses all core objectives as described earlier in this document while keeping entire system open via common standards. It is important to note that interface between Repository, Gateway, and DigiLocker MUST BE via DLTS APIs only to ensure these are loosely coupled. This loose coupling allows providers to refactor, scale, administer, price, etc independent of each other. If a provider offers both repository and gateway features, it must be
8 ensured that users (Issuers and Requesters) can sign up for individual services instead of bundling everything into a monolithic offering. Unique Document URI Every document that is issued and made accessible via DLTS system must have a unique way to resolve to the correct repository without conflict. This is critical to eliminate the need for all documents reference to be in one system. Federated repositories storing documents issued by various departments/agencies must be reachable via the gateway in a unique fashion. All documents issued in compliance to DLTS should have the following URI format: IssuerId-DocType-DocId where IssuerId is a unique issuer entity ID across the country DocType is the document type optionally defined by the issuer DocId is a unique document ID within the issuer system Issuer ID (mandatory) All departments/agencies within government issuing resident documents, termed as Issuers must have a unique identification to ensure all documents issued by them are accessible via DLTS gateway. It is recommended that list of unique issuer codes be derived via their domain URL whenever available and be published as part of e-governance standard codification scheme with ability to add new issuers on need basis. When URL is not available for a department, a unique (alpha) code may be assigned. Examples of issuer )ds are maharashtra.gov.in Maharashtra State Government, kseeb.kar.nic.in Karnataka School Board, cbse.nic.in CBSE School Board, UDEL (Delhi University), etc. These codes MUST BE unique across India and published as part of standard e-governance codification list. Document Type (optional) Issuers can freely define a list of document types for their internal classification. For example, CBSE may classify certificates into MSTN (10 th mark sheet, KVPY (certificate issued to KVPY scholarship fellows), etc. There are no requirements for publishing these via any central registry. Classifying documents into various types allows issuers to choose different repositories for different types. This is to future proof the design without making assumption that all certificates issued by the issuer are available in same repository. This also allows migration from one repository to another in a gradual way. Issuers are free to define their document types without worrying any collaboration across other issuers. Keeping
9 the length minimal allows manual entry of document URI without making it too long. Hence it is recommended to keep length to be only up to 5. It is recommended that issuers define document types either using pure alpha case-insensitive strings of length up to 5. These document types MUST BE unique WITHIN the issuer system. This classification within the issuer system also allows versioning of documents making future documents to be of different formats and in different repositories without having the need to have all documents in one repository. If need arises in future to go beyond length 5, maximum length of doc type can easily use increased without breaking compatibility any existing systems and documents. Document ID (mandatory) A document ID determined by the department/agency (issuer) should be assigned to every document. It MUST BE unique either within the document types of that issuer or it can be unique across all document types of that issuer. Document ID is an alpha-numeric string with maximum length of 10. It is recommended that issuers define document IDs either using pure alpha caseinsensitive string using a RANDOM number/string generator. Document IDs MUST BE unique WITHIN the issuer system within a document type. If need arises in future to go beyond length 10, maximum length of doc ID can easily use increased without breaking compatibility any existing systems and documents. Using random string eliminates the possibility of guessing next sequence number and accessing a list of documents in a sequential way. This is critical to ensure security of documents and ensures document can be accessed ONLY )F the requester knows the actual document ID (instead of guessing sequential numbers). It is highly recommended that issuer needing to issue a total of n documents within a document type use at least 10n random space from which the strings/numbers are chosen to randomly allocate. Notice that since document types allow further classification, it is suggested to keep the length minimal. Since issuers can easily add a new document type without any collaboration and approvals across other issuers, if more numbers are required, a new document type may be introduced. Examples Following are few examples of document URI printed on the document using QR code and a human readable string.
10 CBSE-MSTN KARMR-MCA DLSSB-HSMS-GJSGEJXS Document Issuance Flow Document issuance flow is given below: Create a new digitally signed e-document complying to DLTS specification with a unique URI and an attached optional printable version. Issuer entity uses the unique code for itself (obtain a new one if not already listed) that is available in common DLTS Issuer Codification e- governance standards. This is a country wide Unique )ssuer )D. Document type codification and ID numbering is left to the freedom of issuer. Doc types are issuer specific and need not be unique across issuers. If a new type is required, they should simply register the new type in the repository and start using them. Issuer should have tied up with a repository provider for storing documents and making it available online. Store the new e-document in the repository. There are two ways to add a new document to a repository: via add AP) allowing online live addition of new documents (programmatic) via web portal of the repository provider in a manual fashion human interface) Issue the printed document to the individual(s) for whom the document is issued to with a barcode and human readable document URI. In addition to printed document, issuer may also share the e-document via or other offline sharing schemes. Issuer should also offer an option to people to push the document URI with or without attachment (e-document) via SMTP to their DigiLocker address. Every document issued must have this unique document URI in the format issuerid-doctype-docid printed human readable along with a barcode machine readable, using QR code. Older documents being digitized should be defined under published list of document types so that just by using document ID, corresponding URI can be dynamically formed and document accessed from its repository.
11 Document Sharing and Access Flow Residents wanting to share their documents to requester agencies will have the following flow: Requester (department/agency wanting access to an e-document of their customer) asks the resident to provide the e-document URI There are three ways to share: Share the document URI (since this is simply a text string, this can be collected easily) along with Aadhaar number. Requesters can pull the document via their gateway. For older documents with just document ID (no full DLTS formatted URI), requester can ask the user to choose the issuer and document types from a list, collect document ID, and then internally form URI. Or if it is a legacy self-signed document stored in DigiLocker, share the self-signed document access URL. Or send/upload the copy of the e-document to requester s application directly (when requester has no gateway or DigiLocker access) For e-documents stored in repositories, requester can access them using the URI and access credentials via a gateway. For accessing self-signed, scanned documents in DigiLocker, requesters can use DigiLocker share schemes. Requester uses one of the gateway providers to access documents stored across federated DLTS repositories. Requester uses DLTS Gateway API to access the document based on the URI. Note that some document types of some of the issuers may require online user authentication (via Aadhaar or Aadhaar enabled authentication provider such as e-pramaan). This is based on Issuer rules. If the document type requires document owner authentication, appropriate authentication credentials (biometric/otp/password, etc) also must also be captured. Gateway system looks up its internal database and maps the URI to an actual repository URL and forwards the request to the appropriate repository. If authentication credentials are also sent by the requester, gateway system must do online authentication and only on successful authentication, request can be forwarded to repository. Gateway forms the URL and sends the request to repository based on the DLTS Repository API along with authentication success response. Repository provider returns the digitally signed XML document after gateway authentication. Repository provider must validate credentials of gateway (API license key, digital signature, etc) Repository provider must validate if the Aadhaar number of the input and what s inside the document are matching.
12 If the document type requires authenticated access, before returning the document, it must verify the authentication response provided by the gateway. E-Document returned by the repository goes back to requester via gateway. For large printable documents, a temporary printable URL can be provided so that requester can directly download from repository without going via gateway (this must be one time download URL that expires). Gateway MUST not store URI, e-document, and other authentication credentials as is. It MUST ONLY be used for transient access. Anonimized audit must be stored. Requester uses the e-document for its purposes and provides the intended service to the resident. Repository provider publishes access audit via public URL for transparency and notification subscription. National DigiLocker Directory, Portal/Mobile Application and Dashboard DeitY, as the DigiLocker nodal agency would include an DigiLocker directory (providing details on Issuer ID, requestor ID, Gateway ID, etc.) on the national DigiLocker portal. The portal would also provide all Standards published via electronic documents for public access. Following key features must be incorporated within this DigiLocker Directory: Provide public access to view the list of Issuers (name, ID, registration date), empanelled repositories (name, URL, date of empanelment, contact details), gateways (name, URL, date of empanelment, contact details), etc. Provide repository and gateway empanelment guidelines, application form, and other details. Provide link to request Issuer ID this application must allow new issuers to request a unique ID. This should be a simple electronic workflow to request, approve, and publish new ID. The DigiLocker directory will play a critical role in ensuring that the e-documents repositories which are under consideration for on boarding follow a defined work flow to ensure eligibility prior to becoming certified repositories and are listed on the directory. The DigiLocker Directory will serve as a single window for discovery/browsing of various e- Documents repositories, issuers, requesters, gateways, and document types. DigiLocker Interface
13 To provide a central view (inbox of sort) of all his/her documents and storing selfsigned legacy documents, it is recommended that this DigiLocker feature is added via the National DigiLocker portal along with a mobile application. DigiLocker may provide the following features: Ability for residents to register for DigiLocker service with optional Aadhaar verification. Also, a mechanism to opt-out or de-register should be provided if residents do not want to the DigiLocker. Ability to download a copy of the e-document from appropriate repository to this DigiLocker by providing URI for backup and portability. Ability to upload a self-signed or notary signed legacy certificate/document into the DigiLocker. A limited storage may be provided for storing such legacy documents. A mechanism to manage (tags them, delete them, etc) will have to be provided for completeness. Additional features such as share either UR) or e-document) can be added as a value-added feature. This feature can allow residents to share with departments/agencies who may not have full provisions to automatically access via gateways. This feature also allows legacy documents to be shared. Features such as document sets can be created and shared like shared folder) Sharing can be one time (via unique secure URL) or using push authentication via mobile application, OTP, etc). Sharing can be at document or document sets level. Authentication, auditing, etc should be built-in to ensure security of the DigiLocker. DigiLocker must provide a mechanism to subscribe to access notifications if any entity accesses a document within a repository, DigiLocker software can pull the anonymized audit and provide a notification scheme). Ability to request )ssuers to push document copy or just UR) to resident s DigiLocker ID (e.g., via SMTP protocol. Security & Privacy Aspects Document Security Proposed solution avoids all e-documents to be stored in one central repository to minimize the risk of security and availability. Since documents are mandatorily digitally signed, NO alteration can be done for misuse. It is ONLY the privacy aspect of the document that needs to be addressed. Access Security
14 Repository and gateway providers must comply with DLTS security and API specifications. While some document types may be available to trusted requesters without electronic authentication and authorization of the owner (a simple consent may suffice), some document types may mandatorily require explicit electronic authentication and authorization of the document owner for every access. Access to repositories is only protected by API license keys, secure transport, and access level audits. If explicit authentication is required for a particular document type, a trusted authentication of the owner is mandated during access. Architecture allows owner authentication via Aadhaar or other Aadhaar enabled trusted authentication schemes (e.g., e-pramaan). Gateway provider MUST NOT store the document URI, e-document, authentication credentials, etc. Mandatory audit logs must be maintained both by gateway and repository providers. Repository provider MUST publish anonymized access logs in public for transparency as well as notification subscriptions by the document owners. DLTS Detail Specifications This section describes technical specifications for each of the aspect of DLTS solution including repository and gateway provider specifications at a high level. NOTE: Following high level specifications must be expanded and completed before actual implementation of the whole system. E-Document Specifications Document URI All documents issued in compliance to DLTS should have the following URI format: <IssuerId>[-DocType]-<DocId> Where, IssuerId (mandatory) - is a unique issuer entity ID. This is a unique pure alpaha case-insensitive string. To easily make it unique, department s domain URL can be used whenever available. The list of issuer Ids must be published and should have a mechanism to add new ones as required. Unique list of Issuer IDs MUST BE unique and published via central e-governance codification scheme.
15 DocType (optional) - is the document type optionally defined by the issuer. This is highly recommended for document classification and versioning purposes. Issuers may decide their own classification mechanism. This is a 5 char pure alpha string which can be expanced in future as needed. DocId (mandatory) - is a unique document ID of length up to 10 within the issuer system. It is highly recommended that this is either purely numeric or alpha to avoid confusion with with o etc. Also, it is highly recommended to use random strings to avoid guessing the sequence of document IDs. Document Owner For avoiding document misuse, it is critical that all documents are attached to one or more Aadhaar holders. For example, a cast certificate may be attached to one Aadhaar holder while a marriage certificate is attached to two Aadhaar holders. Proposed DLTS solution offers a mechanism for issuers to secure access via Aadhaar authentication of any of the owners. Document Format All e-documents must be represented in XML format complying to DLTS specifications. This ensures that a standardized XML structure is used to capture common attributes of all documents. All e-documents MUST BE digitally signed by the issuer to ensure documents/certificates are verifiable for authenticity and are unalterable. It is important to note that issuer specific extensions are allowed to this XML for representation of the actual document data. For example, actual details of a cast certificate will be different from actual details of a driver s license. DLTS allows this to ensure that issuers can choose a domain specific XML for their extensions. It is also important to note that DLTS solution does not insist on a common printing format allowing issuers to freely choose a print format for their document. Use of logo, colors, etc are freely possible within the print format. Following is the suggested common XML format for e-document (note that issuer specific extensions are embedded witin DocBody element). <Edoc ver= xsd= > <Meta issuerid= doctype= docid= issuedon= expireson= > <Owners>
16 <Aadhaar uid= name= /> </Owners> <Print format= highresurl= lowresurl= /> </Meta> <DocBody> <!-- any custom issuer specific XML can be embedded here --> <!-- Describes other elements and attributes of this particular doc --> </DocBody> <Signature/> <Edoc> E-document Examples A sample marriage certificate is given below. Note that the DocBody which is specific to marriage certificate format is left to issuer to standardize. While it is a good idea to standardize specific types of document and their formats, issuers must be allowed to change and adapt as they wish to provide flexibility and easy adoption. <Edoc ver= 1.0 xsd= > <Meta issuerid= KARMR doctype= MCA docid= issuedon= expireson= > <Owners> <Aadhaar uid= name= Kishan Singh /> <Aadhaar uid= name= Laxmi Agarwal /> </Owners> <Print format= image/jpeg url= /print/bc1f48e586a66eefbdfe96b b21c6c4f93654e5b39f0c1c6e3edb6d17 > </Meta> <DocBody> <Mca ver= 1.0 xsd= > <Marriage date= state= Karnataka district= Bangalore address= 32, 10 th Main, 14 th Cross, Bangalore, > <authority name= Bangalore Marriage Registrar officer= Ramesh Pai witness= Bunty Singh /> </Marriage> </Mca> </DocBody> <Signature/> <Edoc> A sample school leaving certificate is given below. Note that the DocBody of this is very different from the marriage certificate example above. <Edoc ver= 1.0 xsd= > <Meta issuerid= CBSE doctype= MSTN docid= issuedon= expireson= > <Owners> <Aadhaar uid= name= John Alex K /> </Owners> <Print format= application/pdf url= /print/ ef77ea d6b7059a15568ec601e9d409f05a3235e c115097d5 > </Meta> <DocBody> <Mstn ver= 1.0 xsd= > <Marksheet date= school= Tilak Nagar Public School class= 10 > <Official officer= Neela Lal schoolhead= Teressa Mathew /> <Mark>
17 <Subject name= Science mark= 92 max= 100 grade= A+ /> <Subject name= Mathematics mark= 96 max= 100 grade= A+ /> <Subject name= English mark= 91 max= 100 grade= A+ /> <Subject name= Hindi mark= 86 max= 100 grade= A /> <Subject name= Social Studies mark= 83 max= 100 grade= A /> </Mark> </Marriage> </Mca> </DocBody> <Signature/> <Edoc> Repository & Gateway Specifications A detailed API and compliance specifications must be prepared before actual start of implementation. At a high level following items need to be covered in that detail specification document: Repository APIs Document management APIs - adddoc, deletedoc, updatedoc, readdoc Meta data APIs getdoctypes Gateway APIs Document management readdoc Meta data APIs getissuers, getdoctypes, adddoctype, deletedoctype, updatedoctype Compliance Security document storage, issuer access control, gateway access control, validations, etc. Audits access and document management audits
Digital Locker Technology Specification (DLTS) Version 2.3, March 2015 Abstract This document offers a standardized mechanism to issue government documents to Aadhaar holders in electronic and printable
esign FAQ 1. What is the online esign Electronic Signature Service? esign Electronic Signature Service is an innovative initiative for allowing easy, efficient, and secure signing of electronic documents
esign Online Digital Signature Service Government of India Ministry of Communications and Information Technology Department of Electronics and Information Technology Controller of Certifying Authorities
DigiLocker User Manual (https://digitallocker.gov.in) Department of Electronics and Information Technology (DeitY) 1 of 18 1 Introduction Digital Locker, one of the key initiatives under the Digital India
e-sign An Online Electronic Signature Service Dr. Mohammed Misbahuddin Centre for Development of Advanced Computing (C-DAC) Bangalore Under the Aegis of Controller of Certifying Authorities (CCA) Government
Government of India Ministry of Communications & Information Technology Department of Electronics & Information Technology (DeitY) Title of Policy: Policy on Open APIs for Government of India Preamble:
Genomic and Clinical Data Sharing Policy Questions with Technology and Security Implications: Consensus s from the Data Safe Havens Task Team Delivery date: 18 October 2014 When the Security Working Group
IRIS Onboarding Platform Product Overview The Need for a Digitized Onboarding Platform In the current paper-based onboarding process, disparate and self-contained systems work in a non-integrated environment.
Homeland Security Presidential Directive 12 (HSPD 12) Overview Audio: Welcome to the Homeland Security Presidential Directive 12 (HSPD 12) overview module, the first in a series of informational modules
System i Security Digital Certificate Manager Version 5 Release 4 System i Security Digital Certificate Manager Version 5 Release 4 Note Before using this information and the product it supports, be sure
Guidelines for E-mail Account Management and Effective E-mail Usage October 2014 Version 1.0 Department of Electronics and Information Technology Ministry of Communications and Information Technology Government
Evaluation of different Open Source Identity management Systems Ghasan Bhatti, Syed Yasir Imtiaz Linkoping s universitetet, Sweden [ghabh683, syeim642]@student.liu.se 1. Abstract Identity management systems
e-authentication guidelines for esign- Online Electronic Signature Service Version 1.0 June 2015 Controller of Certifying Authorities Department of Electronics and Information Technology Ministry of Communications
From Santhosh Hebbar, Date: 24-04-2015 Kumbar Jaddi, Hitlalli, Yellapur, Uttar Kannada, Karnataka-581347 To THE PRIME MINISTER, Prime Minister's Office, South Block, Raisina Hill, New Delhi-110011 Respected
RSA SecurID Two-factor Authentication Today, we live in an era where data is the lifeblood of a company. Now, security risks are more pressing as attackers have broadened their targets beyond financial
AT&T Synaptic Storage as a Service SM Getting Started Guide Version 3.0 2011 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. All other
WHITE PAPER MANAGED FILE TRANSFER: 10 STEPS TO SOX COMPLIANCE 1. OVERVIEW Do you want to design a file transfer process that is secure? Or one that is compliant? Of course, the answer is both. But it s
Sr. No. Agency Query NeGD Response 1 Email ID for vendors to request credentials for the DigiLocker demo firstname.lastname@example.org 2 Capri Tech Sys Whether a regular Partnership firm (not an LLP) is
IBM i Security Digital Certificate Manager 7.1 IBM i Security Digital Certificate Manager 7.1 Note Before using this information and the product it supports, be sure to read the information in Notices,
Aadhaar Security Policy & Framework for UIDAI Authentication Version 1.0 Unique Identification Authority of India (UIDAI) Table of Contents ACRONYMS AND TERMS... 3 1. INTRODUCTION... 4 2. SECURITY CONSIDERATION...
IBM Campaign Version-independent Integration with IBM Engage Version 1 Release 3 April 8, 2016 Integration Guide IBM Note Before using this information and the product it supports, read the information
S E P T E M B E R 2 0 1 3 Comply or Perish: The biggest challenges of Life Sciences companies today are maintaining a robust product pipeline and reducing time to market while complying with an increasing
e-pramaan: A National e-authentication Service End User Manual version 0.1 1 End-User Manual for e-pramaan: A National e-authentication Service Submitted to Department of Electronics & Information Technology
Class 3 Registration Authority Charter Version 1.0 applicable from 09 November 2010 Building A, Cambridge Park, 5 Bauhinia Street, Highveld Park, South Africa, 0046 Phone +27 (0)12 676 9240 Fax +27 (0)12
Adobe Digital Publishing Suite Security FAQ Adobe Digital Publishing Security FAQ Table of contents DPS Security Overview Network Service Topology Folio ProducerService Network Diagram Fulfillment Server
IDENTITY INFORMATION MANAGMENT ARCHITECTURE SUMMARY Architecture and Standards Branch Author: Creation Date: Last Updated: Version: I. Bailey May 28, 2008 March 23, 2009 0.7 Reviewed By Name Organization
Incorporated 3/7/06; Rev 9/18/09 PaperClip Compliant Email Service Whitepaper Overview The FTC Safeguard Rules require Financial, Insurance and Medical providers to protect their customer s private information
An Approach to Achieve Delegation of Sensitive RESTful Resources on Storage Cloud Kanchanna Ramasamy Balraj Engineering Ingegneria Informatica Spa, Rome, Italy Abstract. The paper explains a simple approach
HOW IT WORKS E-SIGNLIVE 1 INTRODUCTION With e-signlive, Silanis hosted service, you can invite other people to conveniently and securely sign documents over the web. Your documents can be easily signed
Microsoft Office 365 from Vodafone Administrator s Guide for Midsize Businesses and Enterprises Contents Footer bar Return to contents page Go to next of section Return to start of section Previous page
Denver Public Schools - East High School Return this page to the Technology Department in room 230 Electronic Web Access Agreement for Viewing Student Information via DPS Infinite Campus Parent/Student
How to configure Mac OS X Server By Rob Buckley In the previous article in this series, we showed you how to secure a Mac using the functions built into its operating system, OS X. See photo story here
Registration Authority Charter Version 3.0 is applicable from Effective Date Inyanda House 21 Wellington Road Parktown, 2193 Phone +27 (0)11 544 9368 Fax +27 (0)11 544 9599 Website: http://www.transnet.co.za/
3D SECURE We have seen merchants reduce fraud by up to 95% when integrating to 3D Secure... System Overview This document is intended for merchant and developers that want to gain a high level overview
www.css-security.com 425.216.0720 WHITE PAPER Microsoft Windows (RMS) provides authors and owners the ability to control how they use and distribute their digital content when using rights-enabled applications,
FILEHOLD DOCUMENT MANAGEMENT SYSTEM 21 CFR PART 11 COMPLIANCE WHITE PAPER Copyright 2012 FileHold Systems Inc. All rights reserved. For further information about this manual or other FileHold Systems products,
CipherShare s and CipherShare s and Security End-to-end Encryption Need-to-Know: Challenge / Response Authentication Transitive Trust Consistent Security Password and Key Recovery Temporary Application
WHITE PAPER MANAGED FILE TRANSFER: 10 STEPS TO HIPAA/HITECH COMPLIANCE 1. OVERVIEW Do you want to design a file transfer process that is secure? Or one that is compliant? Of course, the answer is both.
Mitra Innovation Leverages WSO2's Open Source Middleware to Build BIM Exchange Platform May 2015 Contents 1. Introduction... 3 2. What is BIM... 3 2.1. History of BIM... 3 2.2. Why Implement BIM... 4 2.3.
PERSONAL IDENTITY VERIFICATION (PIV) OVERVIEW INTRODUCTION (1) Welcome to the Homeland Security Presidential Directive 12 (HSPD-12) Personal Identity Verification (PIV) Overview module, designed to familiarize
Table of Contents Table of Contents Getting Started with Pivotal Single Sign-On Adding Users to a Single Sign-On Service Plan Administering Pivotal Single Sign-On Choosing an Application Type 1 2 5 7 10
Technical Data Sheet DirX Identity V8.5 Secure and flexible Password Management DirX Identity provides a comprehensive password management solution for enterprises and organizations. It delivers self-service
http://ezid.cdlib.org Service Guidelines 1 Purpose This document describes the key services and core policies underlying (CDL) s EZID Service. 2 Introduction to EZID EZID (easy eye dee) is a service providing
ATTESTATION OF ACADEMIC CERTIFICATES FOR FOREIGN STUDENTS RETURNING AFTER COMPLETION OF COURSE IN STATE OF MAHARASHTRA. Department of Higher & Technical Education Human Resource Development Section Government
Critical Factors for the Success of Large Government Digitization Projects Unpublished Property of Newgen Software Copyright 2011 (Newgen Software). For more information, please visit our website at www.newgensoft.com
The Estonian ID Card and Digital Signature Concept Principles and Solutions Ver 20030307 Contents Contents...2 Status of the document...3 Introduction...3 Intended audience...3 Current project status...3
IBM Campaign and IBM Silverpop Engage Version 1 Release 2 August 31, 2015 Integration Guide IBM Note Before using this information and the product it supports, read the information in Notices on page 93.
PUBLIC KEY INFRASTRUCTURE http://www.tutorialspoint.com/cryptography/public_key_infrastructure.htm Copyright tutorialspoint.com The most distinct feature of Public Key Infrastructure PKC is that it uses
IBM Connections White Paper September 2014 IBM Connections Cloud Security 2 IBM Connections Cloud Security Contents 3 Introduction 4 Security-rich Infrastructure 6 Policy Enforcement Points Provide Application
Card Management System Integration Made Easy: Tools for Enrollment and Management of Certificates September 2006 Copyright 2006 Entrust. All rights reserved. www.entrust.com Entrust is a registered trademark
SOA REFERENCE ARCHITECTURE: WEB TIER SOA Blueprint A structured blog by Yogish Pai Web Application Tier The primary requirement for this tier is that all the business systems and solutions be accessible
The Recipe for Sarbanes-Oxley Compliance using Microsoft s SharePoint 2010 platform Technical Discussion David Churchill CEO DraftPoint Inc. The information contained in this document represents the current
and s Branch Glossary of Key Terms The terms and definitions listed in this glossary are used throughout the s Package to define key terms in the context of. Access Control Access The processes by which
Technical Data Sheet DirX Identity V8.4 Secure and flexible Password Management DirX Identity provides a comprehensive password management solution for enterprises and organizations. It delivers self-service
Sophos Mobile Control Startup guide Product version: 3.5 Document date: July 2013 Contents 1 About this guide...3 2 What are the key steps?...5 3 Log in as a super administrator...6 4 Activate Sophos Mobile
McAfee Web Gateway Administration Intel Security Education Services Administration Course Training The McAfee Web Gateway Administration course from Education Services provides an in-depth introduction
DEPARTMENT OF ECONOMICS AND STATISTICS NAGALAND: KOHIMA OFFICE MEMORANDUM Dated Kohima the 14 th June 2013 In pursuant to Notification NO.ES/SP&SSDG/2011-12/67 dated 17-05-2013 the Directorate of Economics
e-government initiatives Anoop Kumar Agrawal, President and CEO, National e-government Division, Deity 26-08-2015 e-governance Development Index Online Service Component Basic e-services, e-participation,
SBA Procedural Notice TO: All SBA Employees CONTROL NO.: 5000-1323 SUBJECT: Acceptance of Electronic Signatures in the 7(a) and 504 Loan Program EFFECTIVE: 10/21/14 The purpose of this Notice is to inform
Xerox econcierge Account Setup Guide Xerox econcierge Account Setup Guide The free Xerox econcierge service provides the quickest, easiest way for your customers to order printer supplies for all their
www.novell.com/documentation Jobs Guide Identity Manager 4.0.1 February 10, 2012 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation,
Citrix Password Manager Quick Deployment Guide Install and Use Password Manager on Presentation Server in Under Two Hours Citrix Systems, Inc. Notice The information in this publication is subject to change
How to Prepare for the Upgrade to Microsoft Dynamics CRM 2013 (On-premises) COMPANY: Microsoft Corporation RELEASED: September 2013 VERSION: 1.0 Copyright This document is provided "as-is". Information
Procedures for the ICAO Public Key Directory last modification final 1/13 SECTION 1 INTRODUCTION 1.1 As part of the MRTD initiative by ICAO, the Participants will upload to and download from the PKD, their
White Paper Delivering Web Services Security: September 2003 Copyright 2003 Entrust. All rights reserved. Entrust is a registered trademark of Entrust, Inc. in the United States and certain other countries.
Cyber Essentials Questionnaire Introduction The Cyber Essentials scheme is recommended for organisations looking for a base level Cyber security test where IT is a business enabler rather than a core deliverable.
Intland s Medical Template Traceability Browser Risk Management & FMEA Medical Wiki Supports compliance with IEC 62304, FDA Title 21 CFR Part 11, ISO 14971, IEC 60601 and more INTLAND codebeamer ALM is
ITAR Compliant Data Exchange Managing ITAR Data Across Collaborative Project Teams WebSpace Customers Aerospace & Defense Manufacturing High Tech & Contract Manufacturing Automotive Manufacturing Medical/
WEBSITE HOSTING SERVICES AGREEMENT Effective Date: 1/1/2015 1) Scope of Services. Company will provide Client a shared or dedicated virtual machine, an Internet address for storage and access to Content,
BlitzDocs Product Brief Intelligent collaboration in the mortgage process Intelligent collaboration in the mortgage process Your business is specific to your processes and your trading partners. That is
Policy Based Encryption E Administrator Guide Policy Based Encryption E Administrator Guide Documentation version: 1.2 Legal Notice Legal Notice Copyright 2012 Symantec Corporation. All rights reserved.
Policy Based Encryption E Administrator Guide Policy Based Encryption E Administrator Guide Documentation version: 1.2 Legal Notice Legal Notice Copyright 2012 Symantec Corporation. All rights reserved.
COMPANY INFO 1 (23) Ericsson Group Certificate Value Statement - 2013 COMPANY INFO 2 (23) Contents 1 Ericsson Certificate Value Statement... 3 2 Introduction... 3 2.1 Overview... 3 3 Contact information...
Two-Factor Authentication A Total Cost of Ownership Viewpoint CONTENTS + Two-Factor Authentication 3 A Total Cost of Ownership Viewpoint + Introduction 3 + Defining Total Cost of Ownership 3 + VeriSign
Sisense Product Highlights Introduction Sisense is a business intelligence solution that simplifies analytics for complex data by offering an end-to-end platform that lets users easily prepare and analyze
X-Road egovernment interoperability framework Serving e-nation over 10 years Backbone of the Estonian egovernment 12 years of active duty, no downtime Over 2000 connected e-services More than 900 connected