On 12/04/2014 08:39 AM, Rich Megginson wrote:
On 12/04/2014 01:45 AM, Petr Spacek wrote:
On 4.12.2014 05:02, Janelle wrote:
Thanks -- still a bit strange that it did not show up on some
servers - vary
random and intermittent.
BTW - a bit of information others might find useful. If you try
On 12/04/2014 01:45 AM, Petr Spacek wrote:
On 4.12.2014 05:02, Janelle wrote:
Thanks -- still a bit strange that it did not show up on some servers - vary
random and intermittent.
BTW - a bit of information others might find useful. If you try to use the
LDAP portion of IPA for authentication
Dmitri Pal wrote:
On 12/04/2014 09:41 AM, Rich Megginson wrote:
On 12/04/2014 08:39 AM, Rich Megginson wrote:
On 12/04/2014 01:45 AM, Petr Spacek wrote:
On 4.12.2014 05:02, Janelle wrote:
Thanks -- still a bit strange that it did not show up on some
servers - vary
random and intermittent.
Hi all,
just (pam)auth and nslcd
It was ported from a running OpenLDAP environment to IPA. Just trying
to do conversions in stages so as not to change too much all at once.
Thought I could go from OpenLDAP to IPA and just use the backend of
389ds. Functionally it does work, but the load
On 12/04/2014 09:56 AM, Janelle wrote:
Hi all,
just (pam)auth and nslcd
It was ported from a running OpenLDAP environment to IPA. Just trying
to do conversions in stages so as not to change too much all at once.
Thought I could go from OpenLDAP to IPA and just use the backend of
389ds.
On Thu, 04 Dec 2014, Janelle wrote:
Hi all,
just (pam)auth and nslcd
It was ported from a running OpenLDAP environment to IPA. Just trying
to do conversions in stages so as not to change too much all at once.
Thought I could go from OpenLDAP to IPA and just use the backend of
389ds.
On 12/4/14 8:30 AM, Alexander Bokovoy wrote:
On Thu, 04 Dec 2014, Janelle wrote:
Hi all,
just (pam)auth and nslcd
It was ported from a running OpenLDAP environment to IPA. Just
trying to do conversions in stages so as not to change too much all
at once. Thought I could go from OpenLDAP to
On 12/04/2014 04:56 PM, Janelle wrote:
Hi all,
just (pam)auth and nslcd
It was ported from a running OpenLDAP environment to IPA. Just trying
to do conversions in stages so as not to change too much all at once.
Thought I could go from OpenLDAP to IPA and just use the backend of
389ds.
To help understand the environment a bit - perhaps this will help.
1. Approx 7500 clients across 3 datacenters- all manor of *nix, ranging
from AIX, Linux, HP-UX and Solaris - hence the reason why they all
can't use ipa-client configs. Although that is in the plan at least
for Linux
On 12/04/2014 11:01 AM, Janelle wrote:
To help understand the environment a bit - perhaps this will help.
1. Approx 7500 clients across 3 datacenters- all manor of *nix,
ranging from AIX, Linux, HP-UX and Solaris - hence the reason why
they all can't use ipa-client configs. Although
Here is a bit of baffling one on 4.0.5:
Replica install p11-kit???
Connection from master to replica is OK.
Connection check OK
p11-kit: ipa.p11-kit: x-public-key-info: invalid or unsupported attribute
Configuring NTP daemon (ntpd)
[1/4]: stopping ntpd
[2/4]: writing configuration
...
On 12/03/2014 04:40 PM, Janelle wrote:
Here is a bit of baffling one on 4.0.5:
Replica install p11-kit???
This is a part of the DNSSEC set of packages.
Connection from master to replica is OK.
Connection check OK
p11-kit: ipa.p11-kit: x-public-key-info: invalid or unsupported attribute
Thanks -- still a bit strange that it did not show up on some servers -
vary random and intermittent.
BTW - a bit of information others might find useful. If you try to use
the LDAP portion of IPA for authentication - rather than fulling
installing the IPA client and using Kerberos - the
On 4.12.2014 05:02, Janelle wrote:
Thanks -- still a bit strange that it did not show up on some servers - vary
random and intermittent.
BTW - a bit of information others might find useful. If you try to use the
LDAP portion of IPA for authentication - rather than fulling installing the
14 matches
Mail list logo
