<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Jason,<br>
<br>
we have a customer where we provision from midPoint to Active
Directory consisting of multiple domain controllers. The AD/Exchange
connector is making serverless bind unless you specify IP/hostname.
But the connector server itself is specified by IP/hostname, so if
you want to have failover for connector server, you need to have
proper infrastructure.<br>
<br>
The customer is using this for provisioning, not synchronization.<br>
<br>
If you are using provisioning to AD, and you can ensure the machine
with connector server is (almost) always running, the serverless
bind should do the trick even if the DC are restarting (because I
suppose at least one is always up and running).<br>
<br>
Regards,<br>
I.<br>
<br>
<div class="moz-cite-prefix">On 02/23/2015 04:42 PM, Jason Everling
wrote:<br>
</div>
<blockquote
cite="mid:CAFkZXY665MuxJJyrfq+JiFbD_gk1-GSqrT6HFLa+1hBg_jACCQ@mail.gmail.com"
type="cite">
<div dir="ltr">Now that all my resources, Active Directory, 3
databases, and CSV are syncing properly, I was thinking about
using our AD virtual ip for failover in midPoint instead of
connecting to only 1 Domain Controller. Midpoint would connect
to the virtual IP and if the primary domain controller goes down
then the 2nd Domain controller would be used.
<div><br>
</div>
<div>Is this OK to use? The sync task stops in a failed state if
the DC is not reachable and this way the task would continue
to run. Our DCs are rebooted 1 at a time regularly for updates
and was just wondering if this would work or if there are any
known issues doing this. I know that I would more than likely
need to modify the site replication time in AD so that user
info is updated more frequently but I could not think of
anything else that could cause an issue.</div>
<div><br>
</div>
<div>JASON</div>
</div>
<br>
<font size="2"><br>
<br>
CONFIDENTIALITY NOTICE:<br>
This e-mail together with any attachments is proprietary and
confidential; intended for only the recipient(s) named above and
may contain information that is privileged. You should not
retain, copy or use this e-mail or any attachments for any
purpose, or disclose all or any part of the contents to any
person. Any views or opinions expressed in this e-mail are those
of the author and do not represent those of the Baptist School
of Health Professions. If you have received this e-mail in
error, or are not the named recipient(s), you are hereby
notified that any review, dissemination, distribution or copying
of this communication is prohibited by the sender and to do so
might constitute a violation of the Electronic Communications
Privacy Act, 18 U.S.C. section 2510-2521. Please immediately
notify the sender and delete this e-mail and any attachments
from your computer. </font><br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
midPoint mailing list
<a class="moz-txt-link-abbreviated" href="mailto:midPoint@lists.evolveum.com">midPoint@lists.evolveum.com</a>
<a class="moz-txt-link-freetext" href="http://lists.evolveum.com/mailman/listinfo/midpoint">http://lists.evolveum.com/mailman/listinfo/midpoint</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Ing. Ivan Noris
Senior Identity Management Engineer & IDM Architect
evolveum.com evolveum.com/blog/
___________________________________________________
"Semper Id(e)M Vix."
</pre>
</body>
</html>