Where is slapd conf file

This looks like a broken slapd. Anyway my openldap daemon started and I was able to connect to ldap server. This isn't a slapd. The installation process should write another one for you. Add a comment. Active Oldest Votes. Improve this answer. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Sign up or log in Sign up using Google.

Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete? Podcast Do polyglots have an edge when it comes to mastering programming Featured on Meta. Directives in this section apply only to the backend in which they are defined. They are supported by every type of backend. Backend directives apply to all databases instances of the same type and, depending on the directive, may be overridden by database directives.

This directive marks the beginning of a backend declaration. Directives in this section apply only to the database in which they are defined.

They are supported by every type of database. This directive marks the beginning of a database instance declaration. This directive puts the database into "read-only" mode. Any attempts to modify the database will return an "unwilling to perform" error. If set on a consumer, modifications sent by syncrepl will still occur.

This directive specifies the DN that is not subject to access control or administrative limit restrictions for operations on this database. The DN need not refer to an entry in this database or even in the directory.

This directive can be used to specifies a password for the DN for the rootdn when the rootdn is set to a DN within the database. It is also permissible to provide hash of the password in RFC form.

This directive specifies the DN suffix of queries that will be passed to this backend database. Multiple suffix lines can be given, and at least one is required for each database definition. Note: When the backend to pass a query to is selected, slapd looks at the suffix line s in each database definition in the order they appear in the file. Thus, if one database suffix is a prefix of another, it must appear after it in the config file. This directive specifies the current database as a consumer of the provider content by establishing the current slapd 8 as a replication consumer site running a syncrepl replication engine.

The provider database is located at the replication provider site specified by the provider parameter. See RFC for more information on the protocol. The provider parameter specifies a scheme, a host and optionally a port where the provider slapd instance can be found. Note that the syncrepl uses a consumer-initiated protocol, and hence its specification is located on the consumer.

The content of the syncrepl consumer is defined using a search specification as its result set. The consumer slapd will send search requests to the provider slapd according to the search specification.

The search specification includes searchbase , scope , filter , attrs , exattrs , attrsonly , sizelimit , and timelimit parameters as in the normal search specification. The searchbase parameter has no default value and must always be specified. Both sizelimit and timelimit default to "unlimited", and only positive integers or "unlimited" may be specified. The exattrs option may also be used to specify attributes that should be omitted from incoming entries.

The operation type is specified by the type parameter. In the refreshOnly operation, the next synchronization search operation is periodically rescheduled at an interval time after each synchronization operation finishes. The interval is specified by the interval parameter. It is set to one day by default.

In the refreshAndPersist operation, a synchronization search remains persistent in the provider slapd instance. Further updates to the provider will generate searchResultEntry to the consumer slapd as the search responses to the persistent synchronization search. The schema checking can be enforced at the LDAP Sync consumer site by turning on the schemachecking parameter. If it is turned on, every replicated entry will be checked for its schema as the entry is stored on the consumer.

Every entry in the consumer should contain those attributes required by the schema definition. Simple authentication should not be used unless adequate data integrity and confidentiality protections are in place e. Simple authentication requires specification of binddn and credentials parameters.

SASL authentication is generally recommended. SASL authentication requires specification of a mechanism using the saslmech parameter. The authzid parameter may be used to specify an authorization identity. See the chapter entitled Replication with slurpd for more information on how to use this directive. This directive specifies the name of the replication log file to which slapd will log changes. The replication log is typically written by slapd and read by slurpd. Normally, this directive is only used if slurpd is being used to replicate the database.

However, you can also use it to generate a transaction log, if slurpd is not running. In this case, you will need to periodically truncate the file, since it will grow indefinitely otherwise. This directive specifies the DN that is not subject to access control or administrative limit restrictions for operations on this database.

The DN need not refer to an entry in this database or even in the directory. This directive can be used to specifies a password for the DN for the rootdn when the rootdn is set to a DN within the database. It is also permissible to provide hash of the password in RFC form. This directive specifies the DN suffix of queries that will be passed to this backend database. Multiple suffix lines can be given, and at least one is required for each database definition.

Note: When the backend to pass a query to is selected, slapd looks at the suffix line s in each database definition in the order they appear in the file. Thus, if one database suffix is a prefix of another, it must appear after it in the config file. This directive specifies the current database as a replica of the master content by establishing the current slapd 8 as a replication consumer site running a syncrepl replication engine.

The master database is located at the replication provider site specified by the provider parameter. See draft-zeilenga-ldup-sync-xx. The provider parameter specifies a scheme, a host and optionally a port where the provider slapd instance can be found. Note that the syncrepl uses a consumer-initiated protocol, and hence its specification is located at the consumer site, whereas the replica specification is located at the provider site.

They do not represent the replication peers of each other. The content of the syncrepl replica is defined using a search specification as its result set. The consumer slapd will send search requests to the provider slapd according to the search specification. The search specification includes searchbase , scope , filter , attrs , attrsonly , sizelimit , and timelimit parameters as in the normal search specification. The searchbase parameter has no default value and must always be specified.

Both sizelimit and timelimit default to "unlimited", and only integers or "unlimited" may be specified. The operation type is specified by the type parameter. In the refreshOnly operation, the next synchronization search operation is periodically rescheduled at an interval time after each synchronization operation finishes.

The interval is specified by the interval parameter. It is set to one day by default. In the refreshAndPersist operation, a synchronization search remains persistent in the provider slapd. Further updates to the master replica will generate searchResultEntry to the consumer slapd as the search responses to the persistent synchronization search. The schema checking can be enforced at the LDAP Sync consumer site by turning on the schemachecking parameter.

If it is turned on, every replicated entry will be checked for its schema as the entry is stored into the replica content. Every entry in the replica should contain those attributes required by the schema definition. If it is turned off, entries will be stored without checking schema conformance.

The default is off. The binddn parameter gives the DN to bind as for the syncrepl searches to the provider slapd. It should be a DN which has read access to the replication content in the master database. The bindmethod is simple or sasl , depending on whether simple password-based authentication or SASL authentication is to be used when connecting to the provider slapd.

The realm parameter specifies a realm which a certain mechanisms authenticate the identity within. The syncrepl replication mechanism is supported by the three native backends: back-bdb, back-hdb, and back-ldbm.

This directive is only applicable in a slave slapd. It specifies the DN allowed to make changes to the replica. See the Replication with slurpd chapter for more information on how to use this directive. It specifies the URL to return to clients which submit update requests upon the replica. If specified multiple times, each URL is provided. That is, they must follow a "database bdb" or "database hdb" line and come before any subsequent "backend" or "database" line.

This directive specifies the directory where the BDB files containing the database and associated indices live. Directives in this category only apply to a LDBM database. That is, they must follow a "database ldbm" line and come before any subsequent "backend" or "database" line.