Support digest authentication

[avisi]

Support digest authentication

[mitchelkuijpers]

I will investigate how to add support for digest authentication but it does not seem so hard. Thank you for your extensive Issue 👍

[mitchelkuijpers]

I have replaced the basic http client for request.js which should include support for digest authentication: ffd8208. I tried using jsDAV to test the authentication but the implementation does not seem to work correctly, so please try it out the new version 0.2.4 and let me know if the digest authentication works :)

[jfix]

Just upgraded to 0.2.4 to give this a spin. Unfortunately, there seems to be a problem with the handling of directories, with both the 'basic' and the 'digest' authentication schemes.

I have this directory structure that I'm 'watching' with Grunt:

src/
     test/
          ascript
     test.xqy
     test2.xqy

Here's what happens when I change the ascript file (or any other, for that matter):

>> File "src/test/ascript" changed.

Running "webdav_sync:default" (webdav_sync) task
starting webdav_sync
Searching for files in: src/**
>> Found 4 files, Start uploading files to http://admin:[email protected]:8887/
>> Unknown error while deleting a dir gave statuscode: 207
>> Unknown error while deleting a dir gave statuscode: 207
Warning: Task "webdav_sync:default" failed. Use --force to continue.

Aborted due to warnings.
Completed in 0.785s at Sun Nov 24 2013 17:49:08 GMT+0100 (CET) - Waiting...

I don't really understand why it's attempting to delete a directory ... The status code 207 is a WebDAV-specific success response. But in any case the directory is not created and the file it should contain doesn't exist either in the WebDAV location. At least, the behaviour is the same for digest and basic. ;-)

[mitchelkuijpers]

I have added this in the last commit to get more of a "synchronisation" behaviour. Is this behaviour a problem for you? Maybe this should be a configuration property..

[jfix]

I don't understand what you mean :( -- Currently I cannot use this grunt plugin because it throws errors when (in my mind) it shouldn't. Thanks (and happy new year).

[mitchelkuijpers]

@jfix Does digest authentication work for you? If it does we can close this issue.

[jfix]

Yes, I've just tried the latest version 0.2.7, using both basic and digest, and they both work. Great work! Bedankt!

[mitchelkuijpers]

Alstublieft!

[dviramontes]

For basic auth:
on the grunt task remote_path string

are you guys needing to do something like this ?:

remote_path: user + ":" + (new Buffer(pass).toString('base64')) + "@localhost:8080/blablah"

or can i just pass the password as a regular string ?

im hitting an authentication issue, just wondering if its something i'm doing wrong.

thanks guys

[jfix]

Hi,

my remote_path for testing looks like this:

remote_path: 'http://admin:[email protected]:8888/'

no need to base64-encode the password.

[dviramontes]

Hey Thanks @jfix
very helpful