Error 501 while using production certificate about aadhaarapi.net HOT 7 CLOSED

Try following the steps, and check if the issue still persists.

1. Firstly, test it with PreProduction keys, available on the UIDAI Developer website.

2. If not solved, recheck if you are using the correct UIDAI encryption key. Encryption key and signature key are different in production environment.

3. Try viewing the final XML in debug mode and manually compare the generated ci value with expiry date of the UIDAI encryption key, the ci identifier should be in the "YYYYMMDD" format.

4. If the problem still persists, contact Aadhaar technical team.

from aadhaarapi.net.

Hi Souvik

First of all, Thanks for the reply. See the code for Auth has this region known as Device to Agency and it was commented, shown below:
#region Device to Agency
// TODO: Wrap DeviceContext{T} into AUA specific protocol and send it to AUA.
// On Device Side:
// var deviceXml = deviceContext.ToXml();
// var wrapped = WrapIntoAuaProtocol(deviceXml);

        // On Agency Side:
        // var auaXml = UnwrapFromAuaProtocol(wrapped);

// var auaContext = new AuthContext();
// auaContext.FromXml(auaXml);
#endregion

I just uncommented deviceXml and found the xml going as device context as follows:

{

NbMR6W7u/9bukL5/6LLnGypU2O2CtUamqjVrQc92gP110CvDI+3vCwki+4GB5fl0N0z3YipYAR91hEo4CCqS3nHXhEQhV+UC9pH1Tq9TiUQHB+5uC6fI4EJgAS0ZCrAP2XqGYwhtHdM+ANkI5NdL6LFJZKwVhN8GMnLxfbphHFldtQJSJ94znR4vYepncPVerVdF4sNFW5s4sJ9xFfgQcD6UTM8OgadhHI7YnmEnB4FYwN628KSML4cmFBFux0Hs9wlmI5Hova1bXuvh12FDgIs0qTdAkT7a0O3y9XXJAfyi883WnIBJDAJg7haZhVfD4rqWzSOVxXx1o6iOtac66Q==
Uofe+M5yhH+CRNteaFGFEZd4nnfDXxOfT3yiH9XdBulTJ74beiSFjAIRHS/sYKe/Ia/qFEtLj0tMSxQFkggYplk8Ju9BQQ+Mlq0aQKOejZI=
3eP5wfunA5n0olDnZXNZYP4mmK4Nyq/+k54zUK2lboSeg6ku0kCj7KqUOnSaOCiM

}

Now there are few questions as 👍

1. why this code was commented .
2. when we try to uncomment and run it , it is unableto wrapauprotocol and then unwrap.

And still showing the same 501 error even after trying the latest production certificate and aua.p12 signature available at adhaar site.

Please help/guide. I will be thankful.

Thanking you
Himanshu Gehlot
[email protected]

from aadhaarapi.net.

Skey ci="20170227" goinhg this way

from aadhaarapi.net.

and value inside the tag is NbMR6W7u/9bukL5/6LLnGypU2O2CtUamqjVrQc92gP110CvDI+3vCwki+4GB5fl0N0z3YipYAR91hEo4CCqS3nHXhEQhV+UC9pH1Tq9TiUQHB+5uC6fI4EJgAS0ZCrAP2XqGYwhtHdM+ANkI5NdL6LFJZKwVhN8GMnLxfbphHFldtQJSJ94znR4vYepncPVerVdF4sNFW5s4sJ9xFfgQcD6UTM8OgadhHI7YnmEnB4FYwN628KSML4cmFBFux0Hs9wlmI5Hova1bXuvh12FDgIs0qTdAkT7a0O3y9XXJAfyi883WnIBJDAJg7haZhVfD4rqWzSOVxXx1o6iOtac66Q==

from aadhaarapi.net.

In case if your device need to send any extra information to the AUA, you may wrap the device XML in a device-AUA specific protocol and send it to AUA, AUA on the other side, may decode and get the final device XML. This is just an optional part, and the (Un)wrapFromAuaProtocol() needs to be implemented by you.

ALSO add one step to the troubleshooting steps:
5. Check if you are you using the correct API web address.

Remember, every parameter is different and secure in production environment: API web address, AUA/ASA license keys, encryption keys, digital signatures, Aadhaar numbers, etc.

If everything is working fine with the Staging and especially Pre-Production keys, then it should also work with Production keys, as the same code is running and generating the XML in same way. As this does not seem to point to a issue, we need to close it.

You may contact Aadhaar team for help in production environment.

from aadhaarapi.net.

Hi Souvik

How to contact Aadhaar Technical team as the only tollfree number they have provided is not responding. Please send if you have any lead.

Thanking you
Himanshu Gehlot

from aadhaarapi.net.

Please find the group mentioned below, there you will get various email addresses of technical team.
Aadhaar Authentication Discussions Group

Regards,
Souvik

from aadhaarapi.net.