Open q-wertz opened 2 years ago
Hi, please update to 24.0.9 or better 25.0.3 and report back if it fixes the issue. Thank you!
My goal is to add a label like e.g. 25-feedback to this ticket of an up-to-date major Nextcloud version where the bug could be reproduced. However this is not going to work without your help. So thanks for all your effort!
If you don't manage to reproduce the issue in time and the issue gets closed but you can reproduce the issue afterwards, feel free to create a new bug report with up-to-date information by following this link: https://github.com/nextcloud/server/issues/new?assignees=&labels=bug%2C0.+Needs+triage&template=BUG_REPORT.yml&title=%5BBug%5D%3A+
Yes, still on 25.0.3
. Not sure if this is important: the user "admin_user" is not on LDAP but a local one
{
"reqId":"4yeOsXJoq1oWMFMpCPkx",
"level":3,
"time":"2023-01-23T15:54:19+00:00",
"remoteAddr":"141.58.121.86",
"user":"admin_user",
"app":"user_ldap",
"method":"POST",
"url":"/apps/user_ldap/ajax/wizard.php",
"message":"Attempt for Paging? ",
"userAgent":"Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/109.0",
"version":"25.0.3.2",
"data":{
"app":"user_ldap"
},
"id":"63ceae53bc7ac"
}
Just to confirm I understand: the error is logged and those errors appear in the UI, but everything functions normally? 🤔
Can you provide the output of occ ldap:show-config
? Feel free to sensor out your domain/identifying info - just make sure any matching entries are the same/etc.
EDIT: I also just noted you're using NGINX. Can you confirm the following two lines exist in your nginx config:
I suspect the telltale sign is that CLI test works, but not the web UI...
This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions.
Sorry, forgot to answer.
root@asterix:~# sudo -u www-data /var/www/nextcloud/occ ldap:test-config s03
The configuration is valid and the bind passed, but a simple search on the base fails. Please check the server base setting.
Just not sure to which field this relates... The Base DN
, Base User Tree
, Base Group Tree
, ...
(or it might come from the fact that we use LDAP Global Catalog?)
The config is:
+-------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Configuration | s03 |
+-------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| hasMemberOfFilterSupport | 1 |
| homeFolderNamingRule | |
| lastJpegPhotoLookup | 0 |
| ldapAgentName | CN=65574F13-674G-HF68-80F2-0050569B202E,OU=FuncUsers,OU=SIAM,DC=university,DC=de |
| ldapAgentPassword | *** |
| ldapAttributeAddress | |
| ldapAttributeBiography | |
| ldapAttributeFediverse | |
| ldapAttributeHeadline | |
| ldapAttributeOrganisation | |
| ldapAttributePhone | |
| ldapAttributeRole | |
| ldapAttributeTwitter | |
| ldapAttributeWebsite | |
| ldapAttributesForGroupSearch | cn |
| ldapAttributesForUserSearch | displayName;mail |
| ldapBackgroundHost | |
| ldapBackgroundPort | |
| ldapBackupHost | |
| ldapBackupPort | |
| ldapBase | DC=university,DC=de |
| ldapBaseGroups | DC=university,DC=de |
| ldapBaseUsers | DC=university,DC=de;DC=stud,DC=university,DC=de |
| ldapCacheTTL | 600 |
| ldapConfigurationActive | 1 |
| ldapConnectionTimeout | 15 |
| ldapDefaultPPolicyDN | |
| ldapDynamicGroupMemberURL | |
| ldapEmailAttribute | mail |
| ldapExperiencedAdmin | 1 |
| ldapExpertUUIDGroupAttr | |
| ldapExpertUUIDUserAttr | |
| ldapExpertUsernameAttr | |
| ldapExtStorageHomeAttribute | |
| ldapGidNumber | gidNumber |
| ldapGroupDisplayName | cn |
| ldapGroupFilter | (&(objectClass=group)(CN=ABC-*)(!(|(CN=ABC-CIFS*)(CN=ABC-OU*)(CN=ABC-DNS*)(CN=ABC-Administratoren)))) |
| ldapGroupFilterGroups | |
| ldapGroupFilterMode | 0 |
| ldapGroupFilterObjectclass | |
| ldapGroupMemberAssocAttr | member |
| ldapHost | ldaps://adserv17.university.de |
| ldapIgnoreNamingRules | |
| ldapLoginFilter | (&(objectClass=InetOrgPerson)(memberof:1.2.840.113556.1.4.1941:=CN=ABC-service-nextcloud,OU=ABC-services,OU=ABC,OU=Fak-42,DC=university,DC=de)(|(sAMAccountName=%uid)(mail=%uid))) |
| ldapLoginFilterAttributes | |
| ldapLoginFilterEmail | 0 |
| ldapLoginFilterMode | 0 |
| ldapLoginFilterUsername | 1 |
| ldapMatchingRuleInChainState | available |
| ldapNestedGroups | 1 |
| ldapOverrideMainServer | |
| ldapPagingSize | 0 |
| ldapPort | 3269 |
| ldapQuotaAttribute | |
| ldapQuotaDefault | |
| ldapTLS | 0 |
| ldapUserAvatarRule | none |
| ldapUserDisplayName | displayname |
| ldapUserDisplayName2 | mail |
| ldapUserFilter | (&(objectclass=InetOrgPerson)(memberof:1.2.840.113556.1.4.1941:=CN=ABC-service-nextcloud,OU=ABC-services,OU=ABC,OU=Fak-42,DC=university,DC=de)) |
| ldapUserFilterGroups | Domänen-Admins |
| ldapUserFilterMode | 0 |
| ldapUserFilterObjectclass | inetOrgPerson |
| ldapUuidGroupAttribute | auto |
| ldapUuidUserAttribute | auto |
| turnOffCertCheck | 0 |
| turnOnPasswordChange | 0 |
| useMemberOfToDetectMembership | 1 |
+-------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
I have the same issue, but running on apache2. Described it in the nextcloud forums, not solved (yet).
https://help.nextcloud.com/t/attempt-for-paging-bad-search-filter/185970
still present in 29.0.3, seems to be related if LDAP - server has a inactivity timeout set.
⚠️ This issue respects the following points: ⚠️
Bug description
In the admin logging I get the Error "Attempt for Paging?" from the
user_ldap
app.Not sure if related, but the LDAP/AD integration interface says
Configuration incorrect
and thatThe Base DN appears to be wrong
but when checking on command line everything appears to be correctUsing google I stumbled into this https://github.com/owncloud/user_ldap/issues/423 which seems related.
Steps to reproduce
Expected behavior
Installation method
Manual installation
Operating system
Debian/Ubuntu
PHP engine version
PHP 7.4
Web server
Nginx
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Updated to a major version (ex. 22.2.3 to 23.0.1)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
We are using Global Catalog (port 3269)