Please read this chapter of admin guide
https://access.redhat.com/site/documentation/en-US/Red_Hat_Directory_Server/9.0/html/Administration_Guide/Extending_the_Directory_Schema.html
This should have solution for your problem.
8 maj 2013 20:53, "Steve Ovens" <steve_ovens@xxxxxxxxx> napisał(a):
Any guidance would be greatly appreciated!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)I have run this through the ol-schema-migrate.pl and placed the output in /etc/dirsrv/slapd-ds/schema/62sshkeys.ldif.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:
#
# LDAP Public Key Patch schema for use with openssh-ldappubkey
# Author: Eric AUGE <eau@xxxxxxxxx>
#
# 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 restarted the server and there were no errors produced so I am assuming that it took the ldif fine.
Thanks
--
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@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
