aagaag
July 23, 2016, 6:32pm
1
Good morning. Our public website is protected by an IIS proxy server featuring basic authentication and SSL (port 443). Unauthenticated (port 80) queries are not served.
I have set up an IIS URL Rewrite rule (reverse proxy, similar to nginx proxy_pass) to rewrite https://iis.mypublicsite/cloud into http://owncloudlinuxserver.private.lan/owncloud . Note that the internal server is not protected at all.
This setup works well via web browser, but the desktop client fails as it does not know how to authenticate itself. Is there a known workaround?
Hi,
AFAIK you can’t use an additional basic auth as at least the status.php needs to be publicly available:
opened 12:26PM - 04 Jul 13 UTC
closed 09:27AM - 26 Nov 13 UTC
Needs info
This issue seems to crop up here and there, but the owncloud client fails to syn… c to an owncloud instance using HTTP basic auth. The failure message unhelpfully reads "Failed to connect to ownCloud, host requires authentication".
It has been claimed that this is due to owncloud itself not supporting basic auth, but this is actually misleading, since all the interfaces, i.e. webdav, caldav, etc., do work despite basic auth, and the web interface works with basic auth credentials out of the box. Moreover, using the "ocsync" CLI tool, I can sync folders just fine, so the issue must be with the GUI client.
So is this fixable after all, or does the GUI client use any other APIs which go beyond the interfaces used by ocsync?
aagaag
July 23, 2016, 7:58pm
3
Thank you for the clarification. I am really, really loathe of exposing an unauthenticated port to the internet, but it seems that there is no alternative if I want to use owncloud.
You could also try to see if it is possible to make the status.php reachable without basic auth. Maybe thats possible within the webservers config.