New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AD Login failed / No DN found for <blank> on <FQDN of DC> #14380
Comments
Please revise your login filter. |
Thanks for the suggestion, I've been working on this. If I run an ldapsearch from the console I get the required result: `ldapsearch -h pdc.company.com -D cn=adlookup,cn=Users,dc=company,dc=com -W "(&(objectclass=person)(samaccountname=user1))" samaccountname LDAPv3 User1, CompanyUser, company.com However I am still getting the same error when trying to login.
I don't know if this is of worth, but the message "No DN found for on pdc.company.com" does not contain the username for which I'm trying to login with. I also have sAMAccountName under the Expert | Internal Username Attribute setting. |
I had this same issue until I changed my filters. My login filter is as follows:
My user filter and group filter are both:
The OID: Hope this helps |
@thefold can you also post your LDAP config? ./occ ldap:show-config run as web user from command line outputs it all nicely. |
I changed my filters as per samicmalone's suggestion but I'm still not able to login. The DN errors have disappeared, but I still get login failed messages.
|
I have the same problem: Owncloud version: 8.0.4 I changed several times the login filter, the group filter, etc, but no login allowed at all, just for the local accounts. Any helps? |
Do you have the PHP module mbstring installed? |
Possible duplicate of #16654 |
Thanks blizzz for the fast answer. Yes, the module is already installed and i'm checking the other report you posted. Thanks again. I'll post it if I resolve the problem with the other report. |
I changed the login filter Thanks! |
@tdaniel555 glad it works for you now. @thefold @samicemalone you still have that issue? |
Hello. I have same error when upgrade from working 8.0.4 to 8.1.4: {"reqId":"zyEsxWKfClGVXIHxqv0v","remoteAddr":"192.168.58.147","app":"PHP","message":"session_name(): session.name cannot be a numeric or empty '5348105571144' at /var/www/html/owncloud/lib/private/session/internal.php#42","level":3,"time":"2015-11-10T06:15:29+00:00","method":"POST","url":"/owncloud/"} {"reqId":"1R/NJx1nBjtpXitEiezd","remoteAddr":"192.168.58.147","app":"PHP","message":"session_name(): session.name cannot be a numeric or empty '5348105571144' at /var/www/html/owncloud/lib/private/session/internal.php#42","level":3,"time":"2015-11-10T06:15:29+00:00","method":"GET","url":"/owncloud/index.php/core/js/oc.js?v=954ef50c4dd62045cc750ed3d5389a51"} {"reqId":"1R/NJx1nBjtpXitEiezd","remoteAddr":"192.168.58.147","app":"user_ldap","message": "No DN found for on 192.168.1.136","level":0,"time":"2015-11-10T06:15:29+00:00","method":"GET","url":"/owncloud/index.php/core/js/oc.js?v=954ef50c4dd62045cc750ed3d5389a51"} But syncing all users from LDAP working normally: {"reqId":"GkeiYBpFnw+8wWZ17Ey1","remoteAddr":"","app":"user_ldap","message":"readAttribute: uid=adok,ou=people,dc=su found","level":0,"time":"2015-11-10T06:15:03+00:00","method":"--","url":"--"} I tried upgrade to 8.2.0, but have same error in log file. LDAP config:
CentOS 6.7 |
@neonman63 this issue has not seen an update since June, at the last one before was that it was got working. Given your log snippets it does not seem to be related. Please open a new bug report using the issue template. Therefore I am also closing this issue. |
Environment:
Owncloud 8.0.0 (also daily for 19/02/2015)
RHEL 6.6 x86_64 (fully patched)
httpd: 2.2.15
php: 5.4
SSL configured with self-certified certificate
Active Directory Functional Level: 2003
I have managed to configure AD authentication and users show in the User list, as do groups and group membership. However when trying to login I get the following messages every time. This occurred both with and without the SSL validation.
{"reqId":"OwkBrUEFR2KLu9D96ELU","remoteAddr":"172.16.0.162","app":"core","message":"Login failed: 'username' (Remote IP: '172.16.0.162', X-Forwarded-For: '')","level":2,"time":"2015-02-19T14:38:50+00:00","method":"POST","url":"\/index.php\/apps\/files_encryption\/ajax\/getMigrationStatus.php"} {"reqId":"P1Ge2KSd2sdm0FuFsxwH","remoteAddr":"172.16.0.162","app":"user_ldap","message":"Turned off SSL certificate validation successfully.","level":0,"time":"2015-02-19T14:38:51+00:00","method":"POST","url":"\/"} {"reqId":"NRL9\/kyB7CwC\/U4LDXKd","remoteAddr":"172.16.0.162","app":"core","message":"Login failed: 'username' (Remote IP: '172.16.0.162', X-Forwarded-For: '')","level":2,"time":"2015-02-19T14:38:51+00:00","method":"POST","url":"\/"} {"reqId":"zasRfkH2gerwngm9vdp0","remoteAddr":"172.16.0.162","app":"user_ldap","message":"No DN found for on pdc.company.com","level":0,"time":"2015-02-19T14:38:51+00:00","method":"GET","url":"\/index.php\/core\/js\/oc.js?v=7fb8145fb09d2483870c1eac230d56c0"}
The text was updated successfully, but these errors were encountered: