The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not update the repository.
English
Include ticket data in response.
Define the route that should get mapped to this operation. Variables marked by a ':' will get mapped to the entered name and passed along with the others to the mapping. (e.g. /Ticket/:TicketID).
This field should be an integer number.
Here you can specify the maximum size (in bytes) of REST messages that OTRS will process.
Send Keep-Alive
This configuration defines if incoming connections should get closed or kept alive.
Endpoint
e.g https://www.otrs.com:10745/api/v1.0 (without trailing backslash)
The password for the privileged user.
URI of a proxy server to be used (if needed).
The user name to be used to access the proxy server.
The password for the proxy user.
Skip proxy servers that might be configured globally?
Show or hide SSL options to connect to the remote system.
The full path and name of the SSL client certificate file (must be in PEM, DER or PKCS#12 format).
The full path and name of the certification authority certificate file that validates SSL certificate.
e.g. /opt/otrs/var/certificates/SOAP/CA/ca.pem
The full path of the certification authority directory where the CA certificates are stored in the file system.
Controller mapping for Invoker
The controller that the invoker should send requests to. Variables marked by a ':' will get replaced by the data value and passed along with the request. (e.g. /Ticket/:TicketID?UserLogin=:UserLogin&Password=:Password).