Implementing Multiple UPN suffixes

Question

What is the best way of implementing user creation with different UPN suffixes in Adaxes as of 2018 ?

I read, and configured, the "old" methods where you create a user property pattern, with a custom text attribute, and then populated the data by changing the web interface with another friendly name, so it wouldnt say "CustomTextAttribute1" and so on...

But that was a solution in 2015, and it seems kind of "dirty" - isnt there a better way, and more native way of implementing different UPN´s for user creation - seems like it could be done smarter?

Couldnt Adaxes read the UPN attributes that are configured in Active Directory, and then present them as possible options for user creation? Just like the normal interface ADUC does?

Answer 1

Hello,

The solution you described is the only one. There is no alternative way.

Comments

Ok, thanks!