Hi guys,
Does anyone know how does multiple customer backends work?
Let's suppose I have two backends. Will OTRS search for the customer in the first backend and, not finding, in the second? Or will OTRS search always in both of them?
Suppose I have the same customer in both backends. In the first backend I got customer fields "A", "B" and "C". And in the second backend I got customer fields "D", "E" and "F". Will OTRS merge those fields so I got all fields properly filled?
Thanks in advance!
Best regards!
How does multiple customer backends work?
Moderator: crythias
-
- Znuny expert
- Posts: 167
- Joined: 26 Nov 2014, 20:34
- Znuny Version: 6.3.4
- Real Name: Samuel Casimiro
- Company: Câmara dos Deputados
- Contact:
How does multiple customer backends work?
Samuel
Znuny 6.3.4 | OTRS 5.0.17
OS: Debian 11 | CentOS 6.5
Database: Postgres | Oracle 12.1
Number of agents: 450 | Number of customers: 20000 | Number of CIs: 30000
Znuny 6.3.4 | OTRS 5.0.17
OS: Debian 11 | CentOS 6.5
Database: Postgres | Oracle 12.1
Number of agents: 450 | Number of customers: 20000 | Number of CIs: 30000
Re: How does multiple customer backends work?
From my limited testing at one point, it searches first backend and stops if user is found.
OTRS 5.0.26 with ITSM, and FAQ module on CentOS 7 with MariaDB and Apache
Using LDAPS for customers and agents against Azure AD
Using LDAPS for customers and agents against Azure AD