Skip to main content
14-Alexandrite
February 4, 2020
Solved

Can't map pwdLastSet Active Directory attribute

  • February 4, 2020
  • 2 replies
  • 1860 views

I am trying to map the pwdLastSet AD attribute to a User Extenstion via Directory Services.  I added a property to the User Extension Thing Shape with Base Type = LONG:

steve237_1-1580780394677.png

Next, I mapped the AD attribute to the user extension with a default value of 237 (I set a default is to show that the value is not being set properly):

steve237_3-1580780637374.png

 However, the value is not set properly.  Here is a screen shot of my user extenstions to show that the value is zero:

steve237_5-1580781106082.png

 

It is not the value from my AD attribute:

steve237_4-1580780986599.png

It was also not set to the default value 237.

 

Are there limitations to which AD attributes can be mapped to user extensions?

 

Thanks,

Steve

 

Best answer by raluca_edu

Hi Steve,

 

What version of ThingWorx are you using?

Could you check the Application.log and Security.log for errors or attach them here?

 

Thank you,

Raluca Edu

2 replies

raluca_edu
17-Peridot
February 4, 2020

Hi Steve,

 

What version of ThingWorx are you using?

Could you check the Application.log and Security.log for errors or attach them here?

 

Thank you,

Raluca Edu

steve23714-AlexandriteAuthor
14-Alexandrite
February 4, 2020

Raluca,

I had been checking the Application log file all along for errors, but unfortunately had failed to check the security log.

 

The security log had error: General error occurred. [explanation: java.lang.Exception: User does not exist in AD, the credentials are invalid, or the User ID Attribute Name Schema Mapping is incorrect.] each time I logged in.  More research showed that the directory service I was using for testing was causing that error, so the second dir service in the list was actually doing the authentication!  (I had not done the same mapping in the second directory service.)  Of course, once I updated the mapping in the 2nd service it started to populate the pwdLastSet user extension. Problem solved.

 

Thanks for the hint.

raluca_edu
17-Peridot
February 5, 2020
I am glad you solved the issue.

Regards,
Raluca
18-Opal
February 4, 2020

Hello Steve,

 

Just my two cents:

  1. Try it with capital P, i.e. PwdLastSet and with "-" i.e. Pwd-Last-Set;
  2. Try defining it as STRING on ThingWorx side;
  3. Try to restart the server;

 

/ Constantine