Description

Alison Wizard is a web assistant that facilitates the deployment of Alison Desktop on the end users' stations, determines if all the necessary components are correctly installed, and to suggest suggests installation or update if necessary.

It detects the minimum conditions under which it should be performed and suggests the necessary corrective steps.

Among the tasks performed we can mention:

• Execute the download of its components

• Facilitate the correct installation of the components

• Validate its correct installation by signing a test transaction (if the user has a certificate)

Alison Desktop is used to generate the key pair, certificate installation, and digital signature operations for the following browser: Internet Explorer, Microsoft Edge, Firefox, Chrome, Opera, Safari.

Alison Desktop can recognize certificates installed in various secure repositories like Microsoft CSP, Firefox NSS, PKCS # 11 devices, Smartcards, eTokens, and multiple platforms (Windows, Mac OS, Linux).

Advantages and benefits

• Alison Wizard simplifies the download of the required components to operate and enable them on the browser properly.

• Users will have the same user experience, no matter which browser is using.

• End-user can test the correct installation of the certificate, and even check if the certificate is valid or revoked.

Installation

Follow this instruction to install a docker instance of the product.

Configuration

You can customize your installation by changing some variables.

Step 1: Detect Alison-Desktop

Image Added

This is Alison Wizard's first step. The target is to verify if Alison Desktop is installed on the end-user machine.

If not detected, downloads the appropriate installer for the operating system in use. End-user has to install it and run Alison-Desktop to allow Alison Wizard to continue.

A new icon will appear on the tray to access additional features.

Image Removed

Step 2: Integrate

Image Added

Verify the correct communication between the browser and Alison Desktop. If necessary, the process will prompt the end-user to install additional components.

If communication between the browser in use and Alison Desktop is enabled, Alison Wizard will jump to the third step.

Integration is shared between different browsers, like Internet Explorer and Chrome, but it's recommended to run the wizard on each browser that the end-user has. Alison Wizard is a diagnostic tool that facilitates end-user error detection and suggests a solution.

Step 3: Test user certificate

Image Added

Once

all the Alison components are installed on the end-user machine, Wizard allows the end-user to validate the correct operation of Alison Desktop through a test signature operation.

It requires at least one certificate installed on some of the enabled Keystore repositories.

If no certificate is detected, the end-user will see a notice

Each tenant has its own configuration, and every Alison Wizard docker instance can manage one or several tenants. 

The configuration file allows defining all the behavior of the Wizard for each tenant. It is easy to make changes in the operation of the application. It requires to reload the Alison Wizard container image to apply any change made on these files.

The following files define tenant configuration and must be customized or replaces.

This is the main configuration file. It defines keystores, providers, filters, and plugins.

It also defines minimal and suggested Alison-Desktop version.

background_world_map.png
background_world_map_ie.png

This file includes a license for the enabled domains.
This file must be replaced by a definitive license file, that can extend new domains and expiration date.

Create a new Tenant

The best way to create a new tenant is to copy ACME tenant configuration distributed on the last version of Docker Image, modify its name and apply changes on each related file.

Principal variables that you can modify to custom your tenant:

The following example will set up a new tenant for Alison Wizard. You can download the files in the following link looney-demo.tgz.

Custom configuration directories

├── debbie
│   ├── config
│   │   ├── certstore
│   │   │   ├── CertiSur.root.ClassB.G1.pilot.509.cer
│   │   │   └── CertiSur.shared.ClassB.G1.pilot.509.cer
│   │   ├── debbie.json
│   │   ├── debbielog.properties
│   │   └── policies
│   │       └── looney.policy.json
│   ├── logs
│   └── repository
├── docker-compose.yml
└── wizard
    ├── alison-sdk
    ├── logs
    └── tenants
        ├── looney
        │   ├── config
        │   │   ├── alison-config.json
        │   │   ├── authtoken-desktop.json
        │   │   └── license-desktop.json
        │   ├── images
        │   │   ├── background_world_map.png
        │   │   └── clientLogo.jpg
        │   └── stylesheets
        │       └── custom.css
        └── versiones.yml

Docker compose file 

version: '3'

services:

  wizard:
    image: certisursa/wizard:latest
    environment:
      ENABLED_TENANTS: looney
      WIZARD_SECRET_KEY_BASE: 95820b3cea66376d006bf3ca3adf48287c1fc671e81c5956f8cd56aaffc4ac707673872d3d8561e14d851dea4c685a9874329a86f5c4b741e6e187cb70895820
      BASE_INSTALLERS_PATH: https://s3.amazonaws.com/downloads.certisur.net/installers   
      DEBBIE_BASE_URL: http://192.168.1.61:8081
      ENABLED_BROWSERS: chrome,firefox,edge,safari
      ENABLED_PLATFORMS: windows,mac,linux
    volumes:
      - "./wizard/tenants:/opt/jboss/config/tenants"
      - "./wizard/logs:/opt/jboss/logs"
    ports:
      - 8082:8080

  debbie:
    image: certisursa/debbie:v2.2.9a
    environment:
      checkMACAddress: disabled
    volumes:
      - "./debbie/config:/app/config"
      - "./debbie/repository:/app/repository"
      - "./debbie/logs:/app/log"
    ports:
      - 8081:8080

Working with the demo

1 - Deploy and run

To deploy this configuration you must execute the following in a shell window.

# docker-compose --verbose -f docker-compose.yml up -d

Image Removed

Image Removed

3- Stop the containers

To stop the demo you must execute the following in a shell window.