Friday, 17 November 2017

CRM error login 2011/2013/2015/2016 Windows Authentification federation

Users... Can't Live With Them, Can't Live Without Them...



This is never old to say but still happens, so: Create a workflows to update the username in order to avoid the error, this way we will restabishe the link with the other account on the AD.

Example:
username       - GUID On AD - Status
contoso\hsilva - 12345 <- Active
contoso\hsilva - 12345 <- Disabled

Online:
Create workflow on-demand and run against the Disabled username adadmin\hsilva, and change the username for contoso\test (its conviente that you use a user that no longer is going to be used on the AD and that "contoso\test" exist)

On Premises:
You can create a workflow as online and is the best pratice, insted of going directly into the database to the user and change the bollean value from 0 to 1. In this case you need to active the user so you can go back to the CRM and change the username to "contoso\test" and then disable the user.

No comments:

Post a Comment