-
Notifications
You must be signed in to change notification settings - Fork 187
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 backend for graph API doesn't handle binary UUID correctly #5815
Comments
First part of the fix is here: cs3org/reva#3767 Some additional changes are required in the graph service. Fix will come after the above PR is merged. |
rhafer
added a commit
to rhafer/ocis
that referenced
this issue
Apr 27, 2023
In Active Directories UUID attributes such as "objectGUID" use a binary syntax (oposed to the standard UUID syntax defined in RFC4530). This introduces a flag to enable support for binary UUIDs as the id for users and groups (similar to what the "users" and "groups" services already support) Fixes: owncloud#5815
rhafer
added a commit
to rhafer/ocis
that referenced
this issue
Apr 27, 2023
In Active Directories UUID attributes such as "objectGUID" use a binary syntax (oposed to the standard UUID syntax defined in RFC4530). This introduces a flag to enable support for binary UUIDs as the id for users and groups (similar to what the "users" and "groups" services already support) Fixes: owncloud#5815
rhafer
added a commit
to rhafer/ocis
that referenced
this issue
May 2, 2023
In Active Directories UUID attributes such as "objectGUID" use a binary syntax (oposed to the standard UUID syntax defined in RFC4530). This introduces a flag to enable support for binary UUIDs as the id for users and groups (similar to what the "users" and "groups" services already support) Fixes: owncloud#5815
rhafer
added a commit
to rhafer/ocis
that referenced
this issue
May 2, 2023
In Active Directories UUID attributes such as "objectGUID" use a binary syntax (oposed to the standard UUID syntax defined in RFC4530). This introduces a flag to enable support for binary UUIDs as the id for users and groups (similar to what the "users" and "groups" services already support) Fixes: owncloud#5815
rhafer
added a commit
to rhafer/ocis
that referenced
this issue
May 3, 2023
In Active Directories UUID attributes such as "objectGUID" use a binary syntax (oposed to the standard UUID syntax defined in RFC4530). This introduces a flag to enable support for binary UUIDs as the id for users and groups (similar to what the "users" and "groups" services already support) Fixes: owncloud#5815
github-project-automation
bot
moved this from In progress
to Done
in Infinite Scale Team Board
May 3, 2023
fschade
pushed a commit
that referenced
this issue
Jul 10, 2023
In Active Directories UUID attributes such as "objectGUID" use a binary syntax (oposed to the standard UUID syntax defined in RFC4530). This introduces a flag to enable support for binary UUIDs as the id for users and groups (similar to what the "users" and "groups" services already support) Fixes: #5815
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The IDP and the reva service allow to use binary encode UUIDs as the user/group ids (by setting
LDAP_GROUP_SCHEMA_ID_IS_OCTETSTRING="true"
,LDAP_USER_SCHEMA_ID_IS_OCTETSTRING="true"
andIDP_LDAP_UUID_ATTRIBUTE_TYPE=binary
. This is important as Active Directory's objectGUID attribute is encoded that way.Unfortunately the LDAP backend in graph is currently lacking support for handling those types of user ids. In order to support AD as a user backend we need to add LDAP_GROUP_SCHEMA_ID_IS_OCTETSTRING="true"
and
LDAP_USER_SCHEMA_ID_IS_OCTETSTRING="true"`support to the graph service.The text was updated successfully, but these errors were encountered: