Issue trying to resolve users from another domain

  • 16 February 2021
  • 0 replies
  • 181 views

Badge +6

Issue

You may experience that the refresh of an identity from Active Directory (AD) does not resolve correctly, and you are presented with an error.

Error Code

The following error will appear very often (every 8 hours for each user) in the K2 Host Server log:

"58110654","2021-05-24 04:14:55","Error","IdentityService","64005","ResolvingException","IdentityService.ProviderCacheIdentity:RoleProvider.GetUser","64005 Failed to resolve 'K2:FRHIF114': A referral was returned from the server. .","anonymous","0.0.0.0","SEFRAPP02019:F:K2 blackpearlHost ServerBin","58110654","9f1998fbb20447058acb1345f32f28d8",""
 
This error appears for all accounts. The business application seems to work without problems, and you can connect to the K2 management website with Windows STS. However, you can't grant permissions to any account, as it fails to search for the user: 
.","anonymous","0.0.0.0","SEFRAPP02019:F:K2 blackpearlHost ServerBin","58321598","84315d20f9c6470a94bf6fc7c18588c7","" "58321806","2021-06-03 10:28:13","Error","IdentityService","64007","IdentityServiceError","IdentityService.ProviderFindUsers","64007 An error occurred during Group provider search, and no results were returned A referral was returned from the server.
 

Resolution

This type of error could generally appear when there is a trust issue between the default K2 server domain and the specific domain. Its likely that its not possible to browse the LDAP of the specific domain, perhaps the trust between the K2 server domain and this specific domain is the problem.
 
You can fix it by doing one of the following:
  •  Setup a trust between the development and production domains.
  •  Or by switching the development server on the production Active Directory (Domain) instead of the development one.
 
You can find the list of Domains from the K2 Management site, under Users > K2 > Domains.

Additional Information

The error messages are from an environment without the "New Identity Service" activated, but you will certainly see the same error when the "New Identity Service" is activated, with an LDAP browser, connected on the K2 server with the K2 service account you will have certainly see the same error. 


0 replies

Be the first to reply!

Reply