On 16/09/13 15:35, Simo Sorce wrote:
No, we need to update as it is used to unlock auto-locked accounts. What
we decided on was to not propagate any of these operations via
replication to avoid huge churn across all of the enterprise.
Simo.
The underlying issue is: with a large scale
On 17.9.2013 09:18, Arturo Borrero wrote:
On 16/09/13 15:35, Simo Sorce wrote:
No, we need to update as it is used to unlock auto-locked accounts. What
we decided on was to not propagate any of these operations via
replication to avoid huge churn across all of the enterprise.
Simo.
The
On 17/09/13 10:38, Petr Spacek wrote:
Interesting idea, but it needs careful design not to omit any possible
case.
Please create RFE ticket (request for enhancement):
https://fedorahosted.org/freeipa/newticket
You will need an Fedora Account, please follow this:
I apologize for the weird subject. The problem I'm facing feels a little weird
and I could use some help.
I'm running IPA in a test environment and trying to find different ways in
which I can break it and then repair it. My IPA is running on CentOS 6.4:
Linux ipa00.testdomain.com
On 09/16/2013 07:57 PM, Dmitri Pal wrote:
On 09/16/2013 12:02 PM, KodaK wrote:
Yet another AIX related problem:
The AIX LDAP client is called secldapclntd (sure, they could make it
more awkward, but the budget ran out.) I'm running into the issue
detailed here:
