Zammad ticketing/helpdesk on Nethserver available

Having CSRF token issues at login… solution in simple… sort of, temporary:

We have to add the following line to /etc/httpd/conf.d/zammad.conf:

RequestHeader set X_FORWARDED_PROTO ‘https’
RequestHeader set X-Forwarded-Ssl on

But of course it will be overwritten at some point.

So I tried to make a custom template, but it looks like it won’t work in an additional VirtualHost block:
/etc/e-smith/templates-custom/etc/httpd/conf.d/zammad.conf/csrf

<VirtualHost *:443>
RequestHeader set X_FORWARDED_PROTO ‘https’
RequestHeader set X-Forwarded-Ssl on
</VirtualHost>

expand-template /etc/httpd/conf.d/zammad.conf

@mrmarkuz may you please add these lines to the <VirtualHost *:443> section in file
root/etc/e-smith/templates/etc/httpd/conf.d/zammad.conf/10main ?

Or is there any other way to add these inside the *:443 section?

Thanks in advance!

Info (point 2.1):

The linked thread:

1 Like

Thanks for pointing that out.

As a workaround you may overwrite the 10main template fragment just by copying it to templates-custom and edit it as needed for now.
I am going to add this to the module asap.

2 Likes

I added the lines to /etc/httpd/conf.d/zammad.conf to fix the CSRF token issue.

Please test the new module:

yum install http://mrmarkuz.goip.de/mirror/devtest/nethserver-zammad-1.0.0-5.ns7.noarch.rpm
signal-event nethserver-zammad-update

@mrmarkuz
i tried installing zammad with the settings here: https://wiki.nethserver.org/doku.php?id=zammad#zammad_installation

i have not been able to, i get errors, package not available

anyone check

2 Likes

please try again, I tested synapse and changed my firewall setting, sorry…

1 Like

installation works great

1 Like

how do i setup ldap on zamadd.

i have defined the bind password, as well as base DN.
as for the username, i have tried multiple, dont work.

which one works in this case?

@mrmarkuz
what is the current way of installing elastic search on nethserver, and having it work with zammad.

maojority of the instructions on the forum seem like they were work in progress at the time.

Thanks for testing!

Elasticsearch is part of the installation and should be connected to Zammad.

LDAP/AD is not implemented yet in the module.

well, i get the error, elastic search needs to be configured.
how can i achieve this?

I have to check, thanks for pointing out, here are the docs:

https://docs.zammad.org/en/latest/install/elasticsearch.html#set-up-elasticsearch

LDAP:
Works for me this way:

Given ad.mydomain.com is the domain:

Host: ldaps://nsdc-server.ad.mydomain.com
SSL: Yes
Base DN: DC=ad,DC=mydomain,DC=com
Bind User: ldapservice@ad.mydomain.com

well, makes sense maybe in your case.
@CptCharlesG i am using ldap and not ad. so cant seem to know what to input under bind user

if i can get the ldap to work, i would be happy, as thats one less password for users.

Did you try cn=ldapservice,dc=directory,dc=nh ?

https://docs.nethserver.org/projects/nethserver-devel/en/latest/nethserver-directory.html#service-accounts

1 Like

it worked.
so bind dn can also be used as bind user

i know you have alot you are working on at the moment.
did you mange to check why the elastic search is not installed as part of the install process?

Not yet, I’ll report as soon as I have something working…

1 Like

and Happy Birthday @mrmarkuz

4 Likes

This is fantastic news, well done sir. :clap::clap::clap::clap::clap:I am still running the very first one I did with your help without any issues.

1 Like