Skip to main content
Nintex Community Menu Bar
Solved

Error: The 'AAD:User' could not be found

  • February 20, 2020
  • 2 replies
  • 58 views
  • Translate

Hello,

 

We wanted to change Security Label from AAD to AAD Auth in Authentication->Claims, so we done as it said in Step 4 'Add the AAD security Label in K2' in this article: https://help.k2.com/onlinehelp/K2Five/icg/current/default.htm#Configure/SF/MultiAuthAAD.htm?Highlight=azure%20active%20directory
But after trying to overwrite old Security label from AAD to AAD Auth with the same SQL Script (but SecurityLabelName changed), all Azure Authentication stopped working and we can no longer validate new users. Even after running this script again with AAD as SecurityLabelName it didn't help - Azure Active Directory doesn't work anymore. What can we do make it work again?

 

I attached error.


16852i5DA50A65F9FE5727.png

Best answer by HeinrichCohn

Hi AnnaGGC


 


I would recommend that you possibly review the below KB article and also confirm if you are utilizing the new Identity service.


 


https://help.k2.com/kb003132


 


The error you are seeing is due to identity that are not enable and not cached in K2.


 


Regards

View original

2 replies

Forum|alt.badge.img+8
  • Nintex Employee
  • 57 replies
  • Answer
  • February 24, 2020

Hi AnnaGGC


 


I would recommend that you possibly review the below KB article and also confirm if you are utilizing the new Identity service.


 


https://help.k2.com/kb003132


 


The error you are seeing is due to identity that are not enable and not cached in K2.


 


Regards

Translate

  • Author
  • 6 replies
  • February 24, 2020

Hello, 

 

Thank you very much. It helped, now users can log in! Unfortunetly, I still have an error when I want to add Server Rights for users: 'Security Label not found: AAD'. Now I use AAD Auth security label.

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings