Build Status:

See the LICENSE-2.0.txt file

See the NOTICE.txt file

See the UPGRADING.md file

Please see the wiki for information on how to get started with developing themes for OpenConext EngineBlock In short, themes require front-end resource compilation which can be done by running the following commands:

First set the desired theme name in the parameters.yml. This will load the correct Twig templates as they are a part of the Symfony config.

parameters:
    # Other parameters have been left out for brevity
    theme.name: skeune

Next build the front-end assets for the selected theme.

    (cd theme && yarn install --frozen-lockfile && yarn build)

Finally, when not in an environment with the debug flag enabled, you need to clear the cache. This will ensure the translations and templates are swapped out for the ones found in the new theme.

$ php72 ./app/console cache:clear --env=prod

To setup the required tooling on the VM, the following steps might be useful:

cd /opt/openconext/OpenConext-engineblock/theme
sudo curl --silent --location https://rpm.nodesource.com/setup_11.x | sudo bash -
sudo yum install nodejs
sudo npm install --global yarn
(yarn install --frozen-lockfile && yarn build)

In addition to the npm/yarn scripts that are available to run (unit/e2e) tests and quality assurance, you can also use the Twig linting tool built into Symfony. To run this linter:

If you are able to run Ant build targets use:
$ ant php-twig-lint

But you can also run the linter directly from the Symfony console. From the webroot:
$ php72 ./app/console lint:twig theme/

• Linux
• Apache
• PHP 7.2:
  • libxml
  • apcu
  • apcu-bc (a requirement while we are using an older Doctrine version)
• MySQL > 5.x with settings:
  • default-storage-engine=InnoDB
  • default-collation=utf8_unicode_ci
• Manage
• Composer (for php dendency management)
• Yarn (optional for theme deployment)

Note: While care was given to make EngineBlock as compliant as possible with mainstream Linux distributions, it is only regularly tested with RedHat Enterprise Linux and CentOS.

Note: you are highly encouraged to use OpenConext-Deploy to deploy OpenConext installations.

If you are reading this then you've probably already installed a copy of EngineBlock somewhere on the destination server, if not, then that would be step 1 for the installation.

If you do not use OpenConext-Deploy and have an installed copy and your server meets all the requirements above, then please follow the steps below to start your installation.

EXAMPLE

mysql -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 21
Server version: 5.0.77 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> create database engineblock default charset utf8 default collate utf8_unicode_ci;

EngineBlock requires you to have the folders below writable by your webserver user.

 app/cache

Run the command below in the root of your project to install the required dependencies.

composer install --no-interaction --optimize-autoloader --prefer-dist --no-dev

Note: The command above assumes that the application must be build for production, and omits development dependencies.

Then edit the parameters.yml with your favorite editor and review the settings to make sure it matches your configuration.

To install possible database updates, call doctrine migrations by using the following console command:

app/console doctrine:migrations:migrate --env=prod

Note: EngineBlock requires database settings, without it doctrine migrate will not function. Furthermore, this assumes that the application must use the production settings (--env=prod), this could be replaced with dev should you run a development version.

Configure a single virtual host, this should point to the web directory:

DocumentRoot    /opt/www/engineblock/web

It should also serve both the engine.yourdomain.example and engine-api.yourdomain.example domains.

Make sure the ENGINEBLOCK_ENV is set, and that the SYMFONY_ENV is set, this can be mapped from ENGINEBLOCK_ENV as:

EXAMPLE

SetEnv ENGINEBLOCK_ENV !!ENV!!
SetEnv SYMFONY_ENV !!SF_ENV!!

Make sure you have the following rewrite rules (replace app.php with app_dev.php for development):

RewriteEngine On
# We support only GET/POST/HEAD
RewriteCond %{REQUEST_METHOD} !^(POST|GET|HEAD)$
RewriteRule .* - [R=405,L]
# If the requested url does not map to a file or directory, then forward it to index.php/URL.
# Note that the requested URL MUST be appended because Corto uses the PATH_INFO server variable
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_FILENAME} !-f
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ /app.php/$1 [L] # Send the query string to index.php

# Requests to the domain (no query string)
RewriteRule ^$ app.php/ [L]

Note that EngineBlock SHOULD run on HTTPS, you can redirect users from HTTP to HTTPS with the following Apache rewrite rules on a *:80 VirtualHost:

RewriteEngine   on
RewriteCond     %{SERVER_PORT} ^80$
RewriteRule     ^(.*)$ https://%{SERVER_NAME}$1 [L,R=301]

Copy the app_dev.php.dist file to the web directory.

Openconext-engineblock $ cp app_dev.php.dist web/app_dev.php

Use these URLs to test your EngineBlock instance:

• http://engine.example.com, this should redirect you to the following URL
• https://engine.example.com, show a page detailing information about the capabilities
• https://engine.example.com/authentication/idp/metadata, this should present you with the IdP metadata of EngineBlock
• https://engine.example.com/authentication/sp/metadata, this should present you with the SP metadata of EngineBlock
• https://engine.example.com/authentication/proxy/idps-metadata, this should present you with the proxy IdP metadata
• https://engine-api.example.com, this should return an empty 200 OK response

Please see security considerations to harden your Engineblock after installation.

It is recommended practice that you deploy engineblock in a directory that includes the version number and use a symlink to link to the 'current' version of EngineBlock.

EXAMPLE

.
..
engineblock -> engineblock-v1.6.0
engineblock-v1.5.0
engineblock-v1.6.0

If you are using this pattern, an update can be done with the following:

1. Download and deploy a new version in a new directory.

2. Check out the release notes in UPGRADING.md

3. Run the database migrations script.

    app/console doctrine:migrations:migrate --env=prod
   

4. Change the symlink.

The list of browsers that should be supported:

IE / Edge	Firefox	Chrome	Safari	iOS Safari	Samsung	Opera
IE10, IE11, Edge	last 2 versions	last 2 versions	last 2 versions	last 2 versions	last 2 versions	last 2 versions

The list of browsers being tested:

IE / Edge	Firefox	Chrome	Chrome Android	Safari	iOS Safari
IE11, Edge last version	last version	last version	last version	last version	last version

Most additional documentation can be found in the wiki. If you want to help with development for instance, you can take a look at the Development Guidelines

Also, the following documentation can be found in the docs directory:

1. License
2. Release Procedure
3. EngineBlock Input and Output Command Chains
4. Release notes for releases < 5.0.0