Entity Search Web App

If you are beginning your journey with Senzing, please start with Senzing Quick Start guides.

You are in the Senzing Garage where projects are "tinkered" on. Although this GitHub repository may help you understand an approach to using Senzing, it's not considered to be "production ready" and is not considered to be part of the Senzing product. Heck, it may not even be appropriate for your application of Senzing!

Overview

This is an implementation of an entity search app which uses the senzing rest poc server microservice to access functions of the Senzing API through a web interface.

Related artifacts

DockerHub
Helm Chart

Legend

🤔 - A "thinker" icon means that a little extra thinking may be required. Perhaps you'll need to make some choices. Perhaps it's an optional step.
✏️ - A "pencil" icon means that the instructions may need modification before performing.
⚠️ - A "warning" icon means that something tricky is happening, so pay attention.

Preparation

Prerequisite software

The following software programs need to be installed:

docker
docker-compose

Pull latest docker images

Pull the latest release of this app from Docker Hub. Example:
```
sudo docker pull senzing/entity-search-web-app
```
Pull the latest of the poc server from DockerHub. Example:
```
sudo docker pull senzing/senzing-poc-server
```

Clone repository

Set these environment variable values:

export GIT_ACCOUNT=senzing
export GIT_REPOSITORY=entity-search-web-app
export GIT_ACCOUNT_DIR=~/${GIT_ACCOUNT}.git
export GIT_REPOSITORY_DIR="${GIT_ACCOUNT_DIR}/${GIT_REPOSITORY}"

Follow steps in clone-repository to install the Git repository.

Configuration

Configuration values specified by environment variable or command line parameter.

SENZING_DATA_VERSION_DIR
SENZING_ETC_DIR
SENZING_G2_DIR
SENZING_NETWORK
SENZING_RUNAS_USER
SENZING_VAR_DIR

Using docker-compose

Run in a docker-compose formation. Example:

cd ${GIT_REPOSITORY_DIR}
sudo \
  docker-compose up senzing-webapp

Verify that containers are running and accessible:
1. Open a web browser on http://localhost:8081 (or substitute hostname or IP for localhost).
2. Alternatively, curl can be used. Example:
```
curl http://machine-host-name:8081
```

Using docker

Docker network

The following docker containers communicate over a docker network.

🤔 Find or create a docker network. Perform one of the following procedures.
1. Find a docker network.
  1. List docker networks. Example:
```
sudo docker network ls
```
  2. ✏️ Specify docker network. Choose value from NAME column of docker network ls. Example:
```
export SENZING_NETWORK=*nameofthe_network*
```
2. Create docker network.
  1. ✏️ Specify network name. Example:
```
export SENZING_NETWORK=sz-api-network
```
  2. Create docker network. Example:
```
sudo docker network create -d bridge ${SENZING_NETWORK}
```

Construct parameter for docker run. Example:

export SENZING_NETWORK_PARAMETER="--net ${SENZING_NETWORK}"

Run

Attach senzing-poc-server. Example:

sudo docker run \
  --interactive \
  --name=senzing-poc-server \
  --publish 8080:8080 \
  --rm \
  --tty \
  --volume ${SENZING_DATA_VERSION_DIR}:/opt/senzing/data \
  --volume ${SENZING_ETC_DIR}:/etc/opt/senzing \
  --volume ${SENZING_G2_DIR}:/opt/senzing/g2 \
  --volume ${SENZING_VAR_DIR}:/var/opt/senzing \
  ${SENZING_NETWORK_PARAMETER} \
  senzing/senzing-poc-server \
    -concurrency 10 \
    -httpPort 8080 \
    -bindAddr all \
    -iniFile /etc/opt/senzing/G2Module.ini

Run entity search web app. Example:

sudo docker run \
  --env SENZING_API_SERVER_URL=http://senzing-poc-server:8080 \
  --env SENZING_WEB_SERVER_PORT=8081 \
  --interactive \
  --name=senzing-webapp \
  --publish 8081:8081 \
  --rm \
  --tty \
  ${SENZING_NETWORK_PARAMETER} \
  senzing/entity-search-web-app

To verify that containers are running and accessible:
1. Open a web browser on http://localhost:8081 (or substitute hostname or IP for localhost).
2. Alternatively, curl can be used. Example:
```
curl http://machine-host-name:8081
```

Using SSL

The main docker image for the senzing webapp supports running it's webserver over HTTPS. In order to deploy the webapp in a secure way, you must be using the image in a swarm configuration, rather than a standalone service. For more information on swarms and why this is a requirement see Docker Swarm Secrets

Prerequisites

docker client and daemon with API version > 1.25 you can check what api version your docker client is running by typing docker version
Valid SSL certificates(server.key and server.cert) for the webserver. (if you don't have them, you can use a self-signed certificate in the interim)

Self-Signed Certificates

A self-signed certificate is sufficent to establish a secure, HTTPS connection for development purposes. It should not be used in a production environment, but if you're just trying to test out encryption to see how it works it's a viable short-term solution. You will need OpenSSL installed on your system to generate these. Just do a google search or check out this article or this one and come back to this section once you have the server.cert and server.key files

Setting up SSL using Docker Stack

For convenience we have included a docker compose file specifically for running in SSL configuration. We suggest starting with this example if you're not familiar how stacks work(you will want a different yml file for stack deployment for a number of reasons). If you open that example up you will see two lines at the bottom of the file:

  SZ_WEBAPP_SSL_CERT:
    file: '../CERTS/server.cert'
  SZ_WEBAPP_SSL_KEY:
    file: '../CERTS/server.key'

Those lines tell docker to pass two secrets to the services defined in the docker compose file. These two lines should point to the location of the server.key and server.cert file you wish to use. The configuration of the senzing-poc-server service may differ from how you have set up your configuration to run. You should copy over the configuration options defined in your already working docker-compose.yml file to the docker-stack.yml file. The other important lines(under the senzing-webapp service definition) are:

secrets:
      - source: SZ_WEBAPP_SSL_CERT
        target: server.cert
        uid: '1001'
        gid: '1001'
      - source: SZ_WEBAPP_SSL_KEY
        target: server.key
        uid: '1001'
        gid: '1001'

They tell the webapp service to use the content of the secrets defined at the bottom of the file. It's like passing the files in.. but also not. docker secrets are weird.

Next you will deploy the services defined in the yml file to your swarm manager by typing sudo SENZING_DATA_VERSION_DIR=${SENZING_DATA_VERSION_DIR} SENZING_ETC_DIR=${SENZING_ETC_DIR} SENZING_G2_DIR=${SENZING_G2_DIR} SENZING_VAR_DIR=${SENZING_VAR_DIR} docker stack deploy -c docker-stack.yml senzing-webapp check that the services started up successfully by typing docker stack ps senzing-webapp. the result should look like the following

ID                  NAME                                  IMAGE                               NODE                DESIRED STATE       CURRENT STATE               ERROR               PORTS
7mxc4jru51pl        senzing-webapp_senzing-poc-server.1   senzing/senzing-poc-server:latest   americium           Running             Running about an hour ago
rnguy9d2incb        senzing-webapp_senzing-webapp.1       senzing/entity-search-web-app:ssl   americium           Running             Running about an hour ago

next you can initiate a curl request to your webserver with curl -kvv https://localhost:8081. The output should looks something like the following:

* Rebuilt URL to: https://localhost:8081/
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 8081 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Unknown (8):
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Client hello (1):
* TLSv1.3 (OUT), TLS Unknown, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: C=US; ST=OR; L=SenzingTown; O=Senzing; CN=localhost
*  start date: Nov 13 00:49:12 2019 GMT
*  expire date: Nov 12 00:49:12 2020 GMT
*  issuer: C=US; ST=OR; L=SenzingTown; O=Senzing; CN=localhost
*  SSL certificate verify result: self signed certificate (18), continuing anyway.
* TLSv1.3 (OUT), TLS Unknown, Unknown (23):
> GET / HTTP/1.1
> Host: localhost:8081
> User-Agent: curl/7.58.0
> Accept: */*

I'm using a self-signed cert in this example, but the important part is that you see the TLSvx.x handshake(s) and the Server certificate: response block. At this point you open up a normal browser(chrome, ff, edge etc) to your server instance, something like https://localhost:8081. You should see information next to the address in the address bar with the SSL information provided by the certificate. If you self-signed you will be greeted with a warning message asking whether you want to proceed or not, this is normal.

You can shut down the swarm node with docker stack rm senzing-webapp

Admin Area

There is an admin area that can be used to create new datasources, and import data in to those datasources. In order to access this functionality your poc server version must be >= 1.7.11 and it must be started with the -enableAdmin flag set to true.

The admin area can then be accessed by browsing to /admin on the same domain/hostname that you are running the webapp. You will be prompted to input an Api Token, this is the default security mechanism used to keep the riff-raff from doing unwanted things to your data. The token is randomly generated on server startup and output to stout in the same terminal used to start the container. Copy and past this token in to the login box when prompted.

Admin Area Configuration

There are two security modes supported.

JWT/Token based : randomly generated secret/phrase/seed. This is the default mode because it's self-contained and does not require any additional configuration on the part of the admin or user.
None: this is not a recommended mode. It exists purely for development or debugging purposes.

variables:

SENZING_WEB_SERVER_ADMIN_AUTH_MODE defines what security mode to use for the admin area. possible values are JWT,NONE.

Security Safeguards

CORS (Cross Origin Request)

By default the webapp instance will not enable CORS requests to it's api endpoints. It can be specified to allow specific domains to talk to it by setting the SENZING_WEB_SERVER_CORS_ALLOWED_ORIGIN env variable to the value of the domain that the interface you wish to allow communication to resides on.

CSP (Content Security Policy)

By default a CSP is deployed to the routes that serve content on the webapp's host. It allows assets from itself to be loaded (and some cdn assets) and nothing else. For more information on CSP and how it offers some protection against XSS issues see Content-Security-Policy.

Air Gapped Environments

Obviously if your deployment environment is highly restricted you're probably going to run in to issues downloading the latest images from that context. Please refer to "Install docker image in an air-gapped environment" for how to procedure regarding this use-case.

The short version is find a machine with network access, then:

Pull the docker images you need to that machine.

Package them as a tar file. Example:

sudo docker save senzing/entity-search-web-app --output senzing-entity-search-web-app-latest.tar

Copy that to the deployment machine.

Load via

sudo docker load --input senzing-entity-search-web-app-latest.tar

Building from Source

Build Senzing POC server. tag it as senzing/senzing-poc-server. Following the instructions at "Senzing POC server". Example:
```
cd ../senzing-poc-server
sudo docker build --tag senzing/senzing-poc-server .
```

Build the web app. Example:

sudo docker build --tag senzing/entity-search-web-app .

Run the app. Example:
```
sudo docker-compose up senzing-webapp
```

The default api server port that the compose formation is set to communicate is 8080. If you changed it to something else in step 1 you will have to change the environment variables in the docker-compose.yaml.

Development

To modify or make changes to the app the developer will have to clone or fork the Repository and build from source.

git clone git@github.com:senzing-garage/entity-search-web-app.git
cd entity-search-web-app
npm install
npm start

You may also need to install NodeJS, and AngularCLI if you haven't already done so.

Development server

Run
```
ng serve
```
for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Production Server

Generate a compiled version of the app in the _dist/_ directory. Example:
```
ng build --prod
```
Compiled assets can be served by ExpressJS by running:
```
node webserver
```

Code scaffolding

To generate a new component, Run
```
ng generate component component-name
```

Alternatively, you can use

ng generate directive|pipe|service|class|guard|interface|enum|module

Testing

Running unit tests

There are several ways to run unit tests.

For developers, to execute the unit tests via Karma using the default karma config file, run
```
npm run test
```
These tests can also be run in a headless mode by running
```
npm run test:headless
```
For running unit tests from inside a docker container make sure you have the latest docker container, the script or docker-compose.yaml should pass the appropriate test script command to the container by
```
sudo docker-compose up --abort-on-container-exit senzing-webapp-test
```

Running end-to-end tests

For running e2e tests from inside a docker container make sure you have the latest docker container, the script or docker-compose.yml should pass the appropriate e2e script command to the container. Example:
```
sudo docker-compose up --abort-on-container-exit senzing-webapp-e2e
```

Alternately you can pass the commands directly to the container by adding an e2e:docker to the end of your docker run command. Example:

sudo docker run \
  --env SENZING_API_SERVER_URL=http://senzing-poc-server:8080 \
  --env SENZING_WEB_SERVER_PORT=8081 \
  --interactive \
  --name=senzing-webapp-e2e \
  --network=sz-api-network \
  --publish 8081:8081 \
  --tty \
  senzing/entity-search-web-app e2e:docker

Further help

To get more help on the Angular CLI use
```
ng help
```
or go check out the Angular CLI README.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

README.md

README.md

Entity Search Web App

Overview

Related artifacts

Contents

Legend

Preparation

Prerequisite software

Pull latest docker images

Clone repository

Configuration

Using docker-compose

Using docker

Docker network

Run

Using SSL

Prerequisites

Self-Signed Certificates

Setting up SSL using Docker Stack

Admin Area

Admin Area Configuration

Security Safeguards

CORS (Cross Origin Request)

CSP (Content Security Policy)

Air Gapped Environments

Building from Source

Development

Development server

Production Server

Code scaffolding

Testing

Running unit tests

Running end-to-end tests

Further help

Files

README.md

Latest commit

History

README.md

File metadata and controls

Entity Search Web App

Overview

Related artifacts

Contents

Legend

Preparation

Prerequisite software

Pull latest docker images

Clone repository

Configuration

Using docker-compose

Using docker

Docker network

Run

Using SSL

Prerequisites

Self-Signed Certificates

Setting up SSL using Docker Stack

Admin Area

Admin Area Configuration

Security Safeguards

CORS (Cross Origin Request)

CSP (Content Security Policy)

Air Gapped Environments

Building from Source

Development

Development server

Production Server

Code scaffolding

Testing

Running unit tests

Running end-to-end tests

Further help