Damn this still isnt working for my users. I ran both of the posted scripts Tim posted up and its still not letting anyone in.

Forgot ...

Isn't it typical; even though an account is marked as an administrator, it isn't really ,,,!

For IE 11, you need to run it as administrator and the install button will magically appear. Start menu > Internet explorer > right click run as administrator

.. and therein lies a problem; my Windows 7 installation users IE11, and there's no 'install'.

Using Internet explorer 10, browse to

https://yourdomain/owncloud

Accept the self-signed certificate warning, click the 'certificate error' in the address bar on the right hand side. Click view certificates > install certificate. Then go through the wizard but choose specific store location to install (don't let it automatically guess), and select trusted root certificates.

You can check with the 'certmgr.msc' snap-in first?

Out of curiosity, where did you 'acquire' the server certificate from? I thought I'd already done so, but as it's still complaining, I want to duplicate the steps you took on my system.

I eventually managed to connect via Windows7 explorer using WebDAV. i made the registry change, imported the webserver certificate into the trusted root certificates, and then connected using only the hostname... for some reason it didn't like using the FQDN

net use X: https://hostname/owncloud/remote.php/webdav /user:user1 password1

Looks like it's an SSL negotiation issue with Windows 7. IE has better TLSv1.2 support than the legacy WinHTTP code which is only SSL or TLSv1.0. You'll need to import your servers certificate into your trusted root certificate authorities (Start -> run -> certmgr.msc).
https://forum.owncloud.org/viewtopic.php?f=17&t=21656
https://forum.owncloud.org/viewtopic.php?f=23&t=11246&sid=6a27183e7ac9b73a77c777083138820b

Been there, done that
It gets as far as presenting a certificate and then fails (in the GUI), The command line map gives the 1244 error. It's possible to connect using IE and the same map command - that gves you the option to store the certificate (again!), but the 'map network drive' from Explorer doesn't. I think I've tried every possibility and - until I know otherwise - I think it's a Windows issue .. certainly Google is awash with people complaining that they can't get a webdav drive mapped. I haven't tried a Linux map yet, but CyberDuck works fine so long as the trailing '/' is specified.

I'll try and replicate it

Have you seen the following?
http://doc.owncloud.org/server/7.0/user_manual/files/files.html

I'm still getting a problem with Webdav access. I can connect using cyberduck or the owncloud desktop client, but not using Windows 7 network drive mapping (net use) - that still reports a 1244 and not authenticated.
The owncloud installation went through an upgrade, so I repeated your init-ldap command, but with the same effect.

OK, thanks, will patch the install to cope with this scenario, but more importantly did manually running the script fix your user login issue?

FYI the webconfig users are all stored in LDAP, so if the owncloud LDAP config is now updated you should be able to login. Don't forget to enable owncloud for the user first via the webconfig users menu

EDIT: our posts crossed, great! thanks for your feedback, have pushed the patched version to the build system

Oh and with the last command now it's working !!!
Thanks !

Yes https is enabled and here is the output of your last command:

Last login: Sun Jan 11 13:47:42 2015 from desk001.sipl.ca
[root@clearos ~]# /usr/clearos/apps/owncloud/deploy/initialize-ldap
Updating database LDAP settings
Updating database settings for external storage
[root@clearos ~]#

OK - thanks, do you by any chance have HTTPS only enabled? If so, I may have spotted an issue with the install script

Can you run the LDAP setup script instead (and post any output)?
/usr/clearos/apps/owncloud/deploy/initialize-ldap

I'm getting exactly the same report. My problem is no webdav access! (on Windows 7 - and yes, I've updated the BasicAuth reg entry.)

This is the outpu i got and i can access Owncloud web interface with no problem:

[root@clearos ~]# /usr/clearos/apps/owncloud/deploy/install
Updating privileges
Updating existing config.php with system database settings
Call to owncloud URL failed - is the webserver running? - rerun install
[root@clearos ~]#

Hi Patrick, yes sorry missed your reply to this post. Please re run the install script
/usr/clearos/apps/owncloud/deploy/install

And post the output here as it will help to identify why your ldap config is not working.
Thanks
Tim

Tim any news on my problem since i paid the 10$ for the apps and would be happy to get it to works like it's supposed to !

in fresh install dont install owncloud
when all is ok install
owncloud

the perimision por mail not work

Same problem here with a fresh install of Owncloud the option in enabled in the user properties but i'm unable to log in with the user only the built in admin user is working. Here is the output of my Owncloud version:

app-owncloud-core-1.3.6-1.v6.noarch
app-owncloud-extension-core-1.1.1-1.v6.noarch
owncloud-7.0.2-1.v6.noarch
app-owncloud-1.3.6-1.v6.noarch
owncloud-3rdparty-7.0.2-1.v6.noarch

I wonder when installing as if he had not installed as rpm by market palace, LADP is running

the instale.by, market palce not work
yum -e owncloud
yum install owncloud
and yum reinstall owncloud

Thanks Tim
When I get home from work Ill check those and post it

Owncloud was installed through the marketplace. It did update itself from the owncloud website but they were not able to access before that update.

Hi, that's not right the webconfig users should be able to access owncloud - sounds like the LDAP installation isn't configured properly

What version of Owncloud are you using? 'rpm -qa | grep -I owncloud'

If you have installed from the marketplace you can try rerunning the setup script with the following and post the output
/usr/clearos/apps/owncloud/deploy/install