You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 27, 2021. It is now read-only.
Some LDAP properties like `uidnumber` and `gidnumber` are numeric. When an OS tries to look up a user it will not only try to lookup the user by username, but also by the `uidnumber`: `(&(objectclass=posixAccount)(uidnumber=20000))`. The accounts backend for glauth was sending that as a string query `uid_number eq '20000'` in the ListAccounts query. This PR changes that to `uid_number eq 20000`. The removed quotes allow the parser in ocis-accounts to identify the numeric literal.
Related:
- owncloud/ocis-accounts#68
- owncloud#28
Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de>
butonic
added a commit
to butonic/ocis-accounts
that referenced
this issue
Jul 24, 2020
Some LDAP properties like `uidnumber` and `gidnumber` are numeric. When an OS tries to look up a user it will not only try to lookup the user by username, but also by the `uidnumber`: `(&(objectclass=posixAccount)(uidnumber=20000))`. The accounts backend for glauth was sending that as a string query `uid_number eq '20000'` and has been changed to send it as `uid_number eq 20000`. The removed quotes allow the parser in ocis-accounts to identify the numeric literal and use the NewNumericRangeInclusiveQuery instead of a TermQuery.
Related:
owncloud/ocis-glauth#28owncloud/ocis-glauth#29
Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de>
butonic
added a commit
to butonic/ocis-accounts
that referenced
this issue
Jul 27, 2020
Some LDAP properties like `uidnumber` and `gidnumber` are numeric. When an OS tries to look up a user it will not only try to lookup the user by username, but also by the `uidnumber`: `(&(objectclass=posixAccount)(uidnumber=20000))`. The accounts backend for glauth was sending that as a string query `uid_number eq '20000'` and has been changed to send it as `uid_number eq 20000`. The removed quotes allow the parser in ocis-accounts to identify the numeric literal and use the NewNumericRangeInclusiveQuery instead of a TermQuery.
Related:
owncloud/ocis-glauth#28owncloud/ocis-glauth#29
Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de>
When running EOS the OS needs to look up the user by the numeric uid. This fails with the glauth ocis-accounts backend:
might be an ocis-accounts problem
server log
The text was updated successfully, but these errors were encountered: