Sometimes, an user cannot make login with AX 4.0. It happen if user was moved or any change in the Active Directory was performed.
Solution: disable the user, save the record. Then, re-enable the user and save again.
AX refresh the user's SID executing this action.
2 comments:
So what is the cause of the problem you're trying to solve? Is it a chenged user's SID that prevents a user to login?
Frankly speaking it's next to impossible in AD that a SID of a user object changes for any reason. If a user in AD has a different SID then it's just a different user, it has different security groups assignment, different access rights, etc.
The SID could be blank ('') if you disable the user or make underline changes by source code.
In other way, if the user was deleted from the AD (any reason/human error), a new SID will be generated, but inside AX, the userId still continue being valid avoiding data lost (tracing).
Post a Comment