UIDAI
Unique Identification Authority of India
Planning Commission, Govt. of India (GoI),
3rd Floor, Tower II,
Jeevan Bharati Building,
Connaught Circus,
New Delhi 110001
Auth Portal AUA User Manual
Auth Portal User Manual
Version 1.0
1
Table of Contents
1
Introduction ............................................................................................................................................ 5
1.1
Purpose ......................................................................................................................................... 5
1.2
Audience ....................................................................................................................................... 5
1.3
Documentation .............................................................................................................................. 5
1.4
Minimum System Requirements ................................................................................................... 5
1.5
Problem Reporting ........................................................................................................................ 5
2
Features of Auth Portal .......................................................................................................................... 6
3
General Operating Instructions .............................................................................................................. 7
4
3.1
Getting Started .............................................................................................................................. 7
3.2
How to Login to Auth Portal .......................................................................................................... 8
Specific Operating Instructions .............................................................................................................. 9
4.1
AUA On-boarding System Flow .................................................................................................... 9
4.1.1
Submit Enquiry .......................................................................................................................... 9
4.1.2
UIDAI Response to the Enquiry .............................................................................................. 14
4.1.3
Detailed Application Submission ............................................................................................. 14
4.1.4
UIDAI Approval or Rejection ................................................................................................... 24
4.1.5
Signs Agreement ..................................................................................................................... 24
4.1.6
Assessment of Support Required for Readiness .................................................................... 25
4.1.7
Pre-production Integration and Execution in Collaboration with an Approved ASA ............... 25
4.1.8
End to End Testing with an Approved ASA, Audit and Submits Request for Go Live ............ 25
4.1.9
Go Live Checklist Approved .................................................................................................... 29
4.1.10
4.2
Ready to Go Live................................................................................................................. 29
Service Request .......................................................................................................................... 30
4.2.1
Feedback ................................................................................................................................. 30
4.2.2
Incident Reporting ................................................................................................................... 31
4.3
BI Reports/Reports ...................................................................................................................... 32
4.3.1
AUA Wise Biometric Authentication ........................................................................................ 34
4.3.2
ASA Wise Biometric Authentication Report ............................................................................ 35
4.3.3
AUA Wise Demographic Authentication ................................................................................. 36
4.3.4
ASA Wise Demographic Authentication .................................................................................. 37
4.3.5
Aadhaar Authentication- Response by Attempts .................................................................... 38
4.3.6
AUA Wise Rejected Business Transaction Report ................................................................. 39
4.3.7
Aadhaar Authentication Response by Business Transaction Report ..................................... 39
Auth Portal User Manual
Version 1.0
2
4.3.8
Rejected Authentication Transaction Report .......................................................................... 40
4.3.9
AUA Wise Rejected Analysis for Multiple Finger Authentication Report ................................ 41
4.3.10
District Wise Authentication Report (Monthly Report) ......................................................... 42
4.3.11
UDC wise Authentication Report (Monthly Report) ............................................................. 42
4.3.12
Device type wise Authentication Report (Monthly Report) ................................................. 43
4.4
Documents Repository ................................................................................................................ 43
5
Frequently Asked Questions ................................................................................................................ 45
6
Definitions and Acronyms .................................................................................................................... 47
6.1
Definitions .................................................................................................................................... 47
6.2
Acronyms .................................................................................................................................... 48
Auth Portal User Manual
Version 1.0
3
Table of Figures
Figure 1: Auth Portal Home Page ................................................................................................................. 7
Figure 2: Login Screen .................................................................................................................................. 8
Figure 3: How to be an AUA ......................................................................................................................... 9
Figure 4: AUA Enquiry Form ....................................................................................................................... 10
Figure 5: AUA Enquiry Request Preview .................................................................................................... 13
Figure 6: UIDAI Reference Number ............................................................................................................ 14
Figure 7: Welcome Screen.......................................................................................................................... 15
Figure 8: Detailed Application Form ............................................................................................................ 17
Figure 9: Detailed Application Preview ....................................................................................................... 23
Figure 10: Detailed Application Submission .............................................................................................. 23
Figure 11: Application Status ...................................................................................................................... 24
Figure 12: Go Live and Audit Compliance Checklist Link ........................................................................... 25
Figure 13: Go Live Checklist ....................................................................................................................... 26
Figure 14: Audit Compliance Checklist ....................................................................................................... 28
Figure 15: Go Live Checklist Submission ................................................................................................... 29
Figure 16: Feedback Form .......................................................................................................................... 30
Figure 17: Incident Report Form ................................................................................................................. 32
Figure 18: BI Reports .................................................................................................................................. 32
Figure 19: Report Generation .................................................................................................................... 33
Figure 20: Document Repository ................................................................................................................ 44
Auth Portal User Manual
Version 1.0
4
1 Introduction
Auth portal offers to provide services like on-boarding process, AUA - ASA engagement process, and
technical enablement activities. It also offers end to end user management and organization
management.
The one of the main purpose of developing an Auth portal is to fasten the AUA / ASA registration and Onboarding process, simple, convenient and online management of various activities which are required to
be managed by Authentication User Agencies.
1.1 Purpose
The purpose of this document is to provide step-wise instructions to the Authentication User Agency
(AUA) to work on Auth Portal with visual screens for easy and better understanding. It also describes
each form details and its flow based on the actions.
1.2 Audience

Authentication User Agency
1.3 Documentation
The documentation is provided in the following formats:


Adobe Acrobat PDF files
Microsoft World document files
You must have Adobe Acrobat Reader installed to read the PDF files. You can download Adobe Reader
for free from Adobe website which is www.adobe.com.
1.4 Minimum System Requirements
Auth Portal is a web based application, the minimum system requirements for accessing the website are:


