core-main-app 2.12.1

Main functionalities for the curator core project

This Django reusable app contains the main functionalities for the curator core project.

Pre-requisites

For automated and manual install, the following software are needed:

• python

• pip

• virtual env (conda or venv)

In addition, for manual setup, git is needed.

Installation

Automated installation

$ pip install core_main_app

Manual installation

$ git clone https://github.com/usnistgov/core_main_app.git
$ cd core_main_app
$ python setup.py
$ pip install sdist/*.tar.gz

Configuration

Edit the setting.py file

Add the "core_main_app" under INSTALLED_APPS as such:

INSTALLED_APPS = [
    ...
    "core_main_app",
]

Edit the urls.py file

Add the core_main_app urls to the Django project as such.

url(r'^', include("core_main_app.urls")),

Internationalization (i18n)

Before running the project, don’t forget to compile the translation file at project level. i18n uses the gettext package, so please make sure it is installed prior to using this command.

$ python manage.py compilemessages

Enable SSL connection

Please follow these steps to configure the connection to any system running over HTTPS (including the local instance).

• Create a folder for SSL certificates,

• Copy the certificate in the folder,

• Run c_rehash on the folder (needs to be done every time a new certificate is added to the folder),

• Update the SSL_CERTIFICATES_DIR setting to point to the SSL certificate folder previously created.

$ mkdir certs
$ cp cdcs.crt certs/
$ c_rehash certs/

Enable Redis Server authentication

Please follow these steps to enable authentication on the redis server. Depending on the way Redis is started on the machine, the method may differ.

You can follow instructions at https://redis.io/topics/security#authentication-feature to enable authentication: * Open the file redis.conf (e.g. /usr/local/etc/redis.conf), * Uncomment the authentication setting (# requirepass foobared), * It is recommended to replace the default password (foobared) by a strong and long password, * Restart the Redis Server.

You should then update the CDCS settings using a Redis connection URL with the password chosen in the previous steps.

BROKER_URL = 'redis://:<password>@localhost:6379/0'
CELERY_RESULT_BACKEND = 'redis://:<password>@localhost:6379/0'

Enable SMTP server

Please follow these steps to configure the SMTP server:

• Set these constants in your setting.py file (all these constants are required)

EMAIL_HOST = 'smtp.myserver.com'
EMAIL_PORT = 587
DEFAULT_FROM_EMAIL = 'TestSite Team <[e-mail]>'

• These optional constants can be added in your setting.py according to your SMTP server configuration

EMAIL_USE_TLS = True
EMAIL_HOST_USER = 'testsite_app'
EMAIL_HOST_PASSWORD = 'mys3cr3tp4ssw0rd'

Enable History

Django Simple History allows keeping track of changes made to an object stored in the CDCS database. First, install and configure the package. See the django-simple-history documentation.

Then, set the DJANGO_SIMPLE_HISTORY_MODELS setting with a list of models to track. At the moment, this feature is only available for the Data model.

DJANGO_SIMPLE_HISTORY_MODELS=["Data"]

Register models to track by updating project files. For example in mdcs/mdcs_home/admin.py, add the following lines:

from core_main_app.utils.admin_site.model_admin_class import register_simple_history_models
from django.conf import settings

DJANGO_SIMPLE_HISTORY_MODELS = getattr(settings, "DJANGO_SIMPLE_HISTORY_MODELS", None)
register_simple_history_models(DJANGO_SIMPLE_HISTORY_MODELS)

Documentation

Documentation has been generated using Sphinx. To generate a local version of the docs, please clone the repository and run:

$ cd docs/
$ make html

Or, directly using Sphinx:

$ cd docs/
$ sphinx-build -b html . ../dist/_docs

Development

Development version

A development version of this package is available, containing tests and formatting dependencies. To automatically install the development version, run:

$ pip install .[develop]

The development dependencies are located in requirements.dev.txt and can be installed manually using:

$ pip install -r requirements.dev.txt

Code formatting

To ensure consistent formatting across the codebase, the development team is using black. When contributing to this package, install black as part of the development packages and run black /path/to/core_main_app before submitting the contribution.

Tests

To play the test suite created for this package, download the git repository, install the development dependencies and run:

$ python runtests.py

Sending email

To test the email being sent, console backend will print the email instead of sending the real email. By default, the console backend writes to stdout

To specify this backend, add the following in your settings:

EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend'

JSON Support

CDCS 2.6 adds the ability to work directly with JSON documents. A Template can now either be an XML Schema or a JSON schema. Uploaded data, in XML or JSON format, will be validated by a template in the corresponding format, by the appropriate validator.

This addition has been implemented as an option and needs to be enabled to make the features appear in the system. The following settings have been added with the implementation of JSON support and need to be set properly to enable the feature.

ENABLE_JSON_SCHEMA_SUPPORT = True
BACKWARD_COMPATIBILITY_DATA_XML_CONTENT = False
ALLOW_MULTIPLE_SCHEMAS = True # only required for registries

To enable JSON support in the CDCS, ENABLE_JSON_SCHEMA_SUPPORT should be set to True. For the registry projects, which are limited to a single XML Schema by default, the setting ALLOW_MULTIPLE_SCHEMAS should also be set to True. Before CDCS 2.6, some fields of the database contained direct references to the XML format. In particular, the property to read the content of an XML data was called xml_content. When adding support for new formats, these fields have been renamed to not be tied to a specific format, thus Data.xml_content was renamed Data.content. The change also impacted REST APIs, and data upload would need to set a content field, and responses would return a content field. For users that are not ready to migrate their scripts to the new configuration yet, a setting has been added to continue accepting xml_content instead of content in the REST API. It is recommended to set BACKWARD_COMPATIBILITY_DATA_XML_CONTENT to False when ready to make the move to JSON Support and start using Data.content.

Django Allauth

CDCS 2.12 adds support for [django-allauth](https://docs.allauth.org/en/latest/).

To install CDCS with the required packages for django-allauth, add the following line to the requirements.core.txt file of your project, or pip install in your python environment:

` core-main-app[allauth] core-main-app[allauth]==2.12.* # if the project requires a specific version core-main-app[allauth,mongodb]==2.12.* # if the project requires several optional packages such as mongodb `

To enable django-allauth and some preconfigured authentication options set the following environment variables: ` ENABLE_ALLAUTH=True # Enable allauth package ENABLE_SAML2_SSO_AUTH=True # Enable saml2 auth via allauth if both variables are True ENABLE_ALLAUTH_LOCAL_MFA=True # Enable local MFA via allauth `

By default the django-allauth package allows users signing up on a platform and login using their social account. To preserve the CDCS workflow of first requesting an account and waiting for an administrator to approve it, an option has been implemented. To force users making account requests on the system (even when using 3rd party authentication), set: ` ALLAUTH_ACCOUNT_REQUESTS_FOR_NEW_USERS=True `

For systems with existing user bases, the migration to django-allauth will be done as followed: - existing local accounts will be migrated automatically, - existing local accounts previously created by connecting to an Identity Provider (IdP) using SAML2: 1) Automatically migrate existing accounts by matching their email to the email registered in the IdP by setting: ` SAML_EMAIL_AUTHENTICATION=True SAML_VERIFIED_EMAIL=True # Or set to a list of accepted domains ` 2) Let users manually link their account back to the IdP via SAML2 from their profile page. Users who only authenticated via SAML2 in the past may have to first reset their password, connect to their local account and then link their account to the IdP.