From commits-return-34806-apmail-directory-commits-archive=directory.apache.org@directory.apache.org Mon Oct 29 14:27:07 2012 Return-Path: X-Original-To: apmail-directory-commits-archive@www.apache.org Delivered-To: apmail-directory-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2A1AAD71B for ; Mon, 29 Oct 2012 14:27:07 +0000 (UTC) Received: (qmail 14699 invoked by uid 500); 29 Oct 2012 14:27:06 -0000 Delivered-To: apmail-directory-commits-archive@directory.apache.org Received: (qmail 14670 invoked by uid 500); 29 Oct 2012 14:27:06 -0000 Mailing-List: contact commits-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@directory.apache.org Delivered-To: mailing list commits@directory.apache.org Received: (qmail 14663 invoked by uid 99); 29 Oct 2012 14:27:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Oct 2012 14:27:06 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Oct 2012 14:26:58 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 415AC2388A5B for ; Mon, 29 Oct 2012 14:26:12 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r836492 [2/2] - in /websites/staging/directory/trunk/content: ./ apacheds/ apacheds/basic-ug/ Date: Mon, 29 Oct 2012 14:26:10 -0000 To: commits@directory.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20121029142612.415AC2388A5B@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Added: websites/staging/directory/trunk/content/apacheds/basic-ug/3.2-basic-authorization.html ============================================================================== --- websites/staging/directory/trunk/content/apacheds/basic-ug/3.2-basic-authorization.html (added) +++ websites/staging/directory/trunk/content/apacheds/basic-ug/3.2-basic-authorization.html Mon Oct 29 14:26:09 2012 @@ -0,0 +1,255 @@ + + + + + 1.4.1 - Changing the server port for LDAP — Apache Directory + + + + + + +
+ +
+
+ + + +
+
+ + + + + +

1.4.1 - Changing the server port for LDAP

+

This section describes how to change to port for the LDAP protocol. There are two ways to do that : either you use the configuration plugin available in Apache Directory Studio, or you update the LDIF partition that contains the configuration.

+ +

The task and how to accomplish it

+

By default the LDAP server listens on port 10389 (unencrypted or StartTLS) and 10636 (SSL). It is quite common to run LDAP on 389, which is the well-known port for this protocol, but that requires the server to be started with a root user (or with sudo). Of course other options are imaginable as well. Changing the LDAP port is a good example for adjusting the existing Spring configuration as introduced in the last section.

+

+Due to traditional Unix security restrictions, ports less than 1024 were "trusted". Thus on a Unix-System, a non-root process must listen on a port greater than 1023. +

+

Basically, there are two cases : + The server is not started + The server is started

+

We will see how to change the port in those two cases.

+

Using Apache Directory Studio

+

The server is started

+

The best solution is to connect on the server using Studio, and to open it's configuration :

+

+Studio port configuration +

+

When you select this menu, you will get the main configuration screen, containing the port for LDAP and LDAPS :

+

+Studio port configuration +

+

Now, change the values of port to your needs, then save the configuration. You have to restart the server afterwards in order to take this change into effect.

+

The server is not started

+

You can start it and update the configuration, of course. But if you want to configure the server when it's stopped, you will have to load the configuration file, which is on .../instances/default/conf/config.ldif, when the server has been installed using the default setting.

+

Opening this file will open the exact same window :

+

+Studio port configuration +

+

You can update the ports and save the file.

+

+ Note that you will requite write access on this file ! +

+

Modifying the configuration LDIF partition

+

All the ApacheDS configuration is stored as a LDIF file, and can be modified either using a text editor (although we don't consider this as a safe practice) or using a Modify request on a running server.

+

+ Modifying the configuration on a running server will not change the listening port of the running server. You will have to relaunch the server in order to get this new configuration to be available. +

+

The configuration is stored as a set of LDAP entries, so you can update one of them. In order to modify the entry containing the ports, you have first to find it, and second to send a valid modify request.

+

All the ApacheDS configuration is stored under the ou=config partition. The ports are stored in some entries under DN: ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ads-directoryServiceId=default,ou=config (obviously, dependning on your installation, this DN might change : the ads-directoryServiceId may have a different name, so is the ads-serverId). In any case, the ou=transports branch contains two entries :

+

for LDAP :

+
dn: ads-transportid=ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ad
+ s-directoryServiceId=default,ou=config
+ads-systemport: 10389
+ads-enabled: TRUE
+ads-transportnbthreads: 8
+ads-transportaddress: 0.0.0.0
+ads-transportid: ldap
+objectclass: ads-transport
+objectclass: ads-tcpTransport
+objectclass: ads-base
+objectclass: top
+
+ + +

and for LDAPS :

+
dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,a
+ ds-directoryServiceId=default,ou=config
+ads-systemport: 10636
+ads-transportenablessl: TRUE
+ads-enabled: TRUE
+ads-transportaddress: 0.0.0.0
+ads-transportid: ldaps
+objectclass: ads-transport
+objectclass: ads-tcpTransport
+objectclass: ads-base
+objectclass: top
+
+ + +

You just have to send a ModifyRequest using such a LDIF :

+
dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,ads
+ -directoryServiceId=default,ou=config
+changetype: modify
+replace: ads-systemport
+ads-systemport: 10637
+-
+
+ + +

(here, we have modified the LDAPS Port from 10636 to 10637)

+

Those modification can be done directly on the config.ldif file, but you won't have any syntax check if you do so.

+ + + + + +
+
+
+ +
+ + \ No newline at end of file Added: websites/staging/directory/trunk/content/apacheds/basic-ug/3.3-enabling-ssl.html ============================================================================== --- websites/staging/directory/trunk/content/apacheds/basic-ug/3.3-enabling-ssl.html (added) +++ websites/staging/directory/trunk/content/apacheds/basic-ug/3.3-enabling-ssl.html Mon Oct 29 14:26:09 2012 @@ -0,0 +1,255 @@ + + + + + 1.4.1 - Changing the server port for LDAP — Apache Directory + + + + + + +
+ +
+
+ + + +
+
+ + + + + +

1.4.1 - Changing the server port for LDAP

+

This section describes how to change to port for the LDAP protocol. There are two ways to do that : either you use the configuration plugin available in Apache Directory Studio, or you update the LDIF partition that contains the configuration.

+ +

The task and how to accomplish it

+

By default the LDAP server listens on port 10389 (unencrypted or StartTLS) and 10636 (SSL). It is quite common to run LDAP on 389, which is the well-known port for this protocol, but that requires the server to be started with a root user (or with sudo). Of course other options are imaginable as well. Changing the LDAP port is a good example for adjusting the existing Spring configuration as introduced in the last section.

+

+Due to traditional Unix security restrictions, ports less than 1024 were "trusted". Thus on a Unix-System, a non-root process must listen on a port greater than 1023. +

+

Basically, there are two cases : + The server is not started + The server is started

+

We will see how to change the port in those two cases.

+

Using Apache Directory Studio

+

The server is started

+

The best solution is to connect on the server using Studio, and to open it's configuration :

+

+Studio port configuration +

+

When you select this menu, you will get the main configuration screen, containing the port for LDAP and LDAPS :

+

+Studio port configuration +

+

Now, change the values of port to your needs, then save the configuration. You have to restart the server afterwards in order to take this change into effect.

+

The server is not started

+

You can start it and update the configuration, of course. But if you want to configure the server when it's stopped, you will have to load the configuration file, which is on .../instances/default/conf/config.ldif, when the server has been installed using the default setting.

+

Opening this file will open the exact same window :

+

+Studio port configuration +

+

You can update the ports and save the file.

+

+ Note that you will requite write access on this file ! +

+

Modifying the configuration LDIF partition

+

All the ApacheDS configuration is stored as a LDIF file, and can be modified either using a text editor (although we don't consider this as a safe practice) or using a Modify request on a running server.

+

+ Modifying the configuration on a running server will not change the listening port of the running server. You will have to relaunch the server in order to get this new configuration to be available. +

+

The configuration is stored as a set of LDAP entries, so you can update one of them. In order to modify the entry containing the ports, you have first to find it, and second to send a valid modify request.

+

All the ApacheDS configuration is stored under the ou=config partition. The ports are stored in some entries under DN: ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ads-directoryServiceId=default,ou=config (obviously, dependning on your installation, this DN might change : the ads-directoryServiceId may have a different name, so is the ads-serverId). In any case, the ou=transports branch contains two entries :

+

for LDAP :

+
dn: ads-transportid=ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ad
+ s-directoryServiceId=default,ou=config
+ads-systemport: 10389
+ads-enabled: TRUE
+ads-transportnbthreads: 8
+ads-transportaddress: 0.0.0.0
+ads-transportid: ldap
+objectclass: ads-transport
+objectclass: ads-tcpTransport
+objectclass: ads-base
+objectclass: top
+
+ + +

and for LDAPS :

+
dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,a
+ ds-directoryServiceId=default,ou=config
+ads-systemport: 10636
+ads-transportenablessl: TRUE
+ads-enabled: TRUE
+ads-transportaddress: 0.0.0.0
+ads-transportid: ldaps
+objectclass: ads-transport
+objectclass: ads-tcpTransport
+objectclass: ads-base
+objectclass: top
+
+ + +

You just have to send a ModifyRequest using such a LDIF :

+
dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,ads
+ -directoryServiceId=default,ou=config
+changetype: modify
+replace: ads-systemport
+ads-systemport: 10637
+-
+
+ + +

(here, we have modified the LDAPS Port from 10636 to 10637)

+

Those modification can be done directly on the config.ldif file, but you won't have any syntax check if you do so.

+ + + + + +
+
+
+ +
+ + \ No newline at end of file Added: websites/staging/directory/trunk/content/apacheds/basic-ug/4-integrating-apacheds.html ============================================================================== --- websites/staging/directory/trunk/content/apacheds/basic-ug/4-integrating-apacheds.html (added) +++ websites/staging/directory/trunk/content/apacheds/basic-ug/4-integrating-apacheds.html Mon Oct 29 14:26:09 2012 @@ -0,0 +1,255 @@ + + + + + 1.4.1 - Changing the server port for LDAP — Apache Directory + + + + + + +
+ +
+
+ + + +
+
+ + + + + +

1.4.1 - Changing the server port for LDAP

+

This section describes how to change to port for the LDAP protocol. There are two ways to do that : either you use the configuration plugin available in Apache Directory Studio, or you update the LDIF partition that contains the configuration.

+ +

The task and how to accomplish it

+

By default the LDAP server listens on port 10389 (unencrypted or StartTLS) and 10636 (SSL). It is quite common to run LDAP on 389, which is the well-known port for this protocol, but that requires the server to be started with a root user (or with sudo). Of course other options are imaginable as well. Changing the LDAP port is a good example for adjusting the existing Spring configuration as introduced in the last section.

+

+Due to traditional Unix security restrictions, ports less than 1024 were "trusted". Thus on a Unix-System, a non-root process must listen on a port greater than 1023. +

+

Basically, there are two cases : + The server is not started + The server is started

+

We will see how to change the port in those two cases.

+

Using Apache Directory Studio

+

The server is started

+

The best solution is to connect on the server using Studio, and to open it's configuration :

+

+Studio port configuration +

+

When you select this menu, you will get the main configuration screen, containing the port for LDAP and LDAPS :

+

+Studio port configuration +

+

Now, change the values of port to your needs, then save the configuration. You have to restart the server afterwards in order to take this change into effect.

+

The server is not started

+

You can start it and update the configuration, of course. But if you want to configure the server when it's stopped, you will have to load the configuration file, which is on .../instances/default/conf/config.ldif, when the server has been installed using the default setting.

+

Opening this file will open the exact same window :

+

+Studio port configuration +

+

You can update the ports and save the file.

+

+ Note that you will requite write access on this file ! +

+

Modifying the configuration LDIF partition

+

All the ApacheDS configuration is stored as a LDIF file, and can be modified either using a text editor (although we don't consider this as a safe practice) or using a Modify request on a running server.

+

+ Modifying the configuration on a running server will not change the listening port of the running server. You will have to relaunch the server in order to get this new configuration to be available. +

+

The configuration is stored as a set of LDAP entries, so you can update one of them. In order to modify the entry containing the ports, you have first to find it, and second to send a valid modify request.

+

All the ApacheDS configuration is stored under the ou=config partition. The ports are stored in some entries under DN: ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ads-directoryServiceId=default,ou=config (obviously, dependning on your installation, this DN might change : the ads-directoryServiceId may have a different name, so is the ads-serverId). In any case, the ou=transports branch contains two entries :

+

for LDAP :

+
dn: ads-transportid=ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ad
+ s-directoryServiceId=default,ou=config
+ads-systemport: 10389
+ads-enabled: TRUE
+ads-transportnbthreads: 8
+ads-transportaddress: 0.0.0.0
+ads-transportid: ldap
+objectclass: ads-transport
+objectclass: ads-tcpTransport
+objectclass: ads-base
+objectclass: top
+
+ + +

and for LDAPS :

+
dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,a
+ ds-directoryServiceId=default,ou=config
+ads-systemport: 10636
+ads-transportenablessl: TRUE
+ads-enabled: TRUE
+ads-transportaddress: 0.0.0.0
+ads-transportid: ldaps
+objectclass: ads-transport
+objectclass: ads-tcpTransport
+objectclass: ads-base
+objectclass: top
+
+ + +

You just have to send a ModifyRequest using such a LDIF :

+
dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,ads
+ -directoryServiceId=default,ou=config
+changetype: modify
+replace: ads-systemport
+ads-systemport: 10637
+-
+
+ + +

(here, we have modified the LDAPS Port from 10636 to 10637)

+

Those modification can be done directly on the config.ldif file, but you won't have any syntax check if you do so.

+ + + + + +
+
+
+ +
+ + \ No newline at end of file Added: websites/staging/directory/trunk/content/apacheds/basic-ug/4.1-mozilla-thunderbird.html ============================================================================== --- websites/staging/directory/trunk/content/apacheds/basic-ug/4.1-mozilla-thunderbird.html (added) +++ websites/staging/directory/trunk/content/apacheds/basic-ug/4.1-mozilla-thunderbird.html Mon Oct 29 14:26:09 2012 @@ -0,0 +1,255 @@ + + + + + 1.4.1 - Changing the server port for LDAP — Apache Directory + + + + + + +
+ +
+
+ + + +
+
+ + + + + +

1.4.1 - Changing the server port for LDAP

+

This section describes how to change to port for the LDAP protocol. There are two ways to do that : either you use the configuration plugin available in Apache Directory Studio, or you update the LDIF partition that contains the configuration.

+ +

The task and how to accomplish it

+

By default the LDAP server listens on port 10389 (unencrypted or StartTLS) and 10636 (SSL). It is quite common to run LDAP on 389, which is the well-known port for this protocol, but that requires the server to be started with a root user (or with sudo). Of course other options are imaginable as well. Changing the LDAP port is a good example for adjusting the existing Spring configuration as introduced in the last section.

+

+Due to traditional Unix security restrictions, ports less than 1024 were "trusted". Thus on a Unix-System, a non-root process must listen on a port greater than 1023. +

+

Basically, there are two cases : + The server is not started + The server is started

+

We will see how to change the port in those two cases.

+

Using Apache Directory Studio

+

The server is started

+

The best solution is to connect on the server using Studio, and to open it's configuration :

+

+Studio port configuration +

+

When you select this menu, you will get the main configuration screen, containing the port for LDAP and LDAPS :

+

+Studio port configuration +

+

Now, change the values of port to your needs, then save the configuration. You have to restart the server afterwards in order to take this change into effect.

+

The server is not started

+

You can start it and update the configuration, of course. But if you want to configure the server when it's stopped, you will have to load the configuration file, which is on .../instances/default/conf/config.ldif, when the server has been installed using the default setting.

+

Opening this file will open the exact same window :

+

+Studio port configuration +

+

You can update the ports and save the file.

+

+ Note that you will requite write access on this file ! +

+

Modifying the configuration LDIF partition

+

All the ApacheDS configuration is stored as a LDIF file, and can be modified either using a text editor (although we don't consider this as a safe practice) or using a Modify request on a running server.

+

+ Modifying the configuration on a running server will not change the listening port of the running server. You will have to relaunch the server in order to get this new configuration to be available. +

+

The configuration is stored as a set of LDAP entries, so you can update one of them. In order to modify the entry containing the ports, you have first to find it, and second to send a valid modify request.

+

All the ApacheDS configuration is stored under the ou=config partition. The ports are stored in some entries under DN: ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ads-directoryServiceId=default,ou=config (obviously, dependning on your installation, this DN might change : the ads-directoryServiceId may have a different name, so is the ads-serverId). In any case, the ou=transports branch contains two entries :

+

for LDAP :

+
dn: ads-transportid=ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ad
+ s-directoryServiceId=default,ou=config
+ads-systemport: 10389
+ads-enabled: TRUE
+ads-transportnbthreads: 8
+ads-transportaddress: 0.0.0.0
+ads-transportid: ldap
+objectclass: ads-transport
+objectclass: ads-tcpTransport
+objectclass: ads-base
+objectclass: top
+
+ + +

and for LDAPS :

+
dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,a
+ ds-directoryServiceId=default,ou=config
+ads-systemport: 10636
+ads-transportenablessl: TRUE
+ads-enabled: TRUE
+ads-transportaddress: 0.0.0.0
+ads-transportid: ldaps
+objectclass: ads-transport
+objectclass: ads-tcpTransport
+objectclass: ads-base
+objectclass: top
+
+ + +

You just have to send a ModifyRequest using such a LDIF :

+
dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,ads
+ -directoryServiceId=default,ou=config
+changetype: modify
+replace: ads-systemport
+ads-systemport: 10637
+-
+
+ + +

(here, we have modified the LDAPS Port from 10636 to 10637)

+

Those modification can be done directly on the config.ldif file, but you won't have any syntax check if you do so.

+ + + + + +
+
+
+ +
+ + \ No newline at end of file Modified: websites/staging/directory/trunk/content/apacheds/basic-users-guide.html ============================================================================== --- websites/staging/directory/trunk/content/apacheds/basic-users-guide.html (original) +++ websites/staging/directory/trunk/content/apacheds/basic-users-guide.html Mon Oct 29 14:26:09 2012 @@ -135,7 +135,7 @@
  • 1.5 - About the sample configurations and sample directory data
  • -
  • 2 - Handling of data within your directory
  • +
  • 2 - Handling of data within your directory
  • 3 - Basic Security