Latest Version of Popular Browser (IE, Mozilla Firefox and Google Chrome)
Internet Connection
1.5 Problem Reporting
You can send your queries / issues at authsupport@uidai.gov.in.
Auth Portal User Manual
Version 1.0
5
2 Features of Auth Portal
Auth Portal is web-based, very simple and easy to use software with user friendly interface that facilitates
AUA and ASA on enquiry submission process, on-boarding process and Life Cycle Management
activities such as AUA Services, feedback submission to UIDAI and incident reporting. Auth Portal helps
agencies by providing BI reports, which helps them in decision making and identifying the trends based
on various reports.
The key features of the portal include:

ASA and AUA on-boarding Process: Auth Portal facilitates ASA to maintain its profile. The
profile includes brief description about the local government, connectivity to the local government,
neighboring local bodies, places of tourist interest, boarding and lodge details etc.

ASA Services: Facilitates ASA’s to manage the AUAs requests to use ASA services for
Authentication.

Services Requests: - Facilitates AUA to send their feedbacks and Incident reporting to the
UIDAI.

BI Reports - Facilitates AUA to access various Business Intelligence reports to analyze and
identify the various trends and issues which helps AUAs in future strategic planning and decision
making process.

Account Management - This section helps you to manage Organizations and User Information
like personal details, password, Organization, Roles and Identification details like Addresses,
Phone number, email address details etc.

Simplicity & User Friendliness – Auth Portal user interface is intuitively and consistently
designed to enable simplicity and ease of use to end users. Online, field-level help is available for
better understanding and effective usage.

SMS / Email Based Alerts/Notification – Auth Portal has a built in system of alerts/notifications
via SMS/EMAIL on important actions.

Authentication - In view of the high security need of the system, the software provides strong
authentication mechanism and also maintains detailed audit logs of all the transactions carried
out through the software.
Auth Portal User Manual
Version 1.0
6
3 General Operating Instructions
3.1 Getting Started
Auth portal home page will be displayed when you access the auth portal URL. You will not be able to
access the internal pages without logging in to the portal. The home page of Auth portal is shown in the
snapshot below:
Figure 1: Auth Portal Home Page
Click the Login
contain the following fields:


button in order to login to the Auth portal. The Login form will
Username: Please specify the user name which was provided by UIDAI
Password: Please specify the password which was provided by UIDAI.
Note: Forgot password option will allow you to reset the password in case if you forget the password.
Auth Portal home page also contains useful information and links related to the portal. The common
features of the site are made available to all. Anyone can access the common features of the site without
login in to the portal.
Auth Portal User Manual
Version 1.0
7
3.2 How to Login to Auth Portal
In order to login to Auth portal, follow the steps listed below:
1. In order to access Auth portal, use the link http://authportal.uidai.gov.in/.
2. Click the Login
button on the home page.
3. Enter the Username and Password and click the Sign In button as shown in the snapshot below:
Figure 2: Login Screen
4. If the Login is successful, you will be able to proceed with the application. In case of an error, an
appropriate message will be displayed on your screen with reason for unsuccessful login.
Once the login attempt is successful, you will be able to access the features which are assigned to you
role.
In case of unsuccessful login the below messages will be displayed on your screen:
S. No.
Message
Reason
Expected Action from the user
1
This Field Is required
This indicates that you have
not entered Username or
Password and clicked on Login
button
Enter the Username and Password
and then click on Login button
2.
Your request failed to
complete.
This Indicates that provide user
name and password could not
be validated
Verify the entered User Name and
password and Renter the valid user
name and password.
Auth Portal User Manual
Version 1.0
8
4 Specific Operating Instructions
This section will provide the step by step instructions to proceed with all the modules and features
available for you role.
4.1 AUA On-boarding System Flow
AUA on-boarding function allows the AUA’s to engage with UIDAI. The steps to onboard an AUA are
listed below:










Submit Enquiry.
Responds to AUA enquiry.
Submits application with supporting documentation.
Verifies and approves application.
Signs agreement.
Assessment of support required for readiness.
Assist in Pre-production Integration and Execution in collaboration with an approved ASA.
Conducts end to end testing with an approved ASA, audit and submits request for Go Live.
Approve and assist in Go Live.
Production release and operations management.
4.1.1 Submit Enquiry
In order to submit new enquiry follow the steps listed below:
1. Open the Auth portal home page using the URL http://authportal.uidai.gov.in/.
2. Click the Partners tab and click the How to be an AUA link as shown in the snapshot below:
Figure 3: How to be an AUA
Note: You can also access the enquiry form by clicking on Want to be a Partner link on the
header and Send Enquiry link in the bottom left corner of the screen.
Auth Portal User Manual
Version 1.0
9
3. Fill all the mandatory fields in the enquiry form and click the Submit button as shown in the
snapshot below:
Figure 4: AUA Enquiry Form
Auth Portal User Manual
Version 1.0
10
The enquiry form contains the following fields:
S. No
Field Name
Explanation
Organization Details
Description - Enter the Organization Name.
1
Organization Name
Mandatory / Optional - It is a Mandatory field.
Description - Enter the Address Line 1 of your office address.
2
Address Line 1
Mandatory / Optional - It is a Mandatory field.
3
Address Line 2
Description - This field is used to specify the additional details of your
office address, if you won’t be able to enter the complete address in
Address line 1 fields
Mandatory / Optional - It is an Optional field.
Description - Select the State.
4
State
Mandatory / Optional - It is a mandatory field.
Description - Enter the 6 digit pin code of your office area.
5
Pin code
Mandatory / Optional - It is a Mandatory field.
Description - Select the Organization type from the dropdown list. The
list will contain following options :Central Government Ministry / Department
State Government Department
Public Sector Undertaking
Authority constituted under the Central / State Act
6
Organization type
Not-for-Profit Company / Special Purpose Organization of national
importance
Network Service Provider
Telecom Service Provider
System Integrator
Mandatory / Optional - It is a Mandatory field.
7
Industry Sector
Auth Portal User Manual
Description - Select the best suited Industry Sector from the dropdown
list for your organization. The available list is as following:-
Version 1.0
11
S. No
Field Name
Explanation
Social Sector
Banking & Finance
Telecom
Petroleum & Natural Gas
Hospitality
Education
Healthcare
Agriculture
Information Technology
Labor & Employment
Others (Please Specify_______________________)
Mandatory / Optional - It is a Mandatory field.
8
Proposed Business
Scope
Description – This field is used to specify your proposed business scope
as an ASA.
Mandatory / Optional - It is an Optional field.
Nodal Point of Contact
Description – Enter the Nodal Person name.
9
Nodal Person name
Mandatory / Optional - It is a Mandatory field.
Description – Enter the Email address of the nodal person.
11
Email Id
Mandatory / Optional - It is a Mandatory field.
Description – Enter the Mobile number of the nodal officer.
12
Mobile Number
Mandatory / Optional - It is a Mandatory field.
Description – Enter the Landline number of the nodal officer.
13
Telephone Number
Mandatory / Optional - It is a Mandatory field.
Description – Enter the Landline number of the nodal office.
14
Fax
Mandatory / Optional - It is an Optional field.
Auth Portal User Manual
Version 1.0
12
S. No
15
Field Name
Any Queries
Explanation
Description – If you have any queries while submitting enquiry, You can
enter the details.
Mandatory/Optional - It is an Optional field.
4. The entered details will be displayed on your screen, verify the details and click the Confirm and
Submit button as shown in the snapshot below:
Figure 5: AUA Enquiry Request Preview
Auth Portal User Manual
Version 1.0
13
5. Once you submit the enquiry, a reference number will be generated as shown in the snapshot
below:
Figure 6: UIDAI Reference Number
4.1.2 UIDAI Response to the Enquiry
Once the enquiry form is submitted to UIDAI, the enquiry form will be reviewed by the UIDAI Auth Nodal
Person (Auth Admin User). UIDAI Nodal person will respond to the query with any one of the below
options:


Accept
Reject
On acceptance of enquiry by UIDAI, an acknowledgement email along with user id & password will be
sent to you on your registered email address.
If your enquiry is rejected by UIDAI, You will receive a notification email with the reason for rejection of
your enquiry.
4.1.3 Detailed Application Submission
You have to login to the Auth portal using the login id and password provided by UIDAI to submit the
detailed application.
On logging in to the Auth portal you will be asked to reset your password. Once you reset the password,
you will be given an option to submit the detailed application form.
Auth Portal User Manual
Version 1.0
14
1. Click the Click here to submit the Application hyperlink to access the detailed application form
as shown in the snapshot below:
Figure 7: Welcome Screen
2. Enter the required details to complete the detailed application form as shown in the snapshot
below:
Auth Portal User Manual
Version 1.0
15
Auth Portal User Manual
Version 1.0
16
Figure 8: Detailed Application Form
Auth Portal User Manual
Version 1.0
17
The application form contains the below fields:
S. No
Field Name
Explanation
Organization Details
1.
Organization Name
Description – Display in read only mode.
2.
Address Line 1.
Description – Display in read only mode.
3.
Address Line2
Description – Display in read only mode.
4.
State
Description – Display in read only mode.
5.
Pin code
Description – Display in read only mode.
6.
Organization type
Description – Display in read only mode.
7.
Industry Sector
Description – Display in read only mode.
8.
Proposed Business
Scope
Description – This field is used to specify your proposed
business scope as an ASA.
Mandatory/Optional - It is an Optional field.
Management Point of Contact
9.
Contact Name
Description – Enter the Contact person name.
Mandatory/Optional - It is a Mandatory field.
10.
Email Address
Description – Enter the Email address of the contact person.
Mandatory/Optional - It is a Mandatory field.
11.
Mobile Number
Description – Enter the Mobile number of the contact officer.
Mandatory/Optional - It is a Mandatory field.
12.
Telephone Number
Description – Enter the Landline number of the contact officer.
Mandatory/Optional - It is a Mandatory field.
13.
Fax
Description – Enter the Landline number of the nodal office.
Mandatory/Optional - It is an Optional field.
Technical Point of Contact
14.
Contact Name
Description – Enter the Contact person name.
Mandatory/Optional - It is a Mandatory field.
Auth Portal User Manual
Version 1.0
18
S. No
Field Name
15.
Email Address
Explanation
Description – Enter the Email address of the contact person.
Mandatory/Optional - It is a Mandatory field.
16.
Mobile Number
Description – Enter the Mobile number of the contact officer.
Mandatory/Optional - It is a Mandatory field.
17.
Telephone Number
Description – Enter the Landline number of the contact officer.
Mandatory/Optional - It is a Mandatory field.
18.
Fax
Description – Enter the Landline number of the nodal office.
Mandatory/Optional - It is an Optional field.
ASA Infrastructure details
19.
Primary DC
Description- Select the State from the dropdown list which you
have selected as Primary DC.
Mandatory/Optional - It is a Mandatory field.
20.
Secondary DC
Description - Select the State from the dropdown list which you
have selected as Secondary DC.
Mandatory/Optional - It is an Optional field.
21.
DR Site
Description - Select the State from the dropdown list which you
have selected as Disaster Recovery site.
Mandatory/Optional - It is an Optional field.
Connecting to CIDR
22.
23.
Planned Lease Line
capacity (In Mbps)*
Description – Specify the planned lease line capacity in number.
It is recommended that ASA should plan minimum 5 Mbps.
Please Press 'Ctrl' and
select multiple options
from the list
Mandatory/Optional - It is a mandatory field.
UIDAI DC where Lease
Line is Planned *
Description – Select the UIDAI DC where you have planned to
connect via Lease line. To select multiple options press CTRL
and select multiple options.
Mandatory/Optional - It is a mandatory field.
Auth Portal User Manual
Version 1.0
19
S. No
Field Name
Explanation
24.
No. of Lease Line
Planned *
Description – Select any one option from the dropdown list as
stated below:
1 at Noida DC only
1 at Bangalore DC only
2 at Noida DC only
2 at Bangalore DC only
1 each at Noida & Bangalore DCs
2 each at Noida & Bangalore DCs
2 at Noida DC and 1 at Bangalore DC
1 at Noida DC and 2 at Bangalore DC
Mandatory/Optional - It is a mandatory field
AUA Related Information
25.
Geography Catered To
Description – Select any one option from the dropdown list as
stated below:
Pan India
Multiple States
State level
Specify states in case multiple states /single state selected.
Mandatory/Optional - It is a mandatory field.
26.
AUA Supported
Description – Select any one option from the dropdown list as
stated below:
Self as AUA Only
Other entities as AUAs Only
Self as AUA + Other entities as AUAs
27.
Fraud Monitoring
capabilities
Auth Portal User Manual
Description – Select any one option from the dropdown list as
stated below:
Version 1.0
20
S. No
Field Name
Explanation
Yes
No
In Future
Terms and Conditions
28.
Agree to UIDAI Terms
and Conditions
Description - Select the check box if you agree to the UIDAI
Contract Terms and Condition. You can read the full terms and
condition
3. Click the Save
button to save the entered details and Proceed
go to the next stage of application submission.
button to
4. Click the Confirm and Print button in the Application preview screen to download the application
form as shown in the snapshot below:
Auth Portal User Manual
Version 1.0
21
Auth Portal User Manual
Version 1.0
22
Figure 9: Detailed Application Preview
Note: The application should be printed on the company stamp paper and signed by the
concerned authority.
AUA_Application
Form.pdf
5. Upload the signed application form and click on the Submit button as shown in the snapshot
below:
Figure 10: Detailed Application Submission
Auth Portal User Manual
Version 1.0
23
6. A confirmation message will be displayed on your screen stating “Your Application No
'UIDAIAUAXXXXXXXX' has been submitted successfully. Your Application will be reviewed
and answered shortly”.
7. Click the AUA Application Status link to check the status of the application as shown in the
snapshot below:
Figure 11: Application Status
4.1.4 UIDAI Approval or Rejection
After the submission of the application form, your application would be sent to the UIDAI authority for
approval. The UIDAI Approval involves the following stages:
Application Approval
UIDAI reviews your application and approves it, if found satisfactory. UIDAI may also reject or return your
application with an appropriate reason. You will receive a notification email when UIDAI approves, rejects
or returns the application.
4.1.5 Signs Agreement
Once the application is approved by the UIDAI, you will receive a confirmation email. You need to
download the agreement paper from the portal and print it on applicable stamp paper. Submit two duly
signed copies of the agreement to UIDAI Headquarter. After receiving the approval copy, UIDAI will verify
the application and if found satisfactory, UIDAI uploads information on portal and approves the request.
UIDAI_AUA_Agreem
ent.pdf
Note: At this step an AUA is also expected to have an arrangement in place with an UIDAI approved ASA
to access UIDAI authentication services. An arrangement with an ASA is required by an AUA to get
access to UIDAI Authentication database (CIDR). An AUA may enter into an agreement with an ASA as
deemed appropriate by the two parties. To provide support on the agreement, UIDAI has published
guidelines for AUA-ASA agreement.
Auth Portal User Manual
Version 1.0
24
4.1.6 Assessment of Support Required for Readiness
Based on interaction during the previous steps of the process and inputs from an AUA, UIDAI
engagement team assesses the level of support to be provided for go live readiness. In majority of the
cases the assessment for the level of support required by an AUA is accomplished in collaboration with
an ASA. An ASA plays a vital role in On-boarding and readiness of an AUA as the connectivity between
AUA and ASA is a pre-requisite for an AUA to access Aadhaar authentication services.
4.1.7 Pre-production Integration and Execution in Collaboration with an
Approved ASA
UIDAI authentication support team in consultation with an ASA provides access to pre-production
environment and enables the AUA to establish end to end connectivity through an ASA server to carry out
authentication services testing.
UIDAI Authentication support team responds to pre-production access request received from ASA by
sharing the AUA code and license key to enable AUA to conduct end to end testing. At this stage an AUA
is also linked with an approved ASA in the UIDAI backend system which enables the ASA and UIDAI to
process authentication transactions transmitted by an AUA.
4.1.8 End to End Testing with an Approved ASA, Audit and Submits Request for
Go Live
AUA engages the respective ASA and conducts end to end testing on UIDAI pre-production environment.
Post successful end to end testing AUA engages an Auditor to conduct the compliance audit as per
Aadhaar Authentication Standards and Specifications.
Subsequently AUA completes the go live checklist and submits the request for go live with the following
documents:


Go live checklist.
Audit certificate as proof of compliance to current UIDAI standards and specifications.
The Go Live check list and Audit compliance checklist can be accessed by clicking on the hyperlink
provided in the AUA status screen as shown in the snapshot below:
Figure 12: Go Live and Audit Compliance Checklist Link
Auth Portal User Manual
Version 1.0
25
The Go Live Checklist is shown in the diagram below:
Figure 13: Go Live Checklist
Auth Portal User Manual
Version 1.0
26
You should first submit the audit compliance report by clicking on the Audit compliance link available in
the 10th row of the sheet. Once you will click on it. You will be redirected to the Audit compliance Check
list. The Audit Compliance Checklist is displayed in the below snapshot:
Auth Portal User Manual
Version 1.0
27
Figure 14: Audit Compliance Checklist
Auth Portal User Manual
Version 1.0
28
Once the Audit compliance checklist is submitted, you will get an option to submit the Go Live checklist as
shown in the snapshot below:
Figure 15: Go Live Checklist Submission
4.1.9 Go Live Checklist Approved
UIDAI Ops team reviews the Go Live check list and approves the request if all information provided by
you is found correct. Once UIDAI ops teams approves the request, The UIDAI Admin review and approve
the Audit compliance check list if found satisfactory.
After approving the Audit Compliance check list UIDAI Admin approves your request to migrate on Live.
In case of insufficient documents or some missing information UIDAI may return your application with a
specific reason. You should read the reason carefully and send back your information by providing the
required information by you.
You will be informed in case of application Rejected by UIDAI along with the reason of rejection.
4.1.10 Ready to Go Live
After getting migration approval AUA will be provided with the AUA license code. This process will be
handled by UIDAI office.
Auth Portal User Manual
Version 1.0
29
4.2 Service Request
4.2.1 Feedback
AUA can send feedback to UIDAI based on following attribute as Excellent / Very Good / Good / Average
/ Not Satisfactory.










Look and feel of website.
Support (Helpdesk).
User friendliness and Ease of navigation.
Confidentiality and Transparency.
Security.
Cost effectiveness.
Functionality.
Increase in business opportunities.
Increase in competitiveness.
Over all site experience.
The feedback form is shown in the snapshot below:
Figure 16: Feedback Form
To send a feedback you are required to specify following fields on the feedback form:
S. No.
Field Name
Explanation
1
User Type
Description- Display Registered options as selected in Read
only mode
2
Name
Auth Portal User Manual
Description – Display the ASA name.
Version 1.0
30
S. No.
Field Name
Explanation
3
Email id
Description –Display registered email address of the ASA in
read only mode.
4
Phone Number
Description –Display registered mobile number in read only
mode.
Description:- Select the suitable option from Excellent/Very
Good/Good/ Average/ Not Satisfactory options from the
following attributes:-
5
Rating based on Various
attributes.
6
Text Verification
 Look and feel of website.
 Support (Helpdesk).
 User friendliness and Ease of navigation.
 Confidentiality and Transparency.
 Security.
 Cost effectiveness.
 Functionality.
 Increase in business opportunities.
 Increase in competitiveness.
 Over all site experience.
Description: Enter the text shown in the image.
After specifying the complete details, click on Submit button to send feedback to the UIDAI.
4.2.2 Incident Reporting
This section helps AUA’s to report any incident related to fraud or threat to UIDAI. To report any incident
you need to login to auth portal and click on Incident Report option available under Service Request
section in the left menu as shown in the snapshot below:
To report an incident you need to specify following details on the form:
S. No.
Field Name
Explanation
1.
Type of Report
Description - Select the Report type from the dropdown list.
2.
Type Of Reason
Description - Select the Reason of reporting from the
dropdown list
3.
Description
Description - Enter the brief description of Fraud/Incidence you
want to report.
4.
Text Verification
Description - Enter the Text in the text box as shown in the
image above the text field.
Auth Portal User Manual
Version 1.0
31
The below snapshot shows the Incident Reporting form:
Figure 17: Incident Report Form
After providing the complete details, click the Submit button to submit the report.
4.3 BI Reports/Reports
This section allows you to view various reports like ASA Wise Biometric report, AUA wise Biometric report
in .pdf and .xls format.
To access various reports, click on Report link available under BI Report section in the left menu as
shown in the snapshot below:
Figure 18: BI Reports
Auth Portal User Manual
Version 1.0
32
To generate report follow the steps listed below:
1.
2.
3.
4.
Select the type of report from Report Type dropdown list.
Select the Report Period.
Select the Report Format from the dropdown list.
Click the Get Report button to view the selected report as shown in the snapshot below:
Figure 19: Report Generation
The below table shown the options which needs to be selected by an AUA to generate a report:
S. No
Field Name
Explanation
Description: Select the time period from the following options:-
1.
Report period




Today
Date Range
Week till date
Month till date
Mandatory/Optional: It is a Mandatory field.
2
Start Date
Description: When you select the time period as Date range then system
would ask you to enter the Start date.
Mandatory/Optional: It is a Mandatory field.
3
End Date
Auth Portal User Manual
Description: When you select the time period as Date range then system
would ask you to enter the End date.
Version 1.0
33
S. No
Field Name
Explanation
Mandatory/Optional: It is a Mandatory field.
Description: Select any one report format from the list of formats:-
4


