On Mon, Mar 28, 2016 at 10:55:06AM -0500, Endi Sukma Dewata wrote:
> On 3/28/2016 10:00 AM, Rob Crittenden wrote:
> >Timothy Geier wrote:
> >>>Thanks for the procedure..the good news is this worked quite
> >>>well in making sure that 389 didn’t crash immediately after
> >>>startup. The bad news is
> On Mar 28, 2016, at 12:53 PM, Thorsten Scherf wrote:
>
> On [Sat, 26.03.2016 03:26], Timothy Geier wrote:
>> To follow up on this issue, we haven’t been able to get any further since
>> last month due to the missing caServerCert profile..the configuration
>> files /usr/share/pki/ca/profiles
On [Sat, 26.03.2016 03:26], Timothy Geier wrote:
To follow up on this issue, we haven’t been able to get any further since
last month due to the missing caServerCert profile..the configuration
files /usr/share/pki/ca/profiles/ca/caServerCert.cfg
and /var/lib/pki/pki-tomcat/ca/profiles/ca/
On 3/28/2016 10:00 AM, Rob Crittenden wrote:
Timothy Geier wrote:
Thanks for the procedure..the good news is this worked quite well in
making sure that 389 didn’t crash immediately after startup. The bad
news is that the certificates still didn’t renew due to
Server at "http://master_server:80
Timothy Geier wrote:
On Feb 28, 2016, at 2:15 AM, Timothy Geier mailto:tge...@accertify.com>> wrote:
On Feb 23, 2016, at 4:22 AM, Ludwig Krispenz mailto:lkris...@redhat.com>> wrote:
On 02/22/2016 11:51 PM, Timothy Geier wrote:
What’s the established procedure to start a 389 instance with
John Williams wrote:
I've got some sporadic behavior on my IPA instance and I'm hoping
someone can help me resolve the issue. The problem is that many times
my clients cannot authenticate to the respective hosts. First, my
environment. Some details:
ipa2 - centos 6.3 - ipa server 3.0.0
ipa3
