- Original Message -
OK - thanks.
But is there any way IPA can be tweaked to do this without an
external
product (albeit a Red Hat one)? Is it possible for the sssd clients
to
round-robin their requests between 2 or more servers?
At the monment only by using _srv_ records you
Thanks Simo,
I was hoping for an alternative to the DNS _srv_ records due to the
Windows guys having exclusive use of those records (for now).
Is it feasible for IPA communications to be force round robined
between two or more servers that are replicas of each other? If it's a
possibility, I
- Original Message -
Thanks Simo,
I was hoping for an alternative to the DNS _srv_ records due to the
Windows guys having exclusive use of those records (for now).
Is it feasible for IPA communications to be force round robined
between two or more servers that are replicas of each
Hello,
I'm trying to build trust between FreeIPA and Windows Server 2008R2. It is said
that FreeIPA uses samba as the AD server, but I found that 389 Directory Server
is also installed. So which is used as the directory service for FreeIPA. If it
is samba, why 389 Director Server is needed?
Thanks Simo,
I was hoping for an alternative to the DNS _srv_ records due to the
Windows guys having exclusive use of those records (for now).
Is it feasible for IPA communications to be force round robined
between two or more servers that are replicas of each other? If
it's a
-Original Message-
From: freeipa-users-boun...@redhat.com
[mailto:freeipa-users-boun...@redhat.com] On Behalf Of Jakub Hrozek
Sent: 20 August 2012 15:28
To: freeipa-users@redhat.com
Subject: Re: [Freeipa-users] Specifying load balancing to SSSD clients
On Mon, Aug 20, 2012 at
- Original Message -
Hello,
I'm trying to build trust between FreeIPA and Windows Server 2008R2.
It is said that FreeIPA uses samba as the AD server, but I found
that 389 Directory Server is also installed. So which is used as the
directory service for FreeIPA. If it is samba, why 389
- Original Message -
I think I'll raise a ticket then. Not that the _srv_ records don't
do
the right job. It's just that in my scenario they are unusable. I
can't be alone in deploying IPA in a network already dominated by
AD.
For now (as I said in another reply), I'll randomly
+1. Use DNS. I agree with Simo.
On 08/21/2012 10:04 AM, Simo Sorce wrote:
You are not alone but we strongly suggest to use a separate DNS domain for
FreeIPA server, and if possible for its clients. Either a same level domain or,
at least, a delegated zone.
For example:
corp.domain.com - AD
On Tue, Aug 21, 2012 at 2:50 AM, Innes, Duncan
duncan.in...@virginmoney.com wrote:
I can't be alone in deploying IPA in a network already dominated by AD.
You're certainly not. In my case it appears the Windows people have
done everything they can to sabotage my efforts to implement SSO in
10 matches
Mail list logo
