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

limit ldap_dn columns to 4000 #31683

Merged
merged 5 commits into from Mar 30, 2022
Merged

limit ldap_dn columns to 4000 #31683

merged 5 commits into from Mar 30, 2022

Conversation

blizzz
Copy link
Member

@blizzz blizzz commented Mar 23, 2022

fixes #31681, satisfies #31679

Copy link
Contributor

@come-nc come-nc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You also need to change the check in AbstractMapping::map
And I do not think the migration step for existing data is correct. Incomplete dn in mapping is just broken mapping lines which will appear as remnants for users and ghost for groups.
These lines should be deleted I suppose? Or the migration should just fail and we consider this an invalid previous state.

Realistically the case should not appear as maximum dn length was 255 not long ago and I would not expect anyone using >4000 dn.

Ok so actually maybe it’s good to truncate the lines because it will allow the admin to use the remnant system to clean up users. And they can see what the dn was to know which entry is concerned.
So maybe leave it like this but log which entries have been truncated?

@blizzz
Copy link
Member Author

blizzz commented Mar 28, 2022

I got confirmation that the first commits unblocks update with Oracle for good.

@come-nc
Copy link
Contributor

come-nc commented Mar 30, 2022

I do not understand the checkers failure, was there a composer update or something?

@come-nc
Copy link
Contributor

come-nc commented Mar 30, 2022

/rebase

@come-nc
Copy link
Contributor

come-nc commented Mar 30, 2022

/rebase

blizzz and others added 5 commits March 30, 2022 14:43
- enlarging string cols from 255 to more than 4000 fails on default
  Oracle installations for invalid datatype conversion

Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
@come-nc come-nc merged commit 2bf0eff into master Mar 30, 2022
@come-nc
Copy link
Contributor

come-nc commented Dec 13, 2022

/backport to stable22

@come-nc
Copy link
Contributor

come-nc commented Dec 13, 2022

/backport to stable23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: reduce ldap_dn field to 4000 bytes
3 participants