cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily. X

User names should be case insensitive and no duplicate users created when using ActiveDirectory

User names should be case insensitive and no duplicate users created when using ActiveDirectory

When Thingworx is configured to use ActiveDirectory, users can authenticate with username that is case insensitive in ActiveDirectory, but this currently created different users in Thingworx, e.g. I could login with username tomdecock, Tomdecock, TOMDECOCK or even ToMdEcOcK, but this would create 4 different Thingworx Users.  This leads to unwanted complexity when creating personalized Thingworx application experiences for users....

In Article - CS230846 I read that PTC considers this "Working as Designed", so I can only conclude that it is poorly designed then....  Personally I would consider this a serious bug - but hey, the article suggests to file an enhancement request so here it is.... I wonder why PTC does not even consider to file this enhancement request themselves ?

 

4 Comments
bbeuckSIG
15-Moonstone

100% agreed. It's also a question of licenses. It is obviously the customer's duty to consistently purge ambiguous user logins to not let them suck up 4 licenses at once (in given example).

olivierlp
Community Manager
Status changed to: Under Consideration

PTC plans to address this as part of the product roadmap.

cfpenteado
6-Contributor

@olivierlp  Do you have any further information on this? 

 

Duplicate usernames become a giant headache for Navigate. It makes it impossible to use the auto user creation feature effectively when dealing with named license groups. It also becomes a headache to migrate the users out of a system as the import fails due to duplicate users. This really needs to be addressed. 

RachelMc
11-Garnet

@cfpenteado - We are actively aware of this from both internal and external users, and we are evaluating when we can do the work to address this.