On Fri, 19 Aug 2016, David Kowis wrote:
On 08/16/2016 10:51 PM, Alexander Bokovoy wrote:
On Tue, 16 Aug 2016, David Kowis wrote:
On 08/15/2016 09:27 PM, David Kowis wrote:
On 08/15/2016 08:05 PM, Rob Crittenden wrote:
David Kowis wrote:
On 08/15/2016 04:33 AM, Petr Spacek wrote:
This is
On 08/16/2016 10:51 PM, Alexander Bokovoy wrote:
> On Tue, 16 Aug 2016, David Kowis wrote:
>> On 08/15/2016 09:27 PM, David Kowis wrote:
>>> On 08/15/2016 08:05 PM, Rob Crittenden wrote:
David Kowis wrote:
> On 08/15/2016 04:33 AM, Petr Spacek wrote:
>> This is weird as LDAP SASL &
On 08/16/2016 10:51 PM, Alexander Bokovoy wrote:
> On Tue, 16 Aug 2016, David Kowis wrote:
>> On 08/15/2016 09:27 PM, David Kowis wrote:
>>> On 08/15/2016 08:05 PM, Rob Crittenden wrote:
David Kowis wrote:
> On 08/15/2016 04:33 AM, Petr Spacek wrote:
>> This is weird as LDAP SASL &
On Tue, 16 Aug 2016, David Kowis wrote:
On 08/15/2016 09:27 PM, David Kowis wrote:
On 08/15/2016 08:05 PM, Rob Crittenden wrote:
David Kowis wrote:
On 08/15/2016 04:33 AM, Petr Spacek wrote:
This is weird as LDAP SASL & GSSAPI is pretty standard thing.
In any case, you can check server logs
On 08/15/2016 08:05 PM, Rob Crittenden wrote:
> David Kowis wrote:
>> On 08/15/2016 04:33 AM, Petr Spacek wrote:
>>> This is weird as LDAP SASL & GSSAPI is pretty standard thing.
>>>
>>> In any case, you can check server logs or use tcpdump/wireshark and
>>> see if the
>>> error somes from LDAP
David Kowis wrote:
On 08/15/2016 04:33 AM, Petr Spacek wrote:
This is weird as LDAP SASL & GSSAPI is pretty standard thing.
In any case, you can check server logs or use tcpdump/wireshark and see if the
error somes from LDAP server or if it is client side error.
That would tell us where to
On 08/15/2016 04:33 AM, Petr Spacek wrote:
> This is weird as LDAP SASL & GSSAPI is pretty standard thing.
>
> In any case, you can check server logs or use tcpdump/wireshark and see if the
> error somes from LDAP server or if it is client side error.
>
> That would tell us where to focus.
>
On 15.8.2016 03:29, David Kowis wrote:
> On 08/14/2016 07:57 PM, David Kowis wrote:
>> On 08/14/2016 02:31 PM, David Kowis wrote:
>>> Perhaps someone else has had this error before, or maybe just knows what
>>> I need to do?
>>
>> Digging through the mailing list, I only find this guy:
>>
On 08/14/2016 07:57 PM, David Kowis wrote:
> On 08/14/2016 02:31 PM, David Kowis wrote:
>> Perhaps someone else has had this error before, or maybe just knows what
>> I need to do?
>
> Digging through the mailing list, I only find this guy:
>
On 08/14/2016 02:31 PM, David Kowis wrote:
> Perhaps someone else has had this error before, or maybe just knows what
> I need to do?
Digging through the mailing list, I only find this guy:
https://www.redhat.com/archives/freeipa-devel/2014-October/msg00480.html
Seems someone had the exact same
I'm new to this, but super excited to find a nice authentication
solution. Trying to figure out why part of the installation failed,
perhaps someone here can point me in the right direction?
The `ipa-server-install` command makes it all the way through, except to
where it starts to do the client
11 matches
Mail list logo
