Aadhaar authentication ecosystem has a provision wherein any agency seeking to conduct Aadhaar authentication of its customers/associates etc. for service delivery can engage with an existing AUA (Authentication User Agency). Any agency, which enters into an agreement with AUA is defined as sub-AUA. Any agency seeking to become an AUA directly needs to draw up an agreement with UIDAI.
Authentication Service Agency (ASA) - ASA is any entity that transmits authentication requests to the CIDR on behalf of one or more AUAs. ASA act as enabling intermediaries. They have an established secure connection with the CIDR and convey AUA's authentication requests to the CIDR. ASAs receive CIDR's response and transmit back the same to the AUAs.
An ASA may enter into a formal contract with AUAs. UIDAI has a set of proposed guidelines that may be included in the contract between an ASA and an AUA. However, any contract (and commercial terms, if any) between an ASA and AUA is at the sole discretion of the signing parties, and UIDAI does not have any obligations regarding same.
Department AUA on-boarding process
e-Pramaan as an AUA and ASA
- e-Pramaan plays the role of ASA and AUA at once, thus preventing hassles for a department in submitting application forms to UIDAI, signing agreements and setting up the IT infrastructure. e-Pramaan eliminates the need for departments to become AUAs.
- Owing to e-Pramaan's is centralized framework and adherence to standards, there is a need for one-time compliance instead of different departments complying separately.
- Value added services such as exception handling, reporting and fraud monitoring are provided to departments.