Titanium JIRA Archive
Appcelerator Community (AC)

[AC-404] HTTP Digest Authentication (NTML) breaks on iOS 8.3

GitHub Issuen/a
TypeBug
Priorityn/a
StatusResolved
ResolutionHold
Resolution Date2015-11-29T08:54:22.000+0000
Affected Version/sn/a
Fix Version/sn/a
ComponentsTitanium SDK & CLI
Labelsios, triage
ReporterJeff Bonnes
AssigneeShak Hossain
Created2015-04-20T02:23:44.000+0000
Updated2015-11-29T08:54:22.000+0000

Description

Since upgrading devices to iOS 8.3, NTML authentication no longer works. I have attached a simple app.js file that illustrates the issue. I've given the password to Ingo to add as a private comment. This code works on iOS 8.2, but does not work on iOS 8.3. I've also attached Charles proxy output that shows the conversation between the server and app in both iOS versions. With iOS8.2: - the app makes a request to the server - The server responds with a 401 and qop="auth" string as expected - The app requests again with the Authorization: Digest header set - The server returns a valid response 200 With iOS8.3 - the app makes a request to the server - The server responds with a 401 and qop="auth" string as expected - The app requests again with the Authorization: Digest header set. However, the nc = 00000002 in the Authorization header. In iOS 8.2, nc=00000001 - The server returns a 401 with a stale=true param in the qop="auth" header.

Attachments

FileDateSize
app.js2015-04-20T02:23:44.000+0000928
CharlesProxy.txt2015-04-20T02:23:44.000+00003901

Comments

  1. Jebun Naher 2015-11-08

    Hello We tested this issue in our environment with the provided password. But we didn't get any success or error message after running the app. The app keeps showing a loading indicator after clicking on the button. [Screenshot](http://postimg.org/image/5ytf3d665/) *Testing Environment:* Appcelerator Studio, build: 4.3.3.201510212245 Appcelerator Command-Line Interface, version 5.0.4 Ti sdk: 5.0.2 GA Mac Osx: 10.9.5 *Test Case:* Provided by the reporter. Thanks
  2. Jeff Bonnes 2015-11-24

    Password has changed since this was reported. I will review the code and update to the latest SDK to confirm that it is still happening.

JSON Source