No authentication

[voxpupuli]

No authentication

[DavidJFelix]

@insonifi I'm taking a look into this now.

Many web-login mechanisms require that you post to a login url to retrieve a session cookie then maintain and provide that session cookie in subsequent requests to prove that you are logged in. Adding this type of login functionality would likely be a very large change, but is possible.

Without migrating to powershell 3.0 mechanisms (and abandoning old platforms) we may be able to utilize the WebClient UploadString method to push login credentials to a login url, prior to using DownloadFile to actually retrieve the resource.

The above assumes that this is a traditional web login with session cookies mechanism, as this is common for build servers. An easier solution is available if the server you're authenticating with is able to accept basic authentication (Here is a test page to show you what basic authentication looks like) then what I can use the WebClient Headers.add method to put an "authentication" header with a value of "Basic <%= @authkey %>" and set @authkey to be `Stdlib::Base64("${username}:${password}").

I'm currently working on making puppet-download_file a bit more powerful and more platform agnostic (by possibly leveraging wget and curl for OSX/Linux). I'll keep you up to date on my efforts if you're still looking for a solution. I know March to November is a long wait, so this might not even be relevant.