Skip to content
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

LDAP/LDAPS not working with AD after upgrade from 13.02 to 14.03 and again after 14.03 to 14.04 #11948

Closed
Der-Marc opened this issue Oct 20, 2018 · 4 comments
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap bug feature: ldap

Comments

@Der-Marc
Copy link

Steps to reproduce

  1. Cannot log in with AD user after upgrade, nothing changed at the AD (windows server 2016). AD user still valid. Checked connection with LDAP browser. Attached is the relevant part of the log:
    nextcloud.log

Any ideas what has changed? Kind regards
Marc

LDAP configuration (delete this part if not used)

| hasMemberOfFilterSupport | 1 |
| hasPagedResultSupport | |
| homeFolderNamingRule | |
| lastJpegPhotoLookup | 0 |
| ldapAgentName | CN=***,CN=Managed Service Accounts,DC=home,DC=intern |
| ldapAgentPassword | *** |
| ldapAttributesForGroupSearch | |
| ldapAttributesForUserSearch | |
| ldapBackupHost | |
| ldapBackupPort | |
| ldapBase | DC=home,DC=intern |
| ldapBaseGroups | DC=home, DC=intern |
| ldapBaseUsers | DC=home, DC=intern |
| ldapCacheTTL | 600 |
| ldapConfigurationActive | 1 |
| ldapDefaultPPolicyDN | |
| ldapDynamicGroupMemberURL | |
| ldapEmailAttribute | |
| ldapExperiencedAdmin | 0 |
| ldapExpertUUIDGroupAttr | |
| ldapExpertUUIDUserAttr | |
| ldapExpertUsernameAttr | |
| ldapGidNumber | gidNumber |
| ldapGroupDisplayName | cn |
| ldapGroupFilter | |
| ldapGroupFilterGroups | |
| ldapGroupFilterMode | 0 |
| ldapGroupFilterObjectclass | |
| ldapGroupMemberAssocAttr | uniqueMember |
| ldapHost | ldaps://192.168.145.10 |
| ldapIgnoreNamingRules | |
| ldapLoginFilter | (&(&(|(objectclass=user))(|(|(memberof=CN=OCuser,CN=Users,DC=home,DC=intern)(primaryGroupID=1618))))(samaccountname=%uid)) |
| ldapLoginFilterAttributes | |
| ldapLoginFilterEmail | 0 |
| ldapLoginFilterMode | 0 |
| ldapLoginFilterUsername | 1 |
| ldapNestedGroups | 0 |
| ldapOverrideMainServer | |
| ldapPagingSize | 500 |
| ldapPort | 636 |
| ldapQuotaAttribute | |
| ldapQuotaDefault | |
| ldapTLS | 0 |
| ldapUserAvatarRule | default |
| ldapUserDisplayName | displayname |
| ldapUserDisplayName2 | |
| ldapUserFilter | (&(|(objectclass=user))(|(|(memberof=CN=OCuser,CN=Users,DC=home,DC=intern)(primaryGroupID=1618)))) |
| ldapUserFilterGroups | OCuser |
| ldapUserFilterMode | 0 |
| ldapUserFilterObjectclass | user |
| ldapUuidGroupAttribute | auto |
| ldapUuidUserAttribute | auto |
| turnOffCertCheck | 1 |
| turnOnPasswordChange | 0 |
| useMemberOfToDetectMembership | 1 |
+-------------------------------+----------------------------------------------------------------------------------------------------------------------------+




@nextcloud-bot
Copy link
Member

GitMate.io thinks possibly related issues are #5247 (Sharing doesn't work after upgrading to 12.0), #11797 (Upgrade from 13.0.7 to 14.0.2 failed), #8694 (AD/LDAP sharing only in group not working.), #10520 (13.0.5 to 14 beta2 upgrade error), and #10905 (Trashbin is not working on android after RC upgrade).

@Der-Marc
Copy link
Author

Got it to work again with 14.03 by deleting the old configuration, disabling the plugin, enabling it again, using the same configuration information.
After upgrading to 14.04 LDAP is again broken. This time with the warning

Warning | user_ldap | Configuration Error (prefix s01): login filter does not contain %uid place holder. |
Warning | user_ldap | Configuration Error (prefix s01): No LDAP Login Filter given!

Trick from above does not work. Any hints?

Kind regards
Marc

@Der-Marc Der-Marc changed the title LDAP/LDAPS not working with AD after upgrade from 13.02 to 14.03 LDAP/LDAPS not working with AD after upgrade from 13.02 to 14.03 and again after 14.03 to 14.04 Dec 17, 2018
@blizzz
Copy link
Member

blizzz commented May 23, 2019

First log reports that the connection to the LDAP server failed.

Second output is a about a wrong login filter, this is typically logged on setup (when it is not set yet indeed).

Sounds to me rather that there are networking issues around the upgrade.

@skjnldsv skjnldsv added the 0. Needs triage Pending check for reproducibility or if it fits our roadmap label Jun 12, 2019
@skjnldsv
Copy link
Member

As there is no feedback since a while I will close this ticket. If this is still happening please make sure to upgrade to the latest version. After that, feel free to reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap bug feature: ldap
Projects
None yet
Development

No branches or pull requests

4 participants