A possible reason for such behavior is that you are using a modified Create User Web Interface form that does not contain the User Logon Name field. In such a case, when User Logon Name is not specified explicitly, the User Logon Name property is generated by Adaxes automatically basing on the Property Pattern for the User object. Since the value generation template for the property is set by default to %saAMAccountName% in the builtin User Pattern, the generated User Logon Name does not include the UPN suffix.
To remedy the issue, you need to modify the Property Pattern that is used for User objects. To do this:
- Open Adaxes Administration Console.
- In the Console Tree, Navigate to the Property Pattern that is used for User objects (by default, this is the builtin User Pattern) and select it.
- Double-click the User Logon Name property.
- In the Generate default value field, modify the template for the property to include the domain name, for example, %saAMAccountNamefirstname.lastname@example.org.
- Click OK and save the Property Pattern.
Another possible reason is that you use a certain script for username generation that sets only the User Logon Name (pre-Windows 2000) property (SamAccountName), but does not set the User Logon Name property. Or the script may set the User Logon Name property without the UPN suffix. An example of such a script is the script that adds a digit to the end of the username if it is not unique from our Validate/Modify User Input Using a Script Tutorial. If this is the case, you need to modify the script so that it sets the User Logon Name property correctly. If you need help with modifying the script, we can help you.