OIDC Field mapping issues

Technical assistance
1

Infos:

  • Used Zammad version: 6.5.0
  • Used Zammad installation type: docker-compose
  • Operating system: ubuntuL24.04
  • Browser + version: chrome 139

Expected behavior:

  • Custom fields are mapped correctly

Actual behavior:

  • By grabbing the token, I can find that the custom field content has been mapped. I also created the company field in zammad, but it seems that zammad cannot handle the mapping correctly by itself.

oidc:{“sub”:“741e484c-62f5-4da6-9f7f-e6c23d1cad82”,“email_verified”:false,“name”:“test test",“company”:“aaa”,“preferred_username”:“test”,“given_name”:“test”,“locale”:“zh-CN”,“family_name”:“test”,“email”:"test@test.com”}

image
image839×141 7.95 KB

i add the custom text company
image
image850×529 13.8 KB

Steps to reproduce the behavior:

2

Currently, only specific fields are mapped (e.g. firstname, lastname, email, image). So it’s working as designed and more feature request (which is already on our board): User attributes mapping and role mapping with third-party authorization (e.g. SAML) · Issue #4943 · zammad/zammad · GitHub

3

thanks for reply, we use docker-compose repo ; seems version be older than the main zammad repo

4

You’re expected to keep the compose repo files and tag versions up to date. This doesn’t happen automatically.