Objects(created via console) not mapping ldap

  • Used Zammad version: 4.0
  • Used Zammad installation type: package
  • Operating system: Ubuntu 18.04


I’m somewhat trying to automate our Zammad setup so I’m mostly using the rails console to do the customization. Currently I’m trying to create objects via Console (which works fine with ObjectManager::Attribute.create - objects are editable/deletable in the UI) but if I want to use these custom objects for ldap mapping the debug_issue.rb script, which I found, tells me that the attribute couldn’t be matched. I restarted Zammad, did Cache.clear and so on but I don’t seem to get it working.

Did someone try something similiar or maybe has a hint which causes this problem?

PS: creating the objects via UI and using them is working as intended

If somebody runs into the same problem the solution was the least expected and easiest one.

Creating objects via console does work fine, issue was that the new object wasn’t created in the e.g. User table as a new column - took me way too much time to think about that :frowning:

If you’re unsure how to use the rails console I’d like to suggest to use the UI instead. Especially in terms of objects you can turn wrong and have hard times. Don’t forget the mandatory Zammad restart after.

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.