Unable to logon to K2 using AAD credentials: “WIF10201: No valid key mapping found for securityToken” error appears
This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
Issue
In this scenario you run K2 4.7 integrated with AAD without SharePoint, and on a regular basis the following error message appears:
"Unable to logon to K2 using AAD credentials: “WIF10201: No valid key mapping found for securityToken”
This error message has to be fixed manually as described here: Unable to logon to K2 using AAD credentials: “WIF10201: No valid key mapping found for securityToken”
Symptoms
When you run K2 4.7 without November 2017 CU and the error message appears every 2 or 3 months.Resolution
If you run versions of K2 4.7 older than November 2017 CU, you have to update to 4.7 November CU or newer to get support for rollover of the Azure Active Directory certificate thumbprints.
K2 4.7 support for rollover of the Azure Active Directory certificate thumbprints was introduced only in November 2017 CU whereas K2 Five have this capability starting from RTM release.
