-
Notifications
You must be signed in to change notification settings - Fork 40
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #240 from xavierba/unix_eol
Convert files from DOS to Unix end of line
- Loading branch information
Showing
7 changed files
with
267 additions
and
267 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,9 +1,9 @@ | ||
| id;uid;endOfValidity;sn;cn;givenName;mail;o;address;telephoneNumber;carLicense | ||
| 1;j.clarke;31/12/2015;Clarke;Clarke, Jonathan;Jonathan;jonathan@philipoux.net;Normation;;+33 (0)1 83 62 26 96;BHU772|DED899 | ||
| 2;r.schermesser;31/12/2015;Schermesser;Schermesser, Remy-Christophe;Remy-Christophe;remy@schermesser.com;Octo;;; | ||
| 3;t.chemineau;31/12/2015;Chemineau;Chemineau, Thomas;Thomas;thomas@aepik.net;AFNOR;;; | ||
| 4;s.bahloul;31/12/2015;Bahloul;Bahloul, Sebastien;Sebastien;sebastien.bahloul@gmail.com;Dictao;156 av. de Malakof, 75116 PARIS, France;; | ||
| 5;c.oudot;31/12/2015;Oudot;Oudot, Clement;Clement;clem.oudot@gmail.com;Linagora;;33(0)810251251; | ||
| 6;r.ouazana;31/12/2015;Ouazana;Ouazana, Raphael;Raphael;rouazana@linagora.com;Linagora;;33(0)810251251; | ||
| 7;d.coutadeur;31/12/2015;Coutadeur;Coutadeur, David;David;dcoutadeur@linagora.com;Linagora;;33(0)810251251; | ||
| 8;e.pereira;31/12/2015;Pereira;Pereira, Esteban;Esteban;epereira@linagora.com;Linagora;;33(0)810251251; | ||
| id;uid;endOfValidity;sn;cn;givenName;mail;o;address;telephoneNumber;carLicense | ||
| 1;j.clarke;31/12/2015;Clarke;Clarke, Jonathan;Jonathan;jonathan@philipoux.net;Normation;;+33 (0)1 83 62 26 96;BHU772|DED899 | ||
| 2;r.schermesser;31/12/2015;Schermesser;Schermesser, Remy-Christophe;Remy-Christophe;remy@schermesser.com;Octo;;; | ||
| 3;t.chemineau;31/12/2015;Chemineau;Chemineau, Thomas;Thomas;thomas@aepik.net;AFNOR;;; | ||
| 4;s.bahloul;31/12/2015;Bahloul;Bahloul, Sebastien;Sebastien;sebastien.bahloul@gmail.com;Dictao;156 av. de Malakof, 75116 PARIS, France;; | ||
| 5;c.oudot;31/12/2015;Oudot;Oudot, Clement;Clement;clem.oudot@gmail.com;Linagora;;33(0)810251251; | ||
| 6;r.ouazana;31/12/2015;Ouazana;Ouazana, Raphael;Raphael;rouazana@linagora.com;Linagora;;33(0)810251251; | ||
| 7;d.coutadeur;31/12/2015;Coutadeur;Coutadeur, David;David;dcoutadeur@linagora.com;Linagora;;33(0)810251251; | ||
| 8;e.pereira;31/12/2015;Pereira;Pereira, Esteban;Esteban;epereira@linagora.com;Linagora;;33(0)810251251; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,52 +1,52 @@ | ||
| This README file is describing how to setup a sample PostgreSQL server and to | ||
| setup the synchronization from an OpenDJ instance. | ||
| REQUIREMENTS | ||
| ------------ | ||
| First, please check that you have downloaded and deployed the PostgreSQL | ||
| JDBC jar from the PostgreSQL community website. This sample has been tested | ||
| with PostgreSQL-8.4-702-jdbc4.jar but may worked with any feature release and | ||
| also previous release, but with a transactional support. | ||
| POSTGRESQL SERVER SETUP | ||
| ----------------------- | ||
| This sample suppose that the SQL server is installed and correctly setup. | ||
| Please open a psql command line with database administrator rights on the | ||
| embedded postgres database and drop any existing database and role lsc, BUT | ||
| TAKE CARE THAT YOU HAVE ALREADY BACKUPED ANY EXISTING DATA : | ||
| postgres=# DROP DATABASE IF EXISTS lsc | ||
| postgres=# DROP ROLE IF EXISTS lsc | ||
| Go in the right directory and launch the creation script : | ||
| postgres=# \cd $LSC_HOME/sample/postgresql | ||
| postgres=# \i create.sql | ||
| You should see some information message and maybe some warnings. If you don't | ||
| encountered an error, you can continue at the following step. If not, check | ||
| which is the first SQL command that has failed and solved the issue before | ||
| relaunching a copy of the script in which you will have copied only the SQL | ||
| commands that have not succeed first time. | ||
| LSC SETUP | ||
| --------- | ||
| You will find in the etc subdirectory a correct configuration to use with | ||
| newly setup server. You need to edit the lsc.xml to change the server IP | ||
| address, TCP port, username and password : | ||
| <url>jdbc:postgresql://127.0.0.1:5432/lsc</url> | ||
| <username>lsc</username> | ||
| <password>lsc</password> | ||
| This sample requires that you start the embedded OpenDJ LDAP server: | ||
| $ sample/hsqldb/bin/lsc-sample --start-ldap-server | ||
| Then, launch the LSC in a command line | ||
| $ bin/lsc -f sample/postgresql/etc -s all | ||
| And now you should get a OpenDJ and a PostgreSQL synchronized : | ||
| you should see a add operation which will add an entry inside your lsc database | ||
| and inetorgperson table. | ||
| This README file is describing how to setup a sample PostgreSQL server and to | ||
| setup the synchronization from an OpenDJ instance. | ||
|
|
||
| REQUIREMENTS | ||
| ------------ | ||
|
|
||
| First, please check that you have downloaded and deployed the PostgreSQL | ||
| JDBC jar from the PostgreSQL community website. This sample has been tested | ||
| with PostgreSQL-8.4-702-jdbc4.jar but may worked with any feature release and | ||
| also previous release, but with a transactional support. | ||
|
|
||
| POSTGRESQL SERVER SETUP | ||
| ----------------------- | ||
| This sample suppose that the SQL server is installed and correctly setup. | ||
| Please open a psql command line with database administrator rights on the | ||
| embedded postgres database and drop any existing database and role lsc, BUT | ||
| TAKE CARE THAT YOU HAVE ALREADY BACKUPED ANY EXISTING DATA : | ||
|
|
||
| postgres=# DROP DATABASE IF EXISTS lsc | ||
| postgres=# DROP ROLE IF EXISTS lsc | ||
|
|
||
| Go in the right directory and launch the creation script : | ||
|
|
||
| postgres=# \cd $LSC_HOME/sample/postgresql | ||
| postgres=# \i create.sql | ||
|
|
||
| You should see some information message and maybe some warnings. If you don't | ||
| encountered an error, you can continue at the following step. If not, check | ||
| which is the first SQL command that has failed and solved the issue before | ||
| relaunching a copy of the script in which you will have copied only the SQL | ||
| commands that have not succeed first time. | ||
|
|
||
| LSC SETUP | ||
| --------- | ||
|
|
||
| You will find in the etc subdirectory a correct configuration to use with | ||
| newly setup server. You need to edit the lsc.xml to change the server IP | ||
| address, TCP port, username and password : | ||
|
|
||
| <url>jdbc:postgresql://127.0.0.1:5432/lsc</url> | ||
| <username>lsc</username> | ||
| <password>lsc</password> | ||
|
|
||
| This sample requires that you start the embedded OpenDJ LDAP server: | ||
| $ sample/hsqldb/bin/lsc-sample --start-ldap-server | ||
|
|
||
| Then, launch the LSC in a command line | ||
| $ bin/lsc -f sample/postgresql/etc -s all | ||
|
|
||
| And now you should get a OpenDJ and a PostgreSQL synchronized : | ||
| you should see a add operation which will add an entry inside your lsc database | ||
| and inetorgperson table. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,35 +1,35 @@ | ||
| CREATE ROLE lsc LOGIN | ||
| ENCRYPTED PASSWORD 'md5809ead1da2f082b19e643d95a616110f' | ||
| NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE; | ||
|
|
||
| CREATE DATABASE lsc | ||
| WITH OWNER = lsc | ||
| ENCODING = 'UTF8' | ||
| TABLESPACE = pg_default | ||
| CONNECTION LIMIT = -1; | ||
|
|
||
| \c lsc | ||
|
|
||
| CREATE SEQUENCE public.inetorgperson_pkey | ||
| INCREMENT 1 | ||
| MINVALUE 1 | ||
| MAXVALUE 9223372036854775807 | ||
| START 1 | ||
| CACHE 1; | ||
|
|
||
| ALTER TABLE public.inetorgperson_pkey OWNER TO lsc; | ||
|
|
||
| CREATE TABLE public.inetorgperson | ||
| ( | ||
| uid character varying(255) NOT NULL, | ||
| sn character varying(255) NOT NULL, | ||
| givenname character varying(255), | ||
| cn character varying(512) NOT NULL, | ||
| mail character varying(255) NOT NULL, | ||
| address character varying(512), | ||
| telephonenumber character varying(255), | ||
| id bigint NOT NULL DEFAULT nextval('inetorgperson_pkey'::regclass), | ||
| CONSTRAINT inetorgperson_pkey1 PRIMARY KEY (id) | ||
| ); | ||
|
|
||
| GRANT ALL ON TABLE public.inetorgperson TO lsc; | ||
| CREATE ROLE lsc LOGIN | ||
| ENCRYPTED PASSWORD 'md5809ead1da2f082b19e643d95a616110f' | ||
| NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE; | ||
|
|
||
| CREATE DATABASE lsc | ||
| WITH OWNER = lsc | ||
| ENCODING = 'UTF8' | ||
| TABLESPACE = pg_default | ||
| CONNECTION LIMIT = -1; | ||
|
|
||
| \c lsc | ||
|
|
||
| CREATE SEQUENCE public.inetorgperson_pkey | ||
| INCREMENT 1 | ||
| MINVALUE 1 | ||
| MAXVALUE 9223372036854775807 | ||
| START 1 | ||
| CACHE 1; | ||
|
|
||
| ALTER TABLE public.inetorgperson_pkey OWNER TO lsc; | ||
|
|
||
| CREATE TABLE public.inetorgperson | ||
| ( | ||
| uid character varying(255) NOT NULL, | ||
| sn character varying(255) NOT NULL, | ||
| givenname character varying(255), | ||
| cn character varying(512) NOT NULL, | ||
| mail character varying(255) NOT NULL, | ||
| address character varying(512), | ||
| telephonenumber character varying(255), | ||
| id bigint NOT NULL DEFAULT nextval('inetorgperson_pkey'::regclass), | ||
| CONSTRAINT inetorgperson_pkey1 PRIMARY KEY (id) | ||
| ); | ||
|
|
||
| GRANT ALL ON TABLE public.inetorgperson TO lsc; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,68 +1,68 @@ | ||
| This README file is describing how to setup a sample NIS server and to setup | ||
| the synchronization. | ||
| REQUIREMENTS | ||
| ------------ | ||
| First, please check that you have downloaded and deployed the nis plugin jar | ||
| from LSC Project main website. Please also check that you have the nis jar | ||
| provided by Oracle (ex Sun) and note that this dependency is not Open Source | ||
| and is licensed under the Sun Binary license and thus can not be | ||
| redistributed freely. | ||
| NIS SERVER SETUP | ||
| ---------------- | ||
| Then connect to your Debian box and install the nis package : | ||
| $ su - | ||
| $ apt-get install nis | ||
| At this step, please wait until ypbind timeouts because your NIS server is | ||
| not already setup. Then go to /var/yp and create the required domain directory | ||
| structure : | ||
| $ cd /var/yp | ||
| $ mkdir -p lsc-project.org | ||
| $ cd lsc-project.org | ||
| $ make -f ../Makefile all | ||
| You may get some warning message about unregistered RPC service. You can safely | ||
| ignore them. Then check your installation by launching the server in debug mode | ||
| $ ypserv -d | ||
| Then launch the ypbind client in debug mode to check for connection correctness | ||
| $ ypbind -d | ||
| You must see that the connection is well established. Then open a new terminal | ||
| and check for the final test through the ypcat client : | ||
| $ ypcat passwd | ||
| You must see your current accounts shown there and that's it. | ||
| Then stop both daemon started in debug mode and start them again without the | ||
| -d flag. They will daemonize themselves, and it's now time to setup LSC. | ||
| LSC SETUP | ||
| --------- | ||
| You will find in the etc subdirectory a correct configuration to use with | ||
| newly setup server. You need to edit the lsc.xml to change the server IP | ||
| address and the managed NIS domain in the following line : | ||
| <url>nis://NIS-SERVER-ADDRESS/lsc-project.org</url> | ||
| Note that this synchronization will lookup accounts through the | ||
| passwd.byname map : | ||
| <map>passwd.byname</map> | ||
| This means that if you want to synchronize groups, you will need to change the | ||
| map you plan to use. | ||
| This sample requires that you start the embedded OpenDJ LDAP server: | ||
| $ sample/hsqldb/bin/lsc-sample --start-ldap-server | ||
| Then, launch the LSC in a command line | ||
| $ bin/lsc -f sample/nis/etc -s passwd | ||
| And now you should get a NIS server and a directory synchronized : | ||
| you should see a renaming operation which will change the RDN of the uid=00000001 | ||
| entry to mail=test@lsc-project.org | ||
| This README file is describing how to setup a sample NIS server and to setup | ||
| the synchronization. | ||
|
|
||
| REQUIREMENTS | ||
| ------------ | ||
|
|
||
| First, please check that you have downloaded and deployed the nis plugin jar | ||
| from LSC Project main website. Please also check that you have the nis jar | ||
| provided by Oracle (ex Sun) and note that this dependency is not Open Source | ||
| and is licensed under the Sun Binary license and thus can not be | ||
| redistributed freely. | ||
|
|
||
| NIS SERVER SETUP | ||
| ---------------- | ||
| Then connect to your Debian box and install the nis package : | ||
| $ su - | ||
| $ apt-get install nis | ||
|
|
||
| At this step, please wait until ypbind timeouts because your NIS server is | ||
| not already setup. Then go to /var/yp and create the required domain directory | ||
| structure : | ||
| $ cd /var/yp | ||
| $ mkdir -p lsc-project.org | ||
| $ cd lsc-project.org | ||
| $ make -f ../Makefile all | ||
|
|
||
| You may get some warning message about unregistered RPC service. You can safely | ||
| ignore them. Then check your installation by launching the server in debug mode | ||
| $ ypserv -d | ||
|
|
||
| Then launch the ypbind client in debug mode to check for connection correctness | ||
| $ ypbind -d | ||
|
|
||
| You must see that the connection is well established. Then open a new terminal | ||
| and check for the final test through the ypcat client : | ||
| $ ypcat passwd | ||
|
|
||
| You must see your current accounts shown there and that's it. | ||
|
|
||
| Then stop both daemon started in debug mode and start them again without the | ||
| -d flag. They will daemonize themselves, and it's now time to setup LSC. | ||
|
|
||
| LSC SETUP | ||
| --------- | ||
|
|
||
| You will find in the etc subdirectory a correct configuration to use with | ||
| newly setup server. You need to edit the lsc.xml to change the server IP | ||
| address and the managed NIS domain in the following line : | ||
|
|
||
| <url>nis://NIS-SERVER-ADDRESS/lsc-project.org</url> | ||
|
|
||
| Note that this synchronization will lookup accounts through the | ||
| passwd.byname map : | ||
|
|
||
| <map>passwd.byname</map> | ||
|
|
||
| This means that if you want to synchronize groups, you will need to change the | ||
| map you plan to use. | ||
|
|
||
| This sample requires that you start the embedded OpenDJ LDAP server: | ||
| $ sample/hsqldb/bin/lsc-sample --start-ldap-server | ||
|
|
||
| Then, launch the LSC in a command line | ||
| $ bin/lsc -f sample/nis/etc -s passwd | ||
|
|
||
| And now you should get a NIS server and a directory synchronized : | ||
| you should see a renaming operation which will change the RDN of the uid=00000001 | ||
| entry to mail=test@lsc-project.org |
Oops, something went wrong.