944789 - Plomassy: User identification issue with MobileID

Status: RESOLVED FIXED

(Marketplace Graveyard :: Payments/Refunds, defect, P2)

Description

[jessica.kauffmann]

Attachment: PINfailMP.zip

Region code:
Device:
Connection:
Region code: Plomassy
Device: Inari 
Connection: Data
Phone number/MSISDN: (52) 5533858544/ (52) 5533414637
Language: English/ Spanish
Carrier: Movistar
Last 4 digits CC: N/A
Test App used: MarketPlace/ In-app.

Step to reproduce the failure:
1. Turn the cellphone on.
2. Go to "Settings".
3. Select "Cellular & Data".
4. Go to "Mobile Network".
5. Turn on "Data Connection".
6. Go to MarketPlace.
7. Search for a pricetier app.
8. Click the Pay button.
9. Login to MarketPlace.
10. Create a PIN.
11. Reconfirm the PIN.


Observed behavior:
From step 12, the PIN is not genrated and the purchase is not complete. The following message appears: "The syntax of the response from the remote server is incorrect, for example, the response content is incomplete or the response content cannot be parsed."
This behavior is reproducible in In-App.

Expected behavior:
The correct result it should be that the PIN is generated and the purchase is completed.

Comment 1

[Andy McKay]

Attachment: 2013-11-29-12-51-13.png

That's not a string in our code, is that something in Bango?

The http log (in the zip file) shows that its hitting Bango URLs at this point.

Comment 2

[jessica.kauffmann]

I cannot confirm that, because it does not allow us to complete the creation of the PIN. I never see the payment page.

Comment 3

[Tom]

More questions to understand further.

1. Did you receive an SMS?
2. Can you remember what the PIN was?
3. If you were on Data, why were you taken through the WIFI flow in the first place?

That doesn't look like an error from Bango but I will need more time for investigation.

Comment 4

[Tom]

Further investigation done by our DEV team. 

this is not our error, not our screen and as a result there nothing else we can do with it.

Comment 5

[jessica.kauffmann]

1. Did you receive an SMS? The SMS is received correctly and the code accepted when was written.
2. Can you remember what the PIN was? The was 1234
3. If you were on Data, why were you taken through the WIFI flow in the first place? I had to execute a chek in Data and then executed the tests in Wi-Fi.

Comment 6

[jessica.kauffmann]

Tom,the SMS is received when you execute the log in through Wi-Fi. When the PIN generation is execute through Data you do not arrive to that step.

Comment 7

[Andy McKay]

The ezboot log in the zip shows hits to: partners-api.bluevia.com, bango.info followed by a 500 error.

074509048[40404160]: http request [
1074509048[40404160]:   GET /id/?bango=1113330000000373796&register=n&p=bcid%3d59947970&mozUserId=marketplace.allizom.org:6b38b0b60c1891af15ba75a0440872e735865c3d0d29ec7d250271be6f4fa8a6 HTTP/1.1
1074509048[40404160]:   Host: bango.net
1074509048[40404160]:   User-Agent: Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0
1074509048[40404160]:   Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
1074509048[40404160]:   Accept-Language: en-US,en;q=0.5
1074509048[40404160]:   Accept-Encoding: gzip, deflate
1074509048[40404160]:   Cookie: bangoUserTracking=116220563332950
1074509048[40404160]:   Connection: keep-alive
1074509048[40404160]: ]
24168168[40404550]: http response [
24168168[40404550]:   HTTP/1.1 302 Found
24168168[40404550]:   Content-Type: text/html
24168168[40404550]:   Content-Length: 451
24168168[40404550]:   Location: http://bango.info/BLUEVIA/BLUEVIAIdentificationRequest.aspx?Bango=1113330000000373796&NetworkId=MEX_MOVISTAR&URLReferer=http%3a%2f%2fbango.net%2fid.aspx%3fbango%3d1113330000000373796%26register%3dn%26p%3dbcid%253d59947970%26mozUserId%3dmarketplace.allizom.org%3a6b38b0b60c1891af15ba75a0440872e735865c3d0d29ec7d250271be6f4fa8a6
24168168[40404550]:   Date: Fri, 29 Nov 2013 18:51:05 GMT
24168168[40404550]:   Server: Microsoft-IIS/6.0
24168168[40404550]:   Cache-Control: private
24168168[40404550]:   Set-Cookie: X-Mapping-bgapbelj=9F1C78FFC2BA2E0FBB6C8DA1A6928281; path=/
ASP.NET_SessionId=4lnv2j55kmel5j454biudkek; path=/; HttpOnly
X-Mapping-bgapbelj=9F1C78FFC2BA2E0FBB6C8DA1A6928281; path=/
24168168[40404550]:   X-AspNet-Version: 2.0.50727
24168168[40404550]: ]
1074509048[40404160]: http request [
1074509048[40404160]:   GET /BLUEVIA/BLUEVIAIdentificationRequest.aspx?Bango=1113330000000373796&NetworkId=MEX_MOVISTAR&URLReferer=http%3a%2f%2fbango.net%2fid.aspx%3fbango%3d1113330000000373796%26register%3dn%26p%3dbcid%253d59947970%26mozUserId%3dmarketplace.allizom.org%3a6b38b0b60c1891af15ba75a0440872e735865c3d0d29ec7d250271be6f4fa8a6 HTTP/1.1
1074509048[40404160]:   Host: bango.info
1074509048[40404160]:   User-Agent: Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0
1074509048[40404160]:   Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
1074509048[40404160]:   Accept-Language: en-US,en;q=0.5
1074509048[40404160]:   Accept-Encoding: gzip, deflate
1074509048[40404160]:   Connection: keep-alive
1074509048[40404160]: ]
24168168[40404550]: http response [
24168168[40404550]:   HTTP/1.1 302 Found
24168168[40404550]:   Content-Type: text/html; charset=UTF-8
24168168[40404550]:   Content-Length: 268
24168168[40404550]:   Location: http://partners-api.bluevia.com/mobileid/v1/owd01?x-ob=33403&Bango=1113330000000373796&BID=289335&BIDT=09d40051-c58e-4832-b7fd-6c7eaf80b968
24168168[40404550]:   Date: Fri, 29 Nov 2013 18:51:07 GMT
24168168[40404550]:   Server: Microsoft-IIS/8.0
24168168[40404550]:   X-Powered-By: ASP.NET
24168168[40404550]:   Cache-Control: private
24168168[40404550]:   Set-Cookie: X-Mapping-kcepobcd=2B25587F4255C0327F0EA923D92E4FBC; path=/
ASP.NET_SessionId=azegnalxpdzhsavjqbu3g2rj; path=/; HttpOnly
X-Mapping-kcepobcd=2B25587F4255C0327F0EA923D92E4FBC; path=/
24168168[40404550]:   X-AspNet-Version: 4.0.30319
24168168[40404550]: ]
1074509048[40404160]: http request [
1074509048[40404160]:   GET /mobileid/v1/owd01?x-ob=33403&Bango=1113330000000373796&BID=289335&BIDT=09d40051-c58e-4832-b7fd-6c7eaf80b968 HTTP/1.1
1074509048[40404160]:   Host: partners-api.bluevia.com
1074509048[40404160]:   User-Agent: Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0
1074509048[40404160]:   Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
1074509048[40404160]:   Accept-Language: en-US,en;q=0.5
1074509048[40404160]:   Accept-Encoding: gzip, deflate
1074509048[40404160]:   Connection: keep-alive
1074509048[40404160]: ]
24168168[40404550]: http response [
24168168[40404550]:   HTTP/1.1 500 Internal Server Error
24168168[40404550]:   Content-Type: text/html; charset=UTF-8
24168168[40404550]:   Content-Length: 356
24168168[40404550]:   Connection: Close
24168168[40404550]: ]

The 500 returns text/html. I'm concerned that we are doing http requests, not https ones and that we got a 500 back. I'm thinking that parsing that text/html is resulting in the error.

Comment 8

[Tom]

This is not a Bango issue. 

We are displaying the error passed to us by BlueVia because we do not have an appropriately mapped error message for this. 

You will notice form the logs that the last host is partners-api.bluevia.com not bango.

Comment 9

[Jorge Vila]

Hi,

after reviewing in the logs, we have not found any request for OWD that we answered as HTTP 500

on 29th November, we only found these two requests from OWD Mobile ID

2013/11/29T16:23:09.683 2013/11/29T16:23:10.289 04dd0506-7f0f-4832-9222-909bccad753c BE MobileId 1/50029 INFOSTATS 302 [{"MobileId":{"info":{"partnerName":"owd01","bidToken":"53eed95c91ee277a553b79d770b2rDfk","msisdnHeaders":{"value":"pJ8IsXlnEMKeFZotoaFPC8R0YnySyD1rKElKiK0f0PlpSIMvGKcr/oox8wkxMyiRezBC5hICeykIOvVt+0rkZg=="},"userAgent":"Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0","targetURL":"http://bango.info/BLUEVIA/BLUEVIAIdentification.aspx","mobileIdCorrelator":"df20c75c09c8834d21e71c25ad2f010d8a0fb607","xff":"176.77.138.106","contentType":null,"appProvider":"50098"}}}] 

2013/11/29T16:34:14.625 2013/11/29T16:34:15.388 e8f616ad-e149-4b69-9c7d-e1caff394751 BE MobileId 1/50029 INFOSTATS 302 [{"MobileId":{"info":{"partnerName":"owd01","bidToken":"53eed95c91ee277a553b79d770b2rDfk","msisdnHeaders":{"value":"pJ8IsXlnEMKeFZotoaFPC8R0YnySyD1rKElKiK0f0PlpSIMvGKcr/oox8wkxMyiRezBC5hICeykIOvVt+0rkZg=="},"userAgent":"Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0","targetURL":"http://bango.info/BLUEVIA/BLUEVIAIdentification.aspx","mobileIdCorrelator":"df20c75c09c8834d21e71c25ad2f010d8a0fb607","xff":"176.77.136.27","contentType":null,"appProvider":"50098"}}}]

There are only two requests.

Is this issue still happening? In such case, we could try to capture online.

Best
JORGE

Comment 10

[jessica.kauffmann]

Hi Jorge,

The problem was reproducible yesterday and today too. I'm working with Movistar 2G.

Comment 11

[Jorge Vila]

Hi Jessica,
could we do some online testing?

Do you use skype so we can sync?

Thank you
Jorge

Comment 12

[jessica.kauffmann]

My skype is: jesica.kauffmann

Comment 13

[eder]

Hi Jorge also is reproducible on 3G "geeksphone"

Comment 14

[Jorge Vila]

Hi,

we have tested with Jessica and Eder and Bluevia did NOT receive the mobile id request. 

Somewhere in the network the redirection is being blocked.

We checked that the IPs obtained by the devices are correct, and no traffic is reaching bluevia.

We will raise an issue with Movistar Mexico to trace it.

Best

Comment 15

[Jorge Vila]

Hi,

could you please retry now?

Traffic seems to flow again.

Best

Comment 16

[jessica.kauffmann]

In the Geeksphone (3G) and in the Inari (2G) the PIN was created successfully.

Comment 17

[krupa raj[:krupa]]

Closing the bug for verification based on comment 16.