GitLab

This contains the work-in-progress 4.2 instructions.
Also bumps our copyright.

pod tests should never be run by an end user (especially the failing
ones) and letting end users try to create/drop test databases is a
recipe for failure (especially if run from the cpan client).

Write up docs on how to run tests in case you're developing.

So callbacks get reliable set in 'result' argument.

allows to convert members or do other things

How callbacks were called before was completly useless -
no context and ldap attribute expected not computed value.
It's hardly backwards incompatible change as there was no
good reason to use them.

Drop flattening nested arrays in maps. Only one level deep
arrays are supported now.

New callbacks are called with enough context to change almost
everything and should return computed value.

Net::LDAP::Server::Test 0.16 requires that the base DN exist or it
throws an "Object not found" LDAP error.  Tests now pass under this
version.

This reverts commits 22b0995c and
dbdc867b.

RT::Authen::ExternalAuth is switching to ->Update as well, which lets us
use ->Update here without the waffling problem described by 22b0995c.
Using more core code is better.

Update method does s/\r\n/\n/g on values. This change
of values is not visible, but if combined with ExternalAuth
can result in regular change of a field back and forth.

The original code from 56d0d416 only stands a chance at working on RT
3.6.  RT 3.8 and 4.0 use the modern config handling and call
RT->Config->Get('Plugins') to load plugins.  Get() doesn't read values
from the RT:: namespace; it uses a secondary store which we never
affected.  By calling Set() ourselves we ensure the config is properly
updated and seen by the subsequent RT::Init() call.

It's not easy to exclude numeric users/groups with an LDAP filter,
leaving no way of acknowledging and suppressing the warning.  Rather
than add an option, just lower the log level.

While debugging it's helpful to see what was skipped, but under normal
usage (i.e. from cron), you want to ensure you see meaningful errors and
warnings not the same ones every night.