# HG changeset patch # User weiher # Date 1522159634 -7200 # Node ID 523ca1dfd0775fd98d6b39a8f9bb87ce521a3424 # Parent a21f3604f1db52c91a6ba816c9ff33a0f737e64e added new chapter on installation of CUPS printers diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/doctrees/cups_admin_guide.doctree Binary file elog2labfolder/_build/doctrees/cups_admin_guide.doctree has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/doctrees/cups_user_guide.doctree Binary file elog2labfolder/_build/doctrees/cups_user_guide.doctree has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/doctrees/environment.pickle Binary file elog2labfolder/_build/doctrees/environment.pickle has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/doctrees/installation_cups.doctree Binary file elog2labfolder/_build/doctrees/installation_cups.doctree has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_images/create_local_printer01.png Binary file elog2labfolder/_build/html/_images/create_local_printer01.png has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_images/create_local_printer02.png Binary file elog2labfolder/_build/html/_images/create_local_printer02.png has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_images/create_local_printer03.png Binary file elog2labfolder/_build/html/_images/create_local_printer03.png has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_images/create_local_printer04.png Binary file elog2labfolder/_build/html/_images/create_local_printer04.png has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_images/create_local_printer05.png Binary file elog2labfolder/_build/html/_images/create_local_printer05.png has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_images/create_local_printer06.png Binary file elog2labfolder/_build/html/_images/create_local_printer06.png has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_images/create_local_printer07.png Binary file elog2labfolder/_build/html/_images/create_local_printer07.png has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_images/cups_print_operating.png Binary file elog2labfolder/_build/html/_images/cups_print_operating.png has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_sources/cups_admin_guide.rst.txt --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/elog2labfolder/_build/html/_sources/cups_admin_guide.rst.txt Tue Mar 27 16:07:14 2018 +0200 @@ -0,0 +1,7 @@ +.. _my-reference-label: + +Set up CUPS as labfolder admin +------------------------------ + +This is a test. + diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_sources/cups_user_guide.rst.txt diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_sources/import_export.rst.txt --- a/elog2labfolder/_build/html/_sources/import_export.rst.txt Wed Feb 07 16:53:37 2018 +0100 +++ b/elog2labfolder/_build/html/_sources/import_export.rst.txt Tue Mar 27 16:07:14 2018 +0200 @@ -13,7 +13,7 @@ Export ------ -Exporting projects (or just single entries) is possible in three different formats: PDF, XHTML and JSON. The export as PDF can be done from within a project ... +Exporting projects (or just single entries) is possible in three different formats: PDF, XHTML and JSON. The **export as PDF** can be done from within a project ... .. image:: _static/export_of_projects.png :width: 70 % @@ -25,7 +25,7 @@ :width: 70 % :align: center -The XHTML export can be done via the settings: +The **XHTML export** can be done via the settings: .. image:: _static/export_xhtml.png :width: 70 % @@ -33,5 +33,5 @@ However, to use this type of export it has to be installed first in the *Manage > Apps* section. By means of the XHTML export all projects that one owns will be exported. A detailled selection of projects or entries to be exported is not possible. As soon as the export process is finished a download link appears in the settings in *Data exports*. The downloadable ZIP file contains all images and files along with an index.html file that contains information about all entries. You could open and view the index.html file in a browser similar to the view in labfolder. -The JSON export is only useable via the API endpoint ``GET /entries``. However, at the moment the response only contains useful information such as dates and tags. The author name is hidden behind the author ID and the entry text content is completely missing. +The **JSON export** is only useable via the API endpoint ``GET /entries``. However, at the moment the response only contains useful information such as dates and tags. The author name is hidden behind the author ID and the entry text content is completely missing. diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_sources/importing_from_elog.rst.txt --- a/elog2labfolder/_build/html/_sources/importing_from_elog.rst.txt Wed Feb 07 16:53:37 2018 +0100 +++ b/elog2labfolder/_build/html/_sources/importing_from_elog.rst.txt Tue Mar 27 16:07:14 2018 +0200 @@ -39,22 +39,27 @@ $ git clone https://github.molgen.mpg.de/weiher/elog2labfolder.git -The script *elog2labfolder.py* is meant to be executed from remote, that is, not on the machine on which labfolder is running. A prerequisit is the python MySQLDB package because for a few methods the labfolder API cannot be used, instead, direct manipulation of the labfolder MySQL database is needed. The actual labfolder API is applied in the methodes collected in *myPythonAPIv1.py* and *myPythonAPIv2.py*. Mostly, API version 2 is used but adding text at the end of an entry can only be accomplished by using the version 1 API call. *getListOfAuthors.py* gives you a list of all authors in a raw ELOG export file. +The script *elog2labfolder.py* is meant to be executed from remote, that is, not on the machine on which labfolder is running. A prerequisit is the python MySQLDB package because for a few methods the labfolder API cannot be used, instead, direct manipulation of the labfolder MySQL database is needed. The actual labfolder API is applied in the methodes collected in *myPythonAPIv1.py* and *myPythonAPIv2.py*. Mostly, API version 2 is used but adding text at the end of an entry can only be accomplished by using the version 1 API call. *getListOfAuthors.py* gives you a list of all authors that are mentioned in a raw ELOG export file. -Alternatives to the manipulating the labfolder DB on MySQL level ----------------------------------------------------------------- +Alternatives to manipulating the labfolder DB on MySQL level +------------------------------------------------------------ As mentioned previously: a few methods in the python API use a direct manipulation of the labfolder DB via MySQL queries. These methods are: -* *createUserAccount(email, author, entryContent, verboseOutput, cursor, db)*: If an author of an ELOG logbook entry has not yet a labolder account this account is created on the fly by setting a default (encrypted) password. This password is irrelevant because labfolder checks the entered password with the one from the LDAP server. Note: when setting a password in the DB labfolder's LDAP authentication needs to be disabled (FEATURE_LDAP_AUTHENTICATION=false) and enabled again after the setting process is finished. +* *createUserAccount(email, author, entryContent, verboseOutput, cursor, db)*: If an author of an ELOG logbook entry does not yet have a labolder account this account is created on the fly by setting a default (encrypted) password. This password is irrelevant because labfolder checks the entered password with the one from the LDAP server. Note: when setting a password in the DB labfolder's LDAP authentication needs to be disabled (FEATURE_LDAP_AUTHENTICATION=false) beforehand and enabled again after the setting process is finished. * *updateAuthor(userID, blockID, cursor, db)*: Update the author of an entry. With the script *elog2labfolder.py* an entry is created with the author that is the person whose labfolder credentials are used to get the login token. Via this method the true author can be set to the passed in *userID*. -* *updateDateAndTime(date, blockID, cursor, db)*: Similar to *updateAuthor()* this method sets the creation and modification date to the creation time and date of the entry to be imported. This is necessary because otherwise creation and modification date are the time and date of the import of the entry. +* *updateDateAndTime(date, blockID, cursor, db)*: Similar to *updateAuthor()* this method sets the creation and modification date to the creation time and date of the entry to be imported. This is necessary because otherwise creation and modification date in labfolder are the time and date when the import took place. The labfolder support suggested the following alternative involving using the labfolder API: -* ... siehe E-Mail (gesendet) vom 15.12. ... +* User account: A user account can be created via the API 2 endpoint ``/auth/signup``. The password will be an encrypted dummy password. In order for this to work the LDAP authentication must be turned off when this endpoint is called. After the account creation LDAP authentication should be turned on again. Once the true user of this account logs in labfolder will ignore the dummy password and check the entered password against the password stored in LDAP. + +* Author: To create a labfolder entry by using the original entry's author needs a special work-around. **First, make sure to prevent labfolder users from accessing labfolder for the time of the import.** Then, manually change all user passwords in the DB to the same (encrypted) password. Switch off the LDAP authentication and restart labolder. Now, import entry by entry and get a new login token for each new entry. It is only possible to get login tokens for all users because they all have the same known password. If the author of the entry to be imported does not exist yet in the DB you need to create an account via the API 2 endpoint ``/auth/signup``. Now you reopen the access to the labfolder instance and switch on LDAP again restarting labfolder afterwards. The users can login using their FHI credentials no matter the "universal" password in the DB. If LDAP authentication is not turned on the users could do a password recovery on the login screen and re-set their password to their liking. + +* Date and time: Since you cannot change creation and modification time stamp of an entry via the API you could instead create custom dates during the import of an entry. The original entry creation timestamp could be "Original entry creation" followed by the creation time and date of the import. All entries can be filtered and searched by the custom dates. + diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_sources/index.rst.txt --- a/elog2labfolder/_build/html/_sources/index.rst.txt Wed Feb 07 16:53:37 2018 +0100 +++ b/elog2labfolder/_build/html/_sources/index.rst.txt Tue Mar 27 16:07:14 2018 +0200 @@ -11,19 +11,17 @@ :caption: Contents: installation.rst + installation_cups.rst groups.rst import_export.rst importing_from_elog.rst .. - elog2labfolder.py + DONE: elog2labfolder.py Installation von Cups - Funktion und Nutzung der labfolder-APIs - - Mit welcher API funktioniert was? - Generell nicht möglich mit den APIs: Ändern der User-ID und des Timestamps + DONE: Funktion und Nutzung der labfolder-APIs: Mit welcher API funktioniert was? Generell nicht möglich mit den APIs: Ändern der User-ID und des Timestamps Was sind die Probleme, die uns derzeit an der Umstellung hindern bzw. die uns langfristig gesehen skeptisch machen, ob Labfolder wirklich geeignet ist? @@ -35,7 +33,7 @@ Darstellung von Umlauten im elog-Export Darstellung von Text in PDFs im labfolder-PDF-Viewer (labfolder weiß Bescheid) - Informationen aus meiner E-Mail an Heinz vom 15.12. hinzufügen + DONE: Informationen aus meiner E-Mail an Heinz vom 15.12. hinzufügen Versuch einer REST-API diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_sources/installation_cups.rst.txt --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/elog2labfolder/_build/html/_sources/installation_cups.rst.txt Tue Mar 27 16:07:14 2018 +0200 @@ -0,0 +1,165 @@ +Printing via CUPS and attaching files to labfolder logbooks +=========================================================== + +Follow this guide to set up CUPS virtual printers to be able to print webpages and pictures/files (PDF, PNG, JPG, PS) to one of labfolder's logbooks, thus, creating a new entry with an attachment. If you are an admin of the labfolder VM read the section :ref:`section_cups_admin`. Users of labfolder read the section :ref:`section_cups_user`. + + +.. _section_cups_admin: + +Set up CUPS as labfolder admin +------------------------------ + +First, you need to install CUPS on the virtual machine that runs labfolder:: + + sudo apt-get install cups cups-client cups-bsd + +Next, configure ``/etc/cups/cupsd.conf``:: + + # Sample configuration file for the CUPS scheduler. See "man cupsd.conf" for a + # complete description of this file. + + # Log general information in error_log - change "warn" to "debug" + # for troubleshooting... + LogLevel debug + + # Deactivate CUPS' internal logrotating, as we provide a better one, especially + # LogLevel debug2 gets usable now + MaxLogSize 0 + + # Administrator user group... + SystemGroup lpadmin + ServerAdmin @fhi-berlin.mpg.de + + HostNameLookups On + ServerAlias * + + # Only listen for connections from the local machine. + Listen lftest.rz-berlin.mpg.de:631 + Listen /var/run/cups/cups.sock + + # Show shared printers on the local network. + Browsing Off + BrowseOrder allow,deny + BrowseAllow all + BrowseLocalProtocols CUPS dnssd + BrowseAddress @LOCAL + + # Default authentication type, when authentication is required... + DefaultAuthType Basic + + # Web interface setting... + WebInterface Yes + + # Restrict access to the server... + + Satisfy All + Allow localhost + Allow 141.14.* + Allow 172.16.* + Allow 192.* + Allow all + # Allow shared printing and remote administration... + Order allow,deny + Allow all + + + # Restrict access to the admin pages... + + Order deny,allow + Satisfy All + AuthType Basic + Require user @SYSTEM + Deny All + Allow localhost + Allow 141.14.* + Allow 172.16.* + + + # Restrict access to configuration files... + + Order deny,allow + AuthType Default + Require user @SYSTEM + Satisfy All + Require user root + Deny All + Allow 127.0.0.1 + Allow 141.14.* + Allow 172.16.* + + + # Set the default printer/job policies... + + ... # probably as in the original + + +Change the *Server Admin*'s e-mail address and the server that shall be listened to (see the ``Listen`` statement). Set ``FileDevice Yes`` in ``/etc/cups/cups-files.conf``. Now, create a directory where all printers will go, e.g. ``/usr/local/labfolder/printers``. + +Get the package for creating new printers from git:: + + labfolder@lftest:~$ git clone https://github.molgen.mpg.de/weiher/cupsPrinters + labfolder@lftest:~$ ls + cupsPrinters labfolder + +The only file you need to adapt is ``newPrinter.sh``. It is not a must but it is suggested to name the printers like the projects. For example, the FEL projects *operating* and *installation* could be placed at ``.../printers/FEL/operating`` and ``.../printers/FEL/installation``. Execute the script with sudo rights:: + + labfolder@lftest:~/cupsPrinters$ sudo ./newPrinter.sh + +To prevent ``DENIED`` errors from apparmor install and set the following and restart the CUPS server:: + + $ sudo apt-get install apparmor-utils apparmor-profiles + $ sudo aa-complain cupsd + $ sudo service cups restart + +In case you need to debug some logfiles can be found here: */var/log/syslog*, */var/log/cups/error_log* and */var/log/cups/acces_log* + +One last change is that you need to once add a user named *Printer Print* (firstname lastname) to the labfolder database. This can be done manually inside the DB by this command:: + + $ mysql -u root -p + Enter password: + ... + mysql> use labfolder; + mysql> INSERT INTO user (email, password, firstname, lastname, signupTimestamp, maxStorage) VALUES ('printer@fhi-berlin.mpg.de', '91a13f2aba4a35b00c35dfacadd1d75f4a5171dfa7a465fca9c40e6b007ce982', 'Printer', 'Print', '2018-03-21 10:54:00', '10000000'); + + +.. _section_cups_user: + +Printing to labfolder projects +------------------------------ + +The last thing you need to do is to set up a printer *operating* on your local machine. In Ubuntu Gnome hit Alt+F2 keys and enter ``system-config-printer``. In this printer config interface add a new printer *operating* as follows: + +.. image:: _static/create_local_printer01.png + :width: 70 % + :align: center + + +.. image:: _static/create_local_printer02.png + :width: 70 % + :align: center + + +.. image:: _static/create_local_printer03.png + :width: 70 % + :align: center + + +.. image:: _static/create_local_printer04.png + :width: 70 % + :align: center + + +.. image:: _static/create_local_printer05.png + :width: 70 % + :align: center + + +.. image:: _static/create_local_printer06.png + :width: 70 % + :align: center + + +.. image:: _static/create_local_printer07.png + :width: 70 % + :align: center + diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_static/create_local_printer01.png Binary file elog2labfolder/_build/html/_static/create_local_printer01.png has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_static/create_local_printer02.png Binary file elog2labfolder/_build/html/_static/create_local_printer02.png has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_static/create_local_printer03.png Binary file elog2labfolder/_build/html/_static/create_local_printer03.png has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_static/create_local_printer04.png Binary file elog2labfolder/_build/html/_static/create_local_printer04.png has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_static/create_local_printer05.png Binary file elog2labfolder/_build/html/_static/create_local_printer05.png has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_static/create_local_printer06.png Binary file elog2labfolder/_build/html/_static/create_local_printer06.png has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_static/create_local_printer07.png Binary file elog2labfolder/_build/html/_static/create_local_printer07.png has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/_static/cups_print_operating.png Binary file elog2labfolder/_build/html/_static/cups_print_operating.png has changed diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/cups_admin_guide.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/elog2labfolder/_build/html/cups_admin_guide.html Tue Mar 27 16:07:14 2018 +0200 @@ -0,0 +1,93 @@ + + + + + + + Set up CUPS as labfolder admin — Labfolder at FHI 1.0 documentation + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+

Set up CUPS as labfolder admin

+

This is a test.

+
+ + +
+
+
+ +
+
+
+ ©2018, Stefan Weiher. + + | + Powered by Sphinx 1.6.6 + & Alabaster 0.7.10 + + | + Page source +
+ + + + + + \ No newline at end of file diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/cups_user_guide.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/elog2labfolder/_build/html/cups_user_guide.html Tue Mar 27 16:07:14 2018 +0200 @@ -0,0 +1,89 @@ + + + + + + + <no title> — Labfolder at FHI 1.0 documentation + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ + + +
+
+
+ +
+
+
+ ©2018, Stefan Weiher. + + | + Powered by Sphinx 1.6.6 + & Alabaster 0.7.10 + + | + Page source +
+ + + + + + \ No newline at end of file diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/import_export.html --- a/elog2labfolder/_build/html/import_export.html Wed Feb 07 16:53:37 2018 +0100 +++ b/elog2labfolder/_build/html/import_export.html Tue Mar 27 16:07:14 2018 +0200 @@ -54,14 +54,14 @@

Export

-

Exporting projects (or just single entries) is possible in three different formats: PDF, XHTML and JSON. The export as PDF can be done from within a project …

+

Exporting projects (or just single entries) is possible in three different formats: PDF, XHTML and JSON. The export as PDF can be done from within a project …

_images/export_of_projects.png

… or from the project overview (Manage > Projects):

_images/export_of_projects2.png -

The XHTML export can be done via the settings:

+

The XHTML export can be done via the settings:

_images/export_xhtml.png

However, to use this type of export it has to be installed first in the Manage > Apps section. By means of the XHTML export all projects that one owns will be exported. A detailled selection of projects or entries to be exported is not possible. As soon as the export process is finished a download link appears in the settings in Data exports. The downloadable ZIP file contains all images and files along with an index.html file that contains information about all entries. You could open and view the index.html file in a browser similar to the view in labfolder.

-

The JSON export is only useable via the API endpoint GET /entries. However, at the moment the response only contains useful information such as dates and tags. The author name is hidden behind the author ID and the entry text content is completely missing.

+

The JSON export is only useable via the API endpoint GET /entries. However, at the moment the response only contains useful information such as dates and tags. The author name is hidden behind the author ID and the entry text content is completely missing.

diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/importing_from_elog.html --- a/elog2labfolder/_build/html/importing_from_elog.html Wed Feb 07 16:53:37 2018 +0100 +++ b/elog2labfolder/_build/html/importing_from_elog.html Tue Mar 27 16:07:14 2018 +0200 @@ -69,19 +69,21 @@ 
$ git clone https://github.molgen.mpg.de/weiher/elog2labfolder.git
-

The script elog2labfolder.py is meant to be executed from remote, that is, not on the machine on which labfolder is running. A prerequisit is the python MySQLDB package because for a few methods the labfolder API cannot be used, instead, direct manipulation of the labfolder MySQL database is needed. The actual labfolder API is applied in the methodes collected in myPythonAPIv1.py and myPythonAPIv2.py. Mostly, API version 2 is used but adding text at the end of an entry can only be accomplished by using the version 1 API call. getListOfAuthors.py gives you a list of all authors in a raw ELOG export file.

+

The script elog2labfolder.py is meant to be executed from remote, that is, not on the machine on which labfolder is running. A prerequisit is the python MySQLDB package because for a few methods the labfolder API cannot be used, instead, direct manipulation of the labfolder MySQL database is needed. The actual labfolder API is applied in the methodes collected in myPythonAPIv1.py and myPythonAPIv2.py. Mostly, API version 2 is used but adding text at the end of an entry can only be accomplished by using the version 1 API call. getListOfAuthors.py gives you a list of all authors that are mentioned in a raw ELOG export file.

-
-

Alternatives to the manipulating the labfolder DB on MySQL level

+
+

Alternatives to manipulating the labfolder DB on MySQL level

As mentioned previously: a few methods in the python API use a direct manipulation of the labfolder DB via MySQL queries. These methods are:

    -
  • createUserAccount(email, author, entryContent, verboseOutput, cursor, db): If an author of an ELOG logbook entry has not yet a labolder account this account is created on the fly by setting a default (encrypted) password. This password is irrelevant because labfolder checks the entered password with the one from the LDAP server. Note: when setting a password in the DB labfolder’s LDAP authentication needs to be disabled (FEATURE_LDAP_AUTHENTICATION=false) and enabled again after the setting process is finished.
    • +
  • createUserAccount(email, author, entryContent, verboseOutput, cursor, db): If an author of an ELOG logbook entry does not yet have a labolder account this account is created on the fly by setting a default (encrypted) password. This password is irrelevant because labfolder checks the entered password with the one from the LDAP server. Note: when setting a password in the DB labfolder’s LDAP authentication needs to be disabled (FEATURE_LDAP_AUTHENTICATION=false) beforehand and enabled again after the setting process is finished.
  • updateAuthor(userID, blockID, cursor, db): Update the author of an entry. With the script elog2labfolder.py an entry is created with the author that is the person whose labfolder credentials are used to get the login token. Via this method the true author can be set to the passed in userID.
    • -
  • updateDateAndTime(date, blockID, cursor, db): Similar to updateAuthor() this method sets the creation and modification date to the creation time and date of the entry to be imported. This is necessary because otherwise creation and modification date are the time and date of the import of the entry.
    • +
  • updateDateAndTime(date, blockID, cursor, db): Similar to updateAuthor() this method sets the creation and modification date to the creation time and date of the entry to be imported. This is necessary because otherwise creation and modification date in labfolder are the time and date when the import took place.

The labfolder support suggested the following alternative involving using the labfolder API:

    -
  • … siehe E-Mail (gesendet) vom 15.12. …
    • +
  • User account: A user account can be created via the API 2 endpoint /auth/signup. The password will be an encrypted dummy password. In order for this to work the LDAP authentication must be turned off when this endpoint is called. After the account creation LDAP authentication should be turned on again. Once the true user of this account logs in labfolder will ignore the dummy password and check the entered password against the password stored in LDAP.
    • +
  • Author: To create a labfolder entry by using the original entry’s author needs a special work-around. First, make sure to prevent labfolder users from accessing labfolder for the time of the import. Then, manually change all user passwords in the DB to the same (encrypted) password. Switch off the LDAP authentication and restart labolder. Now, import entry by entry and get a new login token for each new entry. It is only possible to get login tokens for all users because they all have the same known password. If the author of the entry to be imported does not exist yet in the DB you need to create an account via the API 2 endpoint /auth/signup. Now you reopen the access to the labfolder instance and switch on LDAP again restarting labfolder afterwards. The users can login using their FHI credentials no matter the “universal” password in the DB. If LDAP authentication is not turned on the users could do a password recovery on the login screen and re-set their password to their liking.
    • +
  • Date and time: Since you cannot change creation and modification time stamp of an entry via the API you could instead create custom dates during the import of an entry. The original entry creation timestamp could be “Original entry creation” followed by the creation time and date of the import. All entries can be filtered and searched by the custom dates.
diff -r a21f3604f1db -r 523ca1dfd077 elog2labfolder/_build/html/index.html --- a/elog2labfolder/_build/html/index.html Wed Feb 07 16:53:37 2018 +0100 +++ b/elog2labfolder/_build/html/index.html Tue Mar 27 16:07:14 2018 +0200 @@ -46,6 +46,11 @@

Contents: