Confirmed users
483
edits
WebAPI/WebPayment: Difference between revisions
→Testing against the BlueVia Payment Provider
| Line 338: | Line 338: | ||
* Since the BlueVia Payment Provider is behind a Telefónica VPN, the first requirement is to get access to it. Unfortunately not everyone can get access to it and BlueVia should provide access to its dev servers under direct request. | * Since the BlueVia Payment Provider is behind a Telefónica VPN, the first requirement is to get access to it. Unfortunately not everyone can get access to it and BlueVia should provide access to its dev servers under direct request. | ||
* Apart from access to the BlueVia dev server you would also need the BlueVia dev server certificates, since B2G fails [https://bugzilla.mozilla.org/show_bug.cgi?id=769178 Bug 769178] when accessing some HTTPS urls that have a certificate signed by an unknown CA (like the BlueVia one). We should probably be adding it to Gaia by default at some point, but until then, you would need to install them. | * Apart from access to the BlueVia dev server you would also need the BlueVia dev server certificates, since B2G fails ([https://bugzilla.mozilla.org/show_bug.cgi?id=769178 Bug 769178]) when accessing some HTTPS urls that have a certificate signed by an unknown CA (like the BlueVia one). We should probably be adding it to Gaia by default at some point, but until then, you would need to install them. | ||
** If you are testing on a B2G device, you can simply run this [http://openwebdevice.com/blueviacerts/modifyCertDb.zip script] (just run <code>./modifyCertDb.sh</code>) which would install the certificates in the Gaia profile. | ** If you are testing on a B2G device, you can simply run this [http://openwebdevice.com/blueviacerts/modifyCertDb.zip script] (just run <code>./modifyCertDb.sh</code>) which would install the certificates in the Gaia profile. | ||
** Unfortunately, there is not an automatic script for the B2G-desktop environment, and the certificate instalation requires the following steps: | ** Unfortunately, there is not an automatic script for the B2G-desktop environment, and the certificate instalation requires the following steps: | ||
*** From the shell that you are going to run B2G desktop do | *** From the shell that you are going to run B2G desktop do <code>export NSS_DEFAULT_DB_TYPE=sql</code> | ||
*** Remove the <code>key3.db</code> and <code>cert8.db</code> files from your Gaia profile root. | *** Remove the <code>key3.db</code> and <code>cert8.db</code> files from your Gaia profile root. | ||
3. Run B2G via | 3. Run B2G via <code>./b2g -profile <path-to-gaia-profile></code> | ||
4. Open an HTTPS web page from the browser app. | 4. Open an HTTPS web page from the browser app. | ||
5. Close B2G desktop. | 5. Close B2G desktop. | ||