- Used Zammad version: 5.2.3
- Used Zammad installation type: Debian package
- Operating system: Debian 11
- Browser + version: Firefox, Chrome, Edge
- User first send an E-Mail to the Helpdesk, Zammad creates a user
- Users learn that Zammad has a nice Web UI and instead communicating via mail, they want to sign into Zammad, when they try using the Microsoft Sign-In Button they will be greeted with an error as described below.
- Using the Microsoft SSO they get the error: 422: The change you wanted was rejected. - Validation failed: Email address firstname.lastname@example.org’ is already used for other user."
- Send an e-Mail to a Mailbox/Channel monitored by Zammad
- User gets created with Login as their Mail address (and their Mail address as … their contact)
- Users want to use the MS SSO
If they first sign into Zammad via SSO, things work as their AAD ObjectID will be stored in Zammad as “Login”.
My question would be if we can tell Zammad to not use the Azure AD object ID as “Login”, but rather their e-Mail (if that can be reconfigured).