Diff for /admin/quickstart.sdf between versions 1.13 and 1.14

version 1.13, 2000/07/23 05:35:40 version 1.14, 2000/07/30 13:20:14
Line 1 Line 1
 # $OpenLDAP: pkg/openldap-guide/admin/quickstart.sdf,v 1.12 2000/07/22 23:43:12 kurt Exp $  # $OpenLDAP: pkg/openldap-guide/admin/quickstart.sdf,v 1.13 2000/07/23 05:35:40 kurt Exp $
 # Copyright 1999-2000, The OpenLDAP Foundation, All Rights Reserved.  # Copyright 1999-2000, The OpenLDAP Foundation, All Rights Reserved.
 # COPYING RESTRICTIONS APPLY, see COPYRIGHT.  # COPYING RESTRICTIONS APPLY, see COPYRIGHT.
   
 H1: A Quick-Start Guide to Running slapd  H1: A Quick-Start Guide to Running slapd
   
 This section provides a quick step-by-step guide to building,  This chapter provides a quick step-by-step guide to building,
 installing and running {{I:slapd}}. It is intended to provide users with a  installing and running {{slapd}}(8). It is intended to provide
 simple and quick way to get started only. If you intend to run slapd  users with a simple and quick way to get started only.
 seriously, you should read the rest of this guide.  If you intend to run slapd seriously, you should read the rest
   of this guide.
   
   
   Note: This guide does not use strong authentication nor any
   privacy and integrity protection services.  These services are
   described in detail in later chapters.  This guide should
   only be used in isolated environments (such as on a single
   host protected by a firewall).
   
   
 ^{{B:Get the software}}.  ^{{B:Get the software}}.
   
 .{{I:Slapd}} is part of the OpenLDAP distribution, which  .{{slapd}} is part of the {{PRD:OpenLDAP}} distribution, which
 you can retrieve from {{URL: http://www.openldap.org/software/download/}}  you can retrieve from {{URL: http://www.openldap.org/software/download/}}
 or {{URL: ftp://ftp.openldap.org/pub/OpenLDAP/openldap-release.tgz}}.  or {{URL: ftp://ftp.openldap.org/pub/OpenLDAP/openldap-release.tgz}}.
 If you are reading this guide, you have probably already done this.  If you are reading this guide, you have probably already done this.
Line 34  name of the release. Line 42  name of the release.
 .{{S: }}  .{{S: }}
 +{{B: Configure the software}}.  +{{B: Configure the software}}.
   
 .You will need to run the configure script to configure slapd.  .You will need to run the {{EX:configure}} script to configure slapd.
   
 ..{{EX:./configure}}  ..{{EX:./configure}}
   
 . Configure accepts many command line options that enable or disable  . The {{EX:configure}} accepts many command line options that enable
 optional features in slapd.  Usually the defaults are okay, but you  or disable optional software features.  Usually the defaults are okay,
 may want to change them.  To get a complete list of options that configure   but you may want to change them.  To get a complete list of options
 accepts, use the {{EX:--help}} option.  that {{EX:configure}} accepts, use the {{EX:--help}} option.
   
 ..{{EX:./configure --help}}  ..{{EX:./configure --help}}
   
 . Once OpenLDAP has been configured, it needs to be compiled.    . Once OpenLDAP has been configured, it needs to be compiled.  
 You'll need to make dependencies and then compile the software.  You'll need to construct dependencies and then compile the software
   using {{make}}(1) utility.
 For example:  For example:
   
 ..{{EX:make depend}}  ..{{EX:make depend}}
Line 55  For example: Line 64  For example:
 . Once OpenLDAP is compiled you need to install it.  By default OpenLDAP   . Once OpenLDAP is compiled you need to install it.  By default OpenLDAP 
 is installed into {{F:/usr/local}}.  This is typically done as root.  is installed into {{F:/usr/local}}.  This is typically done as root.
   
 ..{{EX:su root}}  ..{{EX:su root -c 'make install'}}
 ..{{EX:make install}}  
   
   
 .{{S: }}  .{{S: }}
 +{{B:Edit the configuration file}}.  +{{B:Edit the configuration file}}.
   
 .Use this section as a brief guide.  For more details on the configuration  .Use this chapter as a brief tutorial.  For more details on the
 file, see chapter 5.  configuration file, see slapd.conf(5) and chapter 5.
   
 .Now we need to edit the default configuration file that was  .Now we need to edit the default configuration file that was
 installed earlier.  The slapd configuration file {{I:slapd.conf}}(5)  installed earlier.  The {{slapd}} configuration file {{slapd.conf}}(5)
 for is normally located at {{F:/usr/local/etc/openldap/slapd.conf}}.  for is normally located at {{F:/usr/local/etc/openldap/slapd.conf}}.
 If you specified the {{EX:--prefix}} option when you ran configure,  If you specified the {{EX:--prefix}} option when you ran {{EX:configure}},
 then replace {{F:/usr/local}} with the value you gave as the  then replace {{F:/usr/local}} with the value you gave as the
 prefix.  For example, if you ran configure as  prefix.  For example, if you ran {{EX:configure}} as
   
 ..{{EX:./configure --prefix=/opt/ldap}}  ..{{EX:./configure --prefix=/opt/ldap}}
   
Line 80  Now look in the configuration file for a Line 88  Now look in the configuration file for a
   
 ..{{EX:database          ldbm}}  ..{{EX:database          ldbm}}
   
 .This marks the begining of the database configuration for slapd.  .This marks the begining of the database configuration for {{slapd}}.
 Everything you will need to change for this example is located  Everything you will need to change for this example is located
 after this line.  after this line.
   
 .Listed below are the default settings for the database in  .Listed below are the default settings for the database in
 {{F:slapd.conf}}(5).  Lines that begin with a sharp sign ('#')  {{F:slapd.conf}}(5).  Lines that begin with a sharp sign ('{{EX:#}}')
 are considered to be comments by slapd, they have been removed  are considered to be comments by slapd, they have been removed
 from the listing below to save space.  If a line starts with  from the listing below to save space.  If a line starts with
 white space it is considered a continuation of the preceeding  white space it is considered a continuation of the preceeding
Line 111  You may specify an alternate directory v Line 119  You may specify an alternate directory v
 in the {{F:slapd.conf}} file.  The directory must exist before  in the {{F:slapd.conf}} file.  The directory must exist before
 you start the server.  you start the server.
   
   Note: Use of rootpw is deprecated in favor of strong authentication
   mechanisms.  These are described in later chapters.
   
 .{{S: }}  .{{S: }}
 +{{B:Starting the server}}.  +{{B:Starting the server}}.
   
 .You are now ready to start the server by running the command  .You are now ready to start the server by running the command
 {{I:slapd}}(8):  {{slapd}}(8):
   
 ..{{EX:/usr/local/libexec/slapd}}  ..{{EX:/usr/local/libexec/slapd}}
   
 . At this point the LDAP server is up and running, but there isn't  . At this point the LDAP server is up and running, but there isn't
 any data in the directory.  You can check to see if the server is  any data in the directory.  You can check to see if the server is
 running and your naming context (the {{EX:suffix}} you specified above)  running and your naming context (the {{EX:suffix}} you specified above)
 by searching it with {{I:ldapsearch}}(1).  By default ldapsearch is  by searching it with {{ldapsearch}}(1).  By default ldapsearch is
 installed as {{F:/usr/local/bin/ldapsearch}}.  installed as {{F:/usr/local/bin/ldapsearch}}.
   
 ..{{EX:ldapsearch -x -b '' -s base '(objectclass=*)' namingContexts}}  ..{{EX:ldapsearch -x -b '' -s base '(objectclass=*)' namingContexts}}
   
 .Note the use of single quotes around command parameters to prevent  . Note the use of single quotes around command parameters to prevent
 special characters from interpreted by the shell.  This should return:  special characters from interpreted by the shell.  This should return:
   
 ..{{EX:dn:}}  ..{{EX:dn:}}
Line 160  include additional entries and attribute Line 170  include additional entries and attribute
 or add them later via LDAP.  or add them later via LDAP.
   
 .The second step is to run a tool to add the contents of this file to the  .The second step is to run a tool to add the contents of this file to the
 your directory.  We use the tool {{I:ldapadd}}(1) to populate the directory.  your directory.  We use the tool {{ldapadd}}(1) to populate the directory.
 Again remember to replace {{EX:dc=example, dc=net}} with the correct values  Again remember to replace {{EX:dc=example, dc=net}} with the correct values
 for your site.  By default ldapadd is installed as  for your site.  By default ldapadd is installed as
 {{F:/usr/local/bin/ldapadd}}.  {{F:/usr/local/bin/ldapadd}}.
Line 169  for your site.  By default ldapadd is in Line 179  for your site.  By default ldapadd is in
   
 .Where {{F:example.ldif}} is the file you created above.  .Where {{F:example.ldif}} is the file you created above.
   
   Note: Use of transport security services is recommended when updating
   the directory.  These services are described in later chapters.
   
   
 .{{S: }}  .{{S: }}
 +{{B:See if it works}}.  +{{B:See if it works}}.
   
 .Now we're ready to verify the added entries are in your directory.    .Now we're ready to verify the added entries are in your directory.  
 You can use any LDAP client to do this, but our example uses the  You can use any LDAP client to do this, but our example uses the
 {{I:ldapsearch}}(1) tool.  Remember to replace {{EX:dc=example,dc=net}}  {{ldapsearch}}(1) tool.  Remember to replace {{EX:dc=example,dc=net}}
 with the correct values for your site.  with the correct values for your site.
   
 ..{{EX:ldapsearch -x -b 'dc=example,dc=net' '(objectclass=*)'}}  ..{{EX:ldapsearch -x -b 'dc=example,dc=net' '(objectclass=*)'}}
   
 .This command will search for and retrieve every entry in the database.  .This command will search for and retrieve every entry in the database.
   
 You are now ready to add more entries using {{I:ldapadd}}(1) or  You are now ready to add more entries using {{ldapadd}}(1) or
 another LDAP client, experiment with various configuration options,  another LDAP client, experiment with various configuration options,
 backend arrangements, etc. Note that by default, the {{I:slapd}}(8)  backend arrangements, etc. Note that by default, the {{slapd}}(8)
 database grants {{I:read access to everybody}}. So if you want to add  database grants {{read access to everybody}} excepting the
 or modify entries over LDAP, you will have to bind as the {{EX:rootdn}}  {{super-user}} (as specified by the {{EX:rootdn}} configuration
 specified in the config file (see Section 5.2.2), or change the  directive).  It is highly recommended that you establish controls
 default access control (see Section 5.3).  to restrict access to authorized users.  Access controls are discussed
   in a later chapter.
   
 The following sections provide more detailed information on making,  The following chapters provide more detailed information on making,
 installing, and running {{I:slapd}}(8).  installing, and running {{slapd}}(8).
   

Removed from v.1.13  
changed lines
  Added in v.1.14


______________
© Copyright 1998-2020, OpenLDAP Foundation, info@OpenLDAP.org