Am 09.05.13 schrieb Rich Megginson <rmeggins(a)redhat.com>:
On 05/09/2013 08:28 AM, Steve Ovens wrote:
> Thanks for the responses.
>
>
> I dont know why I didnt find that manual when I was googling. Perhaps because it is
for the RH DS and I was searching 389 (I realize they are quite similar)
>
>
> As to the FreeIPA, I may investigate this in the future but the issue I have here
is that I have a DS in service already so its not really a fair solution to switch
products.
>
>
> Does FreeIPA provide Active Directory Sync.
>
>
>
Yes, although freeipa is slightly different:
1) it does not do group sync
2) it only syncs adds from AD -> DS - it does not sync adds from DS -> AD
3) it will sync account disable/enable
posix-winsync should sync account disable/enable too, if not it is a bug ;-)
>
>
> Thanks again for the replies
>
>
>
> On Thu, May 9, 2013 at 6:03 AM, Petr Spacek <pspacek(a)redhat.com> wrote:
>
> > Hello,
> >
> > On 8.5.2013 20:53, Steve Ovens wrote:
> >
> > > Hi,
> > >
> > > I have been quite happily using 389 for around a year, and while I am
not
> > > at all advanced I have been able to add Samba and sudoers to 389. I am
now
> > > attempting to add openssh keys to the user entries I am using the
> > > openssh-lpk_openldap.schema:
> > >
> >
> > IMHO the FreeIPA project could help you a lot. It contains pre-baked solutions
for common problems like central management of sudoers and ssh authorized_keys, including
management utilities (with CLI, WebUI, XML RPC, JSON RPC).
> >
> > Homepage:
http://freeipa.org/
> > Users list:
http://www.redhat.com/mailman/listinfo/freeipa-users
> >
> > The home page is undergoing a major redesign at the moment, because it is a
bit confusing to newcomers. I would recommend you to ask freeipa-users list if you
can't find what you are looking for.
> >
> > And BTW - FreeIPA is based on 389 DS.
> >
> > I'm sorry for the advertisement.
> >
> > Petr^2 Spacek
> >
> >
> > > #
> > > # LDAP Public Key Patch schema for use with openssh-ldappubkey
> > > # Author: Eric AUGE <eau(a)phear.org>
> > > #
> > > # Based on the proposal of : Mark Ruijter
> > > #
> > >
> > >
> > > # octetString SYNTAX
> > > attributetype ( 1.3.6.1.4.1.24552.500.1.1.1.13 NAME
'sshPublicKey'
> > > DESC 'MANDATORY: OpenSSH Public key'
> > > EQUALITY octetStringMatch
> > > SYNTAX 1.3.6.1.4.1.1466.115.121.1.40 )
> > >
> > > # printableString SYNTAX yes|no
> > > objectclass ( 1.3.6.1.4.1.24552.500.1.1.2.0 NAME 'ldapPublicKey'
SUP top
> > > AUXILIARY
> > > DESC 'MANDATORY: OpenSSH LPK objectclass'
> > > MAY ( sshPublicKey $ uid )
> > > )
> > >
> > >
> > > I have run this through the
ol-schema-migrate.pl(http://ol-schema-migrate.pl) and placed the output in
> > > /etc/dirsrv/slapd-ds/schema/62sshkeys.ldif.
> > >
> > > I have restarted the server and there were no errors produced so I am
> > > assuming that it took the ldif fine.
> > >
> > > How do I go about using the new schema. I have googled around quite a
bit,
> > > but I must be missing something. I would appreciate any pointers and I
> > > fully intend on publishing a how-to on this (as I do for most things
over
> > > at
overclockers.com(http://overclockers.com)<http://www.overclockers.com/...
> > > )
> > >
> > > Any guidance would be greatly appreciated!
> > >
> >
>
>
>
>
> --
> Red Hat Certified Engineer
> Ubuntu Certified Professional
> Novell Datacenter Specialist
> Novell Certified Linux Administrator
> LPIC-1 Certified
> Linux+ Certified
>
>
>
>
> --
> 389 users mailing list
> 389-users(a)lists.fedoraproject.org
>
https://admin.fedoraproject.org/mailman/listinfo/389-users
>