I'm evaluating OTSR to possible replacement of our current, in-house
developed ticket system. I've printed and bounds the docs, studied them,
and based on what I've read therein and in this mail list, I have some
concerns about the way OTSR works versus how we'd like it to work.
Our current ticket
> I've started with customers; using the web frontend I configured
> everything, but customers can't login. They are taken back to the login
> screen with "Panic! No UserData!!!", while the server log shows:
>
> Any ideas?
I get that error when I set my DB to an LDAP backend which I do not have
tuation is not unique.
How has anyone else confronted with this situation solved this problem?
(I mean, besides disregarding LDAP altogether and entering user data
manually to a local SQL database.)
TIA,
Richard Petty
Austin, Texas
___
OTRS mailing
I'm evaluating OTSR.
One of the things we hoped to be able to do is leverage our read-only LDAP
employee directory to populate fields when creating new customer accounts
that will live on a local MySQL DB. It doesn't look like this is possible.
I'd even be interested in storing the customer-user
I got OTRS going just before a long holiday weekend. I'd logged in as
[EMAIL PROTECTED] with a password of "root", just as the docs say.
I edited a copy of my Config.pm file to use LDAP and had no problems with
the new functionality.
When I returned to work this morning, the session had expired a
