Hi,
I downloaded and installed OTRS 2.4.7 last year and it was running great. Recently I have upgraded it to v.2.4.9 and found there is a problem between the Customer (LDAP user) and Group.
I am using LDAP as the backend server for the customer users. It had been working perfectly. After the upgrading, the option to manage the customer users and group (both 1:n or n:1) is blank. There is no group or any customer user showing up while clicking on "Customer users <--> Groups". I did the upgrade from 2.4.7 to 2.4.9 on different Linux systems (CentOS 5.x), they are all the same.
The interesting thing is if I ignore it and upgrade to version 3.0.4 (or 3.0.5), the option will become normal. Means the customer users and groups will show after clicking "Customer users <--> Groups".
Could this be the problem with the upgrade procedure I went through? or just a bug happened on everyone?
Due to the customer's request, we have to keep at least one machine running under 2.4.9. Does anyone in this group experience the same problem?
Please suggest and your input will be greatly appreciated.
OTRS 2.4.9 Customer user (LDAP) w/ Group
Moderator: crythias
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: OTRS 2.4.9 Customer user (LDAP) w/ Group
2.4.9 has a problem with that interface. you can use the 3.0 interface file to *kinda* make it work.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Re: OTRS 2.4.9 Customer user (LDAP) w/ Group
Thanks crythias. It seems that we have to upgrade it to the new version (3.0.x) to prevent this bug.