Unable to Login - "Error 422"

Technical assistance
1

Infos:

  • Used Zammad version: Latest
  • Used Zammad installation type: apt package
  • Operating system: Debian GNU/Linux 12 (bookworm)
  • Browser + version: Firefox (Latest), Edge (Latest)

Expected behavior:

  • When I login using with email address (for a local account) or using the M365 integration, to be able to login

Actual behavior:

422: The change you wanted was rejected. 
Message from microsoft_office365: invalid_credentials. 

Maybe you tried to change something you didn't have access to.
  • When I login manually, I get the following (NOTE: I’ve disabled username and password field as people people ignored me when I said click on the M365 button, so I need to click on “Request the password login here” option).
StatusCode: 500. 
Error ID *random_string*: Please contact your administrator.

Steps to reproduce the behavior:

NOTE: To confirm, this set-up all appeared to be working on Monday, but I’ve had a couple of weeks off, and I’ve recieved notifications from the system on Monday (systemd timers) but when I came back to work on the Tuesday, I was unable to login. Nothing has been changed on the server, and then M365 intergration appears to be working just fine.

Please let me know what log files you need and I’ll get these uploaded ASAP.

2

Yes. Well, the Microsoft tenant credentials for the app are invalid / no longer valid.
I’m not sure what your question is to be honest.

3

Sorry, my question is how can I login. If the credentials are invalid, then I will need to re-authenticate within Zammad? The Tenant application is showing as functional and operational.

As for the credentials being invalid, I have access to the two accounts linked into Zammad, and either of those accounts passwords have changed. I can also see that the Zammad ticket system is actively connected and working through emails on the email it’s linked with - which if the credentials aren’t linked / invalid it wouldn’t be able to do?

4

Right, it’s not about the accounts credentials, that’s what I also hinted initially. Zammad never gets known the Microsoft account credentials, because the authentication happens on Microsofts end. The API credentials (application id, secret…) are not valid. That is the problem.