Zammad 3.5 is available

Dear Community,

we’re thrilled to announce the immediate release of Zammad 3.5.
This release solves security issues and brings long awaited features (see below).
We strongly encourage all users to update their installations as soon as possible.

A note before hand:
With the last release post on this community we were also asking you guys how you feel about redundant release information. The feedback within a month was that it’s better to have one fully featured news post instead of several places to look in. You can find the poll here.

Long story short?
This is the last release post I’ll be posting on this community board.

From now on, please stay tuned to our release notes on our website:

1. Security advisories

For your overview we’re listing all advisories here, click on the links to get a full description to learn about the scope.

CVEs currently are pending and will be updated as soon as available.

2. Changes

You can find the full changelog including bug fixes (3.4 to 3.5) here.

2.1 Data Privacy :wastebasket:

You’ll now find a new menu entry within the admin settings “Data Privacy”.
This allows you to remove users (yes users, so agents too!) together with the tickets their customer of.
If you remove an agent, this will reset the owner to “nobody” and not delete the ticket in question.

After removal, you’ll receive a full overview of what has been removed.

You can find a pre-QA version of the relevant documentation here:

As soon as we finished the QA, you’ll also find this in the documentation. :raised_hands:

2.2 :busts_in_silhouette: Agents now can be customers (sponsored)

Over the past many Zammad users had the problem that they couldn’t see the tickets they’re customer of, if the ticket was in a group that the agent account had no permission to.

With Zammad 3.5 you can now provide the “customer” role to your agent as well.
This will allow your agents to view their customer tickets no matter of the group they’re in.

If the ticket is in a group the agent has no access to the ticket view will feel exactly like it does for customers. Agents can’t change fields a customer has no access to. :partying_face:

Amazing, right?!

Our sponsors
This feature was sponsored by the following amazing companies, make sure to also drop them a “thank you”! :smirk:

Thank you very much, City of Dornbirn Hospital and EKHN (The Protestant Church in Hesse and Nassau)!

3. Technical notes :bookmark_tabs:

3.1 Ruby version

Please note that with Zammad 3.5 Ruby 2.6.6 is required. If you’re installing from docker or package, you can safely ignore this hint. Source code installations require ruby 2.6.6 to be available before upgrading.

3.2 Debian 8 EOL

As already mentioned on our last release post, we’ll be dropping support for Debian 8.0.
If you’re still using Debian 8, consider upgrading asap!

3.3 Changed API endpoints

Heads up for API users:
The endpoints for Tags and Ticket linking have changed!
Our Tag documentation for the API is already up to date:

Please keep in mind that some API libaries may not yet be ready for this change.
Upgrading Zammad may break the compatibility to them.

3.4 SSO changes

Note: This only affects the endpoint /auth/sso and mostly affects users that want to use e.g. kerberos like authentication.

Zammad now allows you to enable a SSO button.
It will redirect you to /auth/sso - you no longer have to “hack workaround” with cookies or sketchy redirects to that endpoint. :confetti_ball:

But: This also does something else…
Enabling “SSO” will enable the use of sso authentication. If the option is disabled within security, you can no longer use above mentioned endpoint!

If you’re interested in kerberos like SSO, you can find a pre QA version of the documentation here:

To enable SSO, go to “Security” and enable “Authentication via SSO”

3.5 Changes to your vHost

Because of advisory ZAA-2020-18 we strongly suggest adding a further line to your vHost configuration files as noted below (this is also noted in the advisory).

3.5.1 nginx users

Within the location / directive add

proxy_set_header X-Forwarded-User "";

to ensure your webserver no longer allows usage of above mentioned Header.

( see: )

3.5.2 apache2 users

Within Zammads virtualhost conf add

RequestHeader unset X-Forwarded-User

to ensure your webserver no longer allows usage of above mentioned Header.

( see: )

That’s it!

Happy hacking, folks!