Skip Menu |
 

This queue is for tickets about the RT-Extension-LDAPImport CPAN distribution.

Report information
The Basics
Id: 83053
Status: new
Priority: 0/
Queue: RT-Extension-LDAPImport

People
Owner: Nobody in particular
Requestors: tsibley [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.33_02
Fixed in: (no value)



Subject: Comparing LDAP values with truncated RT values leads to history bloat
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 588
Download (untitled) / with headers
text/plain 588b
LDAP values longer than the RT field length will be truncated upon update. Afterwards, all subsequent comparisons to see if the field needs to be updated from LDAP will indicate that LDAP has a new value since the length differs. The result, however, is that the same value ends up in the database once truncated, and user history is bloated. LDAP values should be truncated to the RT field length before being used for comparison. This information *should* be accessible via - Show quoted text
>_Accessible.
Refer to http://issues.bestpractical.com/Ticket/Display.html?id=22448 for an example.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.