On Fri, Jan 11, 2013 at 4:19 PM, Natxo Asenjo natxo.ase...@gmail.com wrote:
On Fri, Jan 11, 2013 at 3:51 PM, Rob Crittenden rcrit...@redhat.com wrote:
Natxo Asenjo wrote:
I just tried again to create a replica and had exactly the same error
as on the thread's first post.
in
We have setup an IPA replica server on the environment using the
following command:-
#ipa-replica-install --setup-dns --setup-ca --forwarder=192.168.1.204
/var/lib/ipa/replica-info-ipa2.labs.local.gpg
There is a client authenticating against it.
If I shutdown the ipa1 (Master server), the client
Maybe I am stupid or tired (or both ..) but I have tried many thing to
include the ca cert, the ipa key and pem file in a single pkcs12 file but I
am still stucked.
Can you give me a more detailled help ?
2013/2/8 Rob Crittenden rcrit...@redhat.com
James James wrote:
OK .. but I have to
It started working after a few minutes.
On Sat, Feb 9, 2013 at 9:34 PM, Rajnesh Kumar Siwal
rajnesh.si...@gmail.com wrote:
We have setup an IPA replica server on the environment using the
following command:-
#ipa-replica-install --setup-dns --setup-ca --forwarder=192.168.1.204
On 02/08/2013 05:29 PM, It Meme wrote:
Hi:
Scenario:
1) User is created via LDAP call to IPA (i.e.the 389 Directory Server)
The above user will not have IPA-specific attributes.
Can we use the Python Library, or CLI, to modify the account to IPA-ize it?
You're really better off using the
Charlie Derwent wrote:
Hi
Whenever I attempt an unattended installation with a principal and
password. The installation fails.
I'm using the following syntax for my command
ipa-client-install --domain=example.com http://example.com
--server=ipa.example.com http://ipa.example.com
Rajnesh Kumar Siwal wrote:
We have setup an IPA replica server on the environment using the
following command:-
#ipa-replica-install --setup-dns --setup-ca --forwarder=192.168.1.204
/var/lib/ipa/replica-info-ipa2.labs.local.gpg
There is a client authenticating against it.
If I shutdown the ipa1
James James wrote:
Maybe I am stupid or tired (or both ..) but I have tried many thing to
include the ca cert, the ipa key and pem file in a single pkcs12 file
but I am still stucked.
Can you give me a more detailled help ?
Well, this is one of the reasons we're deprecating this feature,
Here is what I did:
Install Fedora 17 XFCE spin.
yum upgrade
yum install freeipa-client
enroll machine (it enrolls just fine)
However, when I reboot the machine, I find the ipa.service isn't running.
So I manually try to start it:
systemcrl start ipa.service
Then I get this error
Failed to
