While installing the Identity connector in Cloud environment we are facing domian not found issue.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

While installing the Identity connector in Cloud environment we are facing domian not found issue.

L1 Bithead

Centrify.Cloud.Core.ProxyLib.DomainControllerNotFoundException: Domain not found with name abg.com

  at Centrify.Cloud.Core.ProxyLib.ADHelper.GetDomain(String domainName)

  at Centrify.Cloud.Core.ProxyLib.ADHelper.GetDomainGuid(String domainName)

  at Centrify.Cloud.Core.ProxyLib.ADHelper.GetDomainNativeGuid(String domainName)

  at Centrify.Cloud.Mobile.Model.SetupWizardModule.SetupProxyByCode.RegisterWorker.<>c__DisplayClass2_0.<Run>b__3(RegistrationRequestv4 request)

  at Centrify.Cloud.Mobile.ProxyService.Register(Action`1 initRequest)

  at Centrify.Cloud.Mobile.Model.SetupWizardModule.SetupProxyByCode.RegisterWorker.Run(ISetupWizardWorkerContext context, Object data)

  at Centrify.Cloud.Mobile.View.AggregatedWizardProgressPage.Centrify.Cloud.Mobile.IWizardProgressPage.Execute(ISetupWizardWorkerContext context)

  at System.Threading.Tasks.Task.Execute()

1 accepted solution

Accepted Solutions

The issue with my particular incident is that the Identity Connector was being installed on a child domain-joined server. This was resolved by removing the Identity Connector host from the child domain, and joining the Identity Connector to the parent domain.

View solution in original post

4 REPLIES 4

Did you find a solution to this issue? I am facing the same issue when attempting to install the Identity Connector.

L4 Transporter

Hi @Nagarjuna Reddy​ & @Jorge Guandique​,

 

As the community has not answered this question for some time, could you kindly share if you could resolve this issue and how?

If the issue is still relevant, I would advise raising a ticket with our Support team for further assistance.

 

Thanks,

Niv

The issue with my particular incident is that the Identity Connector was being installed on a child domain-joined server. This was resolved by removing the Identity Connector host from the child domain, and joining the Identity Connector to the parent domain.

L5 Sessionator

Hi @Jorge Guandique​ 

 

Thank you for the update and for sharing the solution. Happy to hear it is now resolved!

 

Regards,

Gil

  • 1 accepted solution
  • 369 Views
  • 4 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!