Report Format
PDF
Excel
Mandatory/Optional: It is a Mandatory field.
Description: Select anyone of the AUA’s from the dropdown list.
5
AUA Name
Note: This is not applicable for all the reports.
4.3.1 AUA Wise Biometric Authentication
This report facilitates you to view AUA wise Biometric Authentication details. Click on the below icon to
view the report:
AUA_Wise_Biometric
_Authentication_Report.pdf
The AUA Wise Biometric Authentication report contains the below listed fields:
S. No
Field Name
1.
AUA Name
This column displays the AUA name.
2.
ASA Name
This column displays the ASA name associated with the
respective AUAs.
Unique UIDs
3.
Authenticated
Accepted
Authentication
3.
4.
Accepted %
UID Wise Auth
Auth Portal User Manual
Biometric
Explanation
This column displays the number of Unique IDs authenticated
for the selected time period by the respective AUAs.
This column displays the number of Accepted Authentication
for the selected time period by the respective AUAs.
This column displays the percentage wise authentication for
the selected time period by the respective AUAs.
This column displays the number of Biometric mismatch
happened between 0 -10 for the selected time period by the
Version 1.0
34
S. No
Field Name
Rejected Details
Explanation
Mismatch
respective AUAs.
(Error Code
300)
0-10
Biometric
Mismatch
(Error Code
300)
This column displays the number of Biometric mismatch
happened between 11 -20 for the selected time period by the
respective AUAs.
11-20
Biometric
Mismatch
(Error Code
300)
This column displays the number of Biometric mismatch
happened between 0 -10 for the selected time period by the
respective AUAs.
21-(T-1)
Other Errors
This column displays the number of rejection happened due to
any other errors for the selected time period by the respective
AUAs.
4.3.2 ASA Wise Biometric Authentication Report
This report facilitates you to view ASA wise Biometric Authentication details. Click on the below icon to
view the report:
ASA_Wise_Biometric
_Authentication_Report.pdf
The ASA Wise Biometric Authentication report contains the below listed fields:
S. No
Field Name
1
ASA Name
Unique UIDs
2
Authenticated
Auth Portal User Manual
Explanation
This column displays the ASA name.
This column displays the number of Unique IDs authenticated
for the selected time period by the respective ASAs.
Version 1.0
35
S. No
Field Name
Explanation
Accepted
This column displays the number of Accepted Authentication
for the selected time period by the respective ASAs.
3
Authentication
4
This column displays the percentage wise authentication for
the selected time period by the respective ASAs.
Accepted %
Biometric
Mismatch
(Error Code
300)
This column displays the number of Biometric mismatch
happened between 0 -10 for the selected time period by the
respective ASAs.
0-10
Biometric
Mismatch
5
UID Wise Auth
Rejected Details
(Error Code
300)
This column displays the number of Biometric mismatch
happened between 11 -20 for the selected time period by the
respective ASAs.
11-20
Biometric
Mismatch
(Error Code
300)
This column displays the number of Biometric mismatch
happened between 0 -10 for the selected time period by the
respective ASAs.
21-(T-1)
Other Errors
This column displays the number of rejection happened due to
any other errors for the selected time period by the respective
ASAs.
4.3.3 AUA Wise Demographic Authentication
This report facilitates you to view AUA wise Demographic Authentication details. Click on the below icon
to view the report:
AUA_Wise_Demogra
phic_Authentication_Report.pdf
The AUA Wise Demographic Authentication report contains the below listed fields:
Auth Portal User Manual
Version 1.0
36
S. No
Field Name
Explanation
1.
AUA Name
This column displays the AUA name.
2.
ASA Name
This column displays the ASA name associated with the
respective AUAs.
3.
Unique UIDs
This column displays the number of Unique IDs authenticated
for the selected time period by the respective AUAs.
Authenticated
4.
Accepted
This column displays the number of Accepted Authentication
for the selected time period by the respective AUAs.
Authentication
5.
6.
Accepted %
UID Wise Auth
Rejected Details
Demographic
Mismatch
This column displays the percentage wise authentication for
the selected time period by the respective AUAs.
This column displays the number of Demographic mismatch
happened for the selected time period by the respective AUAs.
(Error Code
100)
Demographic
Mismatch
This column displays the number of Demographic mismatch
happened for the selected time period by the respective AUAs.
(Error Code
200)
Other Errors
This column displays the number of rejection happened due to
any other errors for the selected time period by the respective
AUAs.
4.3.4 ASA Wise Demographic Authentication
This report facilitates you to view ASA Wise Demographic Authentication details. Click on the below icon
to view the report:
ASA_Wise_Demogra
phic_Authentication_Report.pdf
The ASA Wise Demographic Authentication report contains the below listed fields:
S. No
Field Name
1.
ASA Name
Auth Portal User Manual
Explanation
This column displays the ASA name associated with the
Version 1.0
37
S. No
Field Name
Explanation
respective ASAs.
2.
Unique UIDs Authenticated
This column displays the number of Unique IDs authenticated
for the selected time period by the respective ASAs.
3.
Accepted Authentication
This column displays the number of Accepted Authentication
for the selected time period by the respective ASAs.
4.
Accepted %
This column displays the percentage wise authentication for
the selected time period by the respective ASAs.
Demographic
Mismatch
(Error Code
100)
5.
UID Wise Auth
Rejected Details
Demographic
Mismatch
(Error Code
200)
Other Errors
This column displays the number of Demographic mismatch
happened for the selected time period by the respective ASAs.
This column displays the number of Demographic mismatch
happened for the selected time period by the respective ASAs.
This column displays the number of rejection happened due to
any other errors for the selected time period by the respective
ASAs.
4.3.5 Aadhaar Authentication- Response by Attempts
This report facilitates you to view Aadhaar Authentication- Response by Attempts report. Click on the
below icon to view the report:
Aadhaar_Authentica
tion-Response_by_Attempts_Report.pdf
The Aadhaar Authentication - Response by Attempts report contains the below listed fields:
S. No
Field Name
Explanation
1.
Response category
The column displays response category of authentication e.g.
Successful, Biometric Mismatch etc.
2.
Response Error Code
This column displays the error code against each category and “Yes” in
case of ‘Response Category’ is ‘Successful’
Auth Portal User Manual
Version 1.0
38
S. No
Field Name
Explanation
3.
Number of Attempts
This column displays count of attempts per Response Category in
the period selected.
4.
Percentage (%)
This column displays the percentage of response by Attempts. The
column should display the percentage of Number of attempts out of
Total number of attempts for each Response Category.
4.3.6 AUA Wise Rejected Business Transaction Report
This report facilitates you to view AUA Wise Rejected Business Transaction report. Click on the below
icon to view the report:
AUA_Wise_Rejected
_Business_Transactions_Report.pdf
The AUA Wise Rejected Business Transaction report contains the below listed fields:
S. No
Field Name
Explanation
1.
Number of Attempts
This column displays category of the number of attempts taken
per BT.
2.
Number of Rejected BT
This column displays total number of rejected BT per category.
3.
Percentage (%)
This column displays percentage wise total number of rejected
BT per category.
4.3.7 Aadhaar Authentication Response by Business Transaction Report
This report facilitates you to view 4.3.7 Aadhaar Authentication Response by Business Transaction
report. The Report contains the below listed fields:
S. No
Field Name
Explanation
1.
Response category
This column displays response category of authentication i.e.
successful, biometric mismatch and other errors.
2.
Response Error Code
This column displays error code for each reject type category
and “Yes” for each success type response category.
3.
Number of Business transactions
This column displays BT response category for the period
selected.
Auth Portal User Manual
Version 1.0
39
S. No
Field Name
Explanation
4.
Percentage
This column displays percentage of the each BT category.
4.3.8 Rejected Authentication Transaction Report
This report facilitates you to view Rejected Authentication Transaction report. Click on the below icon to
view the report:
Rejected_Authentica
tion_Transaction_Report.pdf
The Rejected Authentication Transaction report contains the below listed fields:
S. No
Field Name
Explanation
AUA Name
This column displays AUA Name.
1.
Enrolment Reference ID
2.
Transaction ID
3.
Age
4.
This column displays Enrolment Reference ID of the UID for
which authentication was rejected.
This column displays the Transaction ID of the rejected
transaction.
This column displays the Age of the UID Holder getting
authenticated.
5.
Gender
This column displays the Gender of the UID Holder getting
authenticated.
6.
Match Score
This column displays Match score of the UID Holder in case of
Biometric authentication transaction else it remains blank.
8.
Error Code
This column displays error code generated during rejected
authentication transaction.
9.
BFD
This column displays BFD status of UID Holder; It will display 1
if BFD is done 0 if BFD is not done.
10.
Date and Time
Auth Portal User Manual
This column displays Date and time of the authentication
Version 1.0
40
S. No
Field Name
Explanation
transaction.
11.
Terminal ID
12.
Pin code
This Column displays terminal id of the device used for
authentication.
This Column Displays Pin code of the device.
4.3.9 AUA Wise Rejected Analysis for Multiple Finger Authentication Report
This report facilitates you to view AUA Wise Rejected Analysis for Multiple Finger Authentication Report.
Click on the below icon to view the report:
AUA_Wise_Rejected
_Analysis_for_Multiple_Finger_Report_1381467310685.pdf
The AUA Wise Rejected Analysis for Multiple Finger Authentication Report contains the below listed
fields:
S. No
Field Name
1.
AUA Name
This column displays AUA Name.
2.
ASA Name
This column displays Enrolment Reference ID of the UID for
which authentication was rejected.
3.
Unique UIDs
4.
Accepted Authentication
5.
Accept %
6.
SUT Error code 300
This column displays the SUT Error code 300.
8.
SLT Error Code 300
This column displays the SLT Error code 300.
9.
MUT Error code 300
This column displays the MUT Error code 300.
10.
MLT Error Code 300
This column displays the MLT Error code 300.
Auth Portal User Manual
Explanation
This column displays unique UIDs.
This column displays the Accepted Authentications.
This column
authentication.
Version 1.0
displays
the
percentage
of
accepted
41
4.3.10 District Wise Authentication Report (Monthly Report)
This report facilitates you to view District Wise Authentication Report for any month. Click on the below
icon to view the report:
District_Wise_Authe
ntication_Report.pdf
The District Wise Authentication Report contains the below listed fields:
S. No
Field Name
1.
District Name
2.
Total Unique Id
Accepted
3.
Rejected
4.
5.
Accepted Percentage
(%)
Explanation
This column displays District Name
This column displays Total unique ID authenticated for the selected month.
This column displays Total Unique IDs accepted during authentication for the
month selected.
This column displays display total unique IDs which were always rejected
during authentication for the month selected.
This column displays the success percentage district wise.
4.3.11 UDC wise Authentication Report (Monthly Report)
This report facilitates you to view UDC Wise Authentication Report for any month. Click on the below icon
to view the report:
UDC_Wise_Authentic
ation_Report.pdf
The UDC Wise Authentication Report contains the below listed fields:
S. No
Field Name
Explanation
1.
Location Type
This Column displays P to signify- Pin code and G to signify- Geography
depending on location information captured by device.
Auth Portal User Manual
Version 1.0
42
S. No
Field Name
Explanation
2.
Pin code
3.
UDC
4.
Total Unique UID
This column displays total Unique ID authenticated on the device for the
month selected.
5.
Accepted
This Column displays the total Unique ID accepted even once during
authentication for the month selected.
6.
Rejected
This column displays the total Unique ID always rejected during
authentication for the month selected.
This Column displays Pin code of the device used for authentication.
This Column displays UDC code of the authentication device.
Location Type
Display the accepted percentage UDC wise for the month selected.
8.
Accepted %
4.3.12 Device type wise Authentication Report (Monthly Report)
This report facilitates you to view ‘Device type Wise Authentication Report’ for the selected month. Click
on the below icon to view the report:
Device_Type_Wise_
Authentication_Report.pdf
The Device type wise Authentication Report (Monthly Report) contains the below listed fields:
S. No
Field Name
Explanation
1.
Device Type and
Code
This Column displays the FDC/IDC device code. In case
2.
Total unique ID’s
This Column displays Pin code of the device used for authentication.
3.
Accepted (%)
This Column displays UDC code of the authentication device.
4.4 Documents Repository
This section helps you to access the Document repository maintained by UIDAI to provide ready
information in terms of electronic documents for portal stakeholders.
The list of documents is listed below:
Auth Portal User Manual
Version 1.0
43












AUA/ASA On-boarding process documents and eligibility criteria.
AUA/ASA Registration Forms.
Frequently Asked Questions (FAQs).
Standards & Guidelines published by UIDAI.
Training modules, materials and presentations.
Reports on Fraud monitoring.
White papers, magazines, publications, news articles and PoC reports.
List of STQC Certified Devices to be used for Authentication.
List of approved device vendors for authentication.
Device brochures and related material.
Audit related reports for AUA/ASA reference.
Contact details of Live AUAs/ASAs etc.
The document repository is shown in the below snapshot:
Figure 20: Document Repository
Auth Portal User Manual
Version 1.0
44
5 Frequently Asked Questions
1. Who can become an AUA?
Department of Civil Supplies, which seeks to verify the identity of a target resident before issuing them
their monthly ration of rice, kerosene, etc.
Any bank / financial institution that seeks to verify the identity of its customer before letting them
complete a financial transaction such as withdrawal or transfer of funds.
The administration / security department of a high-security building/zone that seeks to verify the identity
of any individual seeking entry into the building/zone.
2. What are the hardware, software, and network requirements to use Aadhaar authentication?
High level hardware and software required for ASAs:



Server with software for processing authentication transactions coming from AUAs (processing
incoming transactions from AUAs, invoking Aadhaar authentication, auditing metadata along with
response).
Database for storing configurations/audits.
ASA network has two elements - connectivity from AUA servers to ASA and from ASA server to
CIDR via leased line.
Actual hardware details, sizing, and bandwidth requirements need to be based on the volume of
transactions processed. ASA is also suggested to deploy sufficient redundancy taking into consideration
the requirement of its operations.
3. How to become an AUA?
Key steps to be followed include:









Identify business / service delivery needs and select appropriate authentication types.
Fill online application form.
Engage with ASA(s).
Send signed contract and supporting documents to UIDAI.
Ensure process and technology compliance.
Plan device deployment.
Obtain approvals from UIDAI.
Carry out end-to-end testing.
Go-live.
4. How can an AUA use Aadhaar authentication services to seed Aadhaar in their database?
An AUA can request Aadhaar holders to provide their Aadhaar numbers, for seeding in the database,
before service delivery. An AUA can further verify the correctness of the Aadhaar numbers, so provided,
through demographic and/or biometric authentication of the Aadhaar holders.
5. Does AUA need to share any digital signature details with UIDAI?
Auth Portal User Manual
Version 1.0
45
Currently AUA is not required to share any digital signature/PKIs with UIDAI. UIDAI Authentication server
requires that public key be part of Authentication XML’s digital signature. However at a later point when
UIDAI portal allows uploading of public key, digital signature need not have the embedded public key,
instead it can be verified against the uploaded public key.
Refer to the Aadhaar Authentication API documentation for requirements of digitally signing of the request
XML in the authentication packet.
6. Are there any specific guidelines or requirements that an AUA need to take into consideration
while developing application for offering buffered authentication for AUA’s business
requirements?
Most of the time, when using buffered authentication, residents may not be present. So, authentication
failures need to be handled differently based on the business rules. Also, storage of authentication
packets during the buffering requires local storage on the device which needs to be planned. Notice that
PID block MUST BE “buffered” ONLY after encryption while using buffering. It is mandated that buffered
data is deleted immediately after sending it to CIDR for authentication.
7. Does a service delivery agency need to sign any contract / engage with any specific
organization(s) to post payments via APB?
The service delivery agency needs to engage with their bank to avail of APB. The bank in turn gets the
agency registered with NPCI.
8. What communication mechanism is required to have connectivity with ASA?
AUA may decide the communication mechanism with ASA. It is recommended that, for reliable and
secure transactions, dedicated network connectivity is used.
9. Will there be any encryption mechanism to secure AUA-ASA communication? If yes which
keys will be used?
It is left to AUA to determine the mechanisms to secure the AUA-ASA communication. Unless you are
already using a secure protocol, if you are looking to build something new, consider using SSL.
Auth Portal User Manual
Version 1.0
46
6 Definitions and Acronyms
6.1 Definitions
Authentication Service
Agency (ASA)
Aadhaar Authentication
Authentication User
Agency (AUA)
Terminal Devices
Authentication Factors
Auth Portal User Manual
ASA is an agency that has established secure leased line connectivity to the
Central Identities Data Repository (CIDR) to transmit authentication request
on behalf of Authentication User Agency (AUAs) and receive response back
from CIDR.
Aadhaar “authentication” means the process wherein Aadhaar Number,
along with other attributes, including biometrics, are submitted to the Central
Identities Data Repository (CIDR) for its verification on the basis of
information or data or documents available with it. UIDAI will provide an
online service to support this process. Aadhaar authentication service only
responds with a “yes/no” and no personal identity information is returned as
part of the response.
AUA is an agency that seeks to use Aadhaar Authentication by connecting to
the CIDR through an ASA. The AUA is the principal entity that drives
authentication requests to enable their services. Based on the result of the
authentication, the AUA determines whether or not to provide Aadhaarholders access to their services. Examples include Government
Departments, Banks, and other public or private organizations.
Terminal devices are devices employed by AUAs (both government and nongovernment) to provide services to the residents. Examples include MicroATM devices, POS devices, PDS terminals, and MGNREGA terminals.
These devices will host the applications of the AUA and have biometric
capture devices to capture biometrics of residents for authentication
purposes. Any additional features of these terminal devices would depend on
specific needs of services offered by AUAs.
Aadhaar authentication will support authentication using multiple factors.
These factors include demographic data, biometric data, OTP, or
combinations thereof. Adding multiple factors may increase the strength of
authentication depending on the factors. Applications using Aadhaar
authentication need to choose appropriate authentication factors based on
the application needs.
Version 1.0
47
6.2 Acronyms
ASA
Authentication Service Agency
AUA
Authentication User Agency
CIDR
Central Identities Data Repository
FP
Finger Print
GNDC
Greater Noida Data Centre
HO
Head Office
MSP
Managed Service Provider
OTP
One Time Pin
RO
Regional Office
SLA
Service Level Agreement
TAT
Turnaround time
UAT
User Acceptance Testing
UID
Unique Identification
UIDAI
Unique Identification Authority of India
Auth Portal User Manual
Version 1.0
48