The WebDav drive I am accessing, uses single-signon authentication.
It looks like it does not accept the syntax https://username:password@hostname/
Webdav_sync shows: Unauthorized
With other tools, I have no problems with the authentication. I think it would be useful if webdav_sync used a different way to specify the username and password.
Thanks,
Michael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
WebDAV-Sync currently only supports "Basic Authentication", which is safe when used with HTTPS. The authority syntax you are referring to is part of the standard URI syntax. You can also save the password by launching UIVI (http://www.re.be/uivi/) and connecting to the same URL.
What kind of single-signon system are you using?
Best regards,
Werner Donné
Pincette bvba
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A connection time-out is not related to logging in. When you don't provide a correct username/password you will get a response immediately. The time-out indicates a low-level network issue. The destination address and port exist but can't be reached. A firewall, for example, could cause this, or any other routing problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Given that I do not experience timeouts when using other clients, how can I diagnose the issue? I double-checked the URL. Could this be related to the spaces in the URL? See also the bug I logged.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm afraid I see no difference at all, except it now prints the text "null" instead of "The property is not available."
The remaining output is exactly as above.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The problem Michael had was that he ran the command-line on Windows in cmd. The %20 occurrences were interpreted as the second argument followed by "0". Since the second argument was empty this yielded "0" in the URL. The solution is to protect the URL from command-line argument substitution.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The WebDav drive I am accessing, uses single-signon authentication.
It looks like it does not accept the syntax https://username:password@hostname/
Webdav_sync shows: Unauthorized
With other tools, I have no problems with the authentication. I think it would be useful if webdav_sync used a different way to specify the username and password.
Thanks,
Michael
Hello Michael,
WebDAV-Sync currently only supports "Basic Authentication", which is safe when used with HTTPS. The authority syntax you are referring to is part of the standard URI syntax. You can also save the password by launching UIVI (http://www.re.be/uivi/) and connecting to the same URL.
What kind of single-signon system are you using?
Best regards,
Werner Donné
Pincette bvba
Hi Werner,
Thanks for the prompt reply. I will try UIVI. We are using Oracle SSO.
Thanks,
Michael
I tried UIVI. I can see that the password is stored correctly in file <user.home>/.be/re/net/URLAuthentication.
When I run the utility, I get this output:
Done.
java.lang.RuntimeException: java.net.ConnectException: Connection timed out: connect
I get the same message in UIVI, by the way.
A connection time-out is not related to logging in. When you don't provide a correct username/password you will get a response immediately. The time-out indicates a low-level network issue. The destination address and port exist but can't be reached. A firewall, for example, could cause this, or any other routing problem.
Given that I do not experience timeouts when using other clients, how can I diagnose the issue? I double-checked the URL. Could this be related to the spaces in the URL? See also the bug I logged.
You can run it as follows:
> java -Dbe.re.http.trace -Dbe.re.http.no-compress -jar …
This will write the entire HTTP-dialog on the terminal. You can then see what it actually does and where it gets the time-out.
Hmm, not getting a timeout now, but the message:
The property is not available.
The output is shown below:
Note that my directory was specified on the commandline as:
https://servername.acme.com/content/dav/st/Tea%20New%20Management/Documents/
Notice how the spaces (encoded as %20) display as 0 in the log. A bug?
I have released version 1.0.6. Can you try it with that?
I'm afraid I see no difference at all, except it now prints the text "null" instead of "The property is not available."
The remaining output is exactly as above.
I have same problem any solution ?
The problem Michael had was that he ran the command-line on Windows in cmd. The %20 occurrences were interpreted as the second argument followed by "0". Since the second argument was empty this yielded "0" in the URL. The solution is to protect the URL from command-line argument substitution.