joshuacox
commented
11 months ago so I have successfully turned a few configlines into around 60 ldif lines:
dn: cn=schema,cn=config
cn: schema
objectClass: olcSchemaConfig
olcAttributeTypes: ( 1.2.840.113556.1.2.102 NAME 'memberOf' D
he entry belongs to' EQUALITY distinguishedNameMatch SYNTAX
115.121.1.12 NO-USER-MODIFICATION USAGE dSAOperation X-ORIGI
ted Administrator' )
olcAttributeTypes: ( OLcfgOvAt:8.1 NAME ( 'olcDynListAttrSet'
DESC 'Dynamic list: <group objectClass>, <URL attributeDesc
attributeDescription>' EQUALITY caseIgnoreMatch SYNTAX OMsD
ORDERED 'VALUES' )
dn: cn=schema,cn=config
cn: schema
objectClass: olcSchemaConfig
olcObjectClasses: ( OLcfgOvOc:8.1 NAME ( 'olcDynListConfig' '
DESC 'Dynamic list configuration' SUP olcOverlayConfig STRU
ListAttrSet )
dn: cn={4}dyngroup,cn=schema,cn=config
objectClass: olcSchemaConfig
cn: {4}dyngroup
olcObjectIdentifier: {0}NetscapeRoot 2.16.840.1.113730
olcObjectIdentifier: {1}NetscapeLDAP NetscapeRoot:3
olcObjectIdentifier: {2}NetscapeLDAPattributeType NetscapeLDA
olcObjectIdentifier: {3}NetscapeLDAPobjectClass NetscapeLDAP:
olcObjectIdentifier: {4}OpenLDAPExp11 1.3.6.1.4.1.4203.666.11
olcObjectIdentifier: {5}DynGroupBase OpenLDAPExp11:8
olcObjectIdentifier: {6}DynGroupAttr DynGroupBase:1
olcObjectIdentifier: {7}DynGroupOC DynGroupBase:2
olcAttributeTypes: {0}( NetscapeLDAPattributeType:198 NAME 'm
dentifies an URL associated with each member of a group. Any
URL can be used.' SUP labeledURI )
olcAttributeTypes: {1}( DynGroupAttr:1 NAME 'dgIdentity' DESC
when processing the memberURL' SUP distinguishedName SINGLE
olcAttributeTypes: {2}( DynGroupAttr:2 NAME 'dgAuthz' DESC 'O
tion rules that determine who is allowed to assume the dgIde
uthzMatch SYNTAX 1.3.6.1.4.1.4203.666.2.7 X-ORDERED 'VALUES'
olcAttributeTypes: {3}( DynGroupAttr:3 NAME 'dgMemberOf' DESC
entry belongs to' EQUALITY distinguishedNameMatch SYNTAX 1.3
.121.1.12 )
olcObjectClasses: {0}( NetscapeLDAPobjectClass:33 NAME 'group
TRUCTURAL MUST cn MAY ( memberURL $ businessCategory $ descr
owner $ seeAlso ) )
olcObjectClasses: {1}( DynGroupOC:1 NAME 'dgIdentityAux' SUP
( dgIdentity $ dgAuthz ) )
structuralObjectClass: olcSchemaConfig
dn: olcOverlay={0}dynlist,olcDatabase={-1}frontend,cn=config
objectClass: olcOverlayConfig
objectClass: olcDynListConfig
olcOverlay: {0}dynlist
olcDynListAttrSet: {0}groupOfURLs labeledURI member
olcDynListAttrSet: {1}groupOfURLs memberURL member+memberOf@g
structuralObjectClass: olcDynListConfigHowever, placing this in /ldifs does not seem to have the desired effect. And honestly, this seems to be the wrong approach. i.e. to take two lines of very easy to understand config and turn them into some archaic block of 60 lines of ldif. I seem to be handing the next person who looks at these configs a major headache.
jonnoss1
carrodher
CrnTeam
Name and Version
bitname/openldap:2.6.6
What is the problem this feature will solve?
The documentation points to adding dynlist like so:
to slapd.conf However there is no slapd.conf in the bitnami container. as we are using /bitnami/openldap/slapd.d
The documentation points to doing something like this to convert:
But again I don't have a slapd.conf file to convert, or is there a base file I can use for this purpose? or is there a way to merge in an overlay?
What is the feature you are proposing to solve the problem?
Just an explanation of how to add in an overlay would be fantastic. Potentially adding it to the documentaiton. Or maybe even an environment variable:
I would imagine most would need configuration lines as well, like:
or something similar.
What alternatives have you considered?
just mapping in a directory and trying to slaptest a config that I might be able to ldifs out of.
with some tweaking I might be able to hack together a solution.
minimal slapd.conf (EDIT: now it works, but I am uncertain what all I need to extract from it)
so now I can get a slapcat:
It certainly is a lot of data, should I just be diffing that and slapcat on a slapd.conf of: