Users created with default_email_id=0

upcnet

Hello,

We're using osTicket v1.12.5 and have problems setting email address for users imported from LDAP automatically (using HTTP Pass Thru). On importing a user whose LDAP 'email' attribute is empty, osTicket creates it with default_email_id=0. Searching through Github, it seems that the issue had been addressed in https://github.com/plch/osTicket/commit/fc11184a3382abc4e47a1ebdfc206166cd6cd495 by throwing importError on bulk users import from CSV files, but using HTTP Pass Thru plugin still causes users to be created with default_email_id=0. We'we checked with version 1.15.0 and the same thing happens. This causes osTicket to give error when email is changed through UI (for users created with default_email_id=0).

Is this a known issue? Any workaround we can use to avoid having default_email_id set to 0?

Thanks

ntozier

You would want to create your users before they try to authenticate.

upcnet

The problem is I don't get to want what I want. The specification for the service is for us to be able to create users within osTicket instances upon first login (by a user) if that user is present in our corporate ldap server. That is why we use "HTTP Pass Thru" plugin. The problem is that some users don't have the attribute 'mail' populated (for whatever reason). It is when osTicket creates the user with default_email_id set to '0' (putting just the character "@" in the email form). It is only when we try to modifiy these users' emails that osTicket throws error.

We would just like to know if these is normal and we have to look for a workaround ourselves or it can be considered to be a bug? (osTicket should complain before inserting the user with invalid 'mail' parameter)

ntozier

osTicket Users are required to have [unique] email addresses.
So you will either have to:

give your users email addresses in LDAP/AD
create users with fake unique emails in osTicket prior to them logging in.

Even the 3rd party [paid] adSync Plugin will not get you around the requirement for users to have [unique] email addresses.

upcnet

ntozier Thankf for Your reply. We'll keep all that in mind. However, I do think osTicket should complain and not insert data into ost_users if email is not set. Currently, it inserts data in ost_users than it complains when one tries to modify them.

In any case, Your reply does answer my question. Thank You.

upcnet

Thinking again. Administrator should be able to modify data of a inserted user. If the field email contains '@' (just one character), osTicket won't let the Admin edit the user data (it just hangs in "Loading" state).