I submitted a couple questions to this group yesterday about using two
DB's simultaneously -- using LDAP to pull up new user data to
pre-populate the add user/update user form, then a local database for
storeage.
Then I realized that the add/change screen might be the only place in
OTRS that the user database info is changed. If this is the case, I
could use the corporate read-only LDAP database and simply reprogram the
update user info button to direct the user to the official, corporate
LDAP maintenance web page.
When we try to log in with the OTRS backend set to LDAP, though, we can
authenticate but receive a message that there is no user data. It seems
that there's more going on behind the scenes than there appears to be at
first glance.
I figure very few companies give new OTRS admins write access to
valuable LDAP employee directories. I suspect my situation 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 list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support oder Consulting für Ihr OTRS System?
=> http://www.otrs.de/
