On Thu, 20 Jan 2011 11:03:12 +0530
Aravind GV aravind...@gmail.com wrote:
Hi Simo,
Great repossess from you but still issue is not solved completely.
After applying your patch iam getting below mention error
[root@dirsrv ~]# ipa-replica-manage connect --winsync --binddn
Hi Simon
Iam traveling this week will test and let u know in a weeks time.
Sent from my iPhone
On Jan 20, 2011, at 7:28 PM, Simo Sorce sso...@redhat.com wrote:
On Thu, 20 Jan 2011 11:03:12 +0530
Aravind GV aravind...@gmail.com wrote:
Hi Simo,
Great repossess from you but still issue is
Hello,
We have a deployment of IPA that we have been using successfully
for 185 days. We are 3 days past the "half year" mark, and the
self-signed cert that was created with the original IPA install
(FreeIPA v2 alpha) has expired. I have created a new
Ian Stokes-Rees wrote:
Hello,
We have a deployment of IPA that we have been using successfully for 185
days. We are 3 days past the half year mark, and the self-signed cert
that was created with the original IPA install (FreeIPA v2 alpha) has
expired. I have created a new self-signed cert,
Some more info:
1. certmonger wasn't running, so I started it. Then I can execute
"ipa-getcert list" but it doesn't return anything.
2. /var/log/ipa/default.log (the only log file in that dir)
appears to show the *new* cert being imported
Ian Stokes-Rees wrote:
Just so I have the full context, where did the original self-signed
cert come from? The initial cert should have been good for 12 months
so I'm a little confused. Do you know where the initial certificate
came from?
I have to plead ignorance, since it was our regular
Ian Stokes-Rees wrote:
Some more info:
1. certmonger wasn't running, so I started it. Then I can execute
ipa-getcert list but it doesn't return anything.
Ok, your install must have pre-dated our implementation of it.
2. /var/log/ipa/default.log (the only log file in that dir) appears to
