UPN not updating after setting up Property Patterns

Question

We are moving away from using the default domain for all user UPNs. I read a few support articles and configured a few property patterns to change the UPN based on the OU the user is in, however, on enabling the user account, it's still showing the default domain as their upn.

I made sure to delete the 'Username' property from the built in User Pattern, is there something else I'm missing?

Built in:

Users in 'CT OUs'

Username Properties for 'CT OUs'

Answer 1

Hello,

There is no need to create a new property pattern. You can update the User one or create multiple property patterns with different settings assigned over different locations if required. The following tutorial will be helpful: https://www.adaxes.com/help/ConfigureUPNSuffixSelection. According to your last screenshot, the property pattern in question is still configured to only use a single specific suffix and not allow selecting any other.

Comments

Alright, I'll take a look. Slightly unrelated, if I wanted usernames to generate as Uppercase FI, Uppercase First letter of lastname, what would I change this to be:

%firstname:lower,1%%lastname:lower%

---

Hello,

It would be %firstname:upper,1%%lastname:upper%. For detils about value references, see https://www.adaxes.com/help/ValueReferences.

---

This appears to generate John Doe as JDOE, I would prefer it to look like JDoe.

Is this possible?

---

Hello,

Unfortunately, there is no such possibility using value references. It can only be done using a script in a business rule. For example, you can use the following script from our repository: https://www.adaxes.com/script-repository/converting-first-character-of-a-value-to-uppercase-s504.htm.