LogoLogo
HomeIntegrityControlSolutionsManagement Center
2.3.0 - WEB
2.3.0 - WEB
  • Introduction
  • The Service
    • About | The Service
      • Release notes
      • Breaking changes
    • Architecture
      • Modules
      • Folder structure
      • Startup
    • Getting started
    • Installation
      • Windows
      • Linux
      • Using a container
    • Operations
      • Configuration
      • Metrics
      • Health check
      • Logging
        • System logging
        • Event logging
      • SBOM & license material
  • Modules
    • External modules
    • Internal modules
      • SAMLModule
      • OIDC
        • OpenID Configuration endpoint
        • JWKS endpoint
        • Authorization endpoint
        • Token endpoint
          • Authorization code
          • Refresh token
        • User info endpoint
        • Introspection endpoint
        • End session endpoint
  • Configuration reference
    • Introduction
    • Terms and abbreviations
    • Property expansion
    • File inclusion
    • Secrets management
    • Examples
  • Authenticators
    • Introduction
    • Common configuration
    • Web Authenticator API
    • Flow control
      • Selector
      • AuthController
      • Chain
      • Impersonate
      • Impersonate With Search
    • Credential validators
      • SITHS eID
        • With QR or "app-switch"
      • BankID
        • On another device
        • On mobile device
      • Freja e-ID
        • With user input
        • With QR or "app-switch"
      • Mobile ID
        • With QR or "app-switch"
      • Header based
        • Certificate
      • Pointsharp Net iD Access server
        • On another device
        • On same device
      • Integrated windows login, IWA
      • User name & password
      • User lookup
      • OTP validator
      • Passkey validator
      • Exposed metrics
      • Test
        • Static SAML
        • No operation
    • Protocol managers
      • SAML
        • SAML IDP
        • SAML SP
        • IDP Discovery Service
      • OIDC
        • Authorization Code Flow
        • Implicit Flow
        • OIDC Relying Party
    • UI
      • Overriding UI elements
      • Accessibility/A11y
Powered by GitBook
On this page
  • Overview
  • Prerequisite
  • Installation
  • Upgrade
  • Restart
  1. The Service
  2. Installation

Linux

Overview

You like to install or upgrade one of the products provided from Fortified ID on a Linux server. Installation is done by running a generic Bash script for all applications that uses a properties to define product and account.

Prerequisite

There are some prerequisite before continuing with install/upgrade.

  • Linux OS 64-bit.

  • Unzip installed in the Linux OS.

  • cURL installed in the Linux OS

  • Contact Fortified ID support to get the download credentials file, customer_access_credentials.json.

  • Latest version of the Bash script and property file.

  • Hardware requirement is depend on usage of the application

    • Minimum of 10 GB of drive space

    • Minimum 4 GB of RAM

    • Integrity is not CPU intensive; two virtual CPUs should work for most scenarios

Installation

In a terminal run the following commands to install the Web service.

    1. Import public key

      sudo apt install gnupg ca-certificates curl
      curl -s https://repos.azul.com/azul-repo.key | sudo gpg --dearmor -o /usr/share/keyrings/azul.gpg
      echo "deb [signed-by=/usr/share/keyrings/azul.gpg] https://repos.azul.com/zulu/deb stable main" | sudo tee /etc/apt/sources.list.d/zulu.list
    2. Run the following command to update available packages.

      sudo apt update
    3. Run the following command to

      sudo apt install zulu17-jre
    4. Verify the Java installation, run the java -version command. You should see the version of the installed Java.

      java -version
  1. Create or use an existing folder to download or copy the installation files to.

  2. Change to the folder that will be used for the installation files.

  3. Run the following command to download the installation files

    curl -X GET https://share.fortifiedid.se/index.php/s/CXGr7dW2rPJWEDi/download -o fortifiedid_online_installation.zip
  4. Run the following command to unzip the files

    unzip fortifiedid_online_installation.zip
  5. Open fortifiedid_online_installation.properties with a text editor

    1. Uncomment the lines in the Web section except for the first row. There is no support to install more than one product at a time.

    2. Change the APP_LINK with the download link for the Web installation that you have got from Fortified ID.

    3. Change INSTALLATION_PATH to the folder where you would like to install the service.

    4. Example of the changes except for the APP_LINK path

      # Install WEB
      APP_LINK=<The provided path for the product>
      INSTALLATION_PATH=/opt/fortifiedid/web
      DOWNLOADED_PRODUCT_FILENAME=web
    5. Save the file when done.

  6. Copy the customer_access_credentials.json that you should have received from Fortified ID file to the folder with the installation files

  7. Run the following command to install the Web service. Add sudo in front of the command if root privilege is need to install the service.

    ./fortifiedid_online_installation.sh
    • Type Y to continue

  8. Change to the <INSTALLATION_PATH>/customer folder

  9. Run the following command to start the Web service. Add sudo in front of the command if root privilege is need to run the service.

    ./startup.sh -c Node ../customer/config/config.json
  10. Installation is complete

  11. Now you are ready to start working with your Fortified ID product. Tip: Check out our use cases to get a head start!

Upgrade

Upgrade of an existing installation is done the same way as when you do a clean installation. Same Bash script and property file. See previous section. When uppgradering, two things to notice:

  • In the fortifiedid.properties file update the APP_LINK setting with the new link .

  • Folders, /application and /JRE, will be replaced during upgrade. Do not store any custom data there. The folder called /customer will not be replaced since it contains your customer data.

Restart

Stop the service by running ./stop.sh

Start the service again by running ./startup.sh -c Node ../customer/config/config.json

PreviousWindowsNextUsing a container

Install Azul Zulu Java 17 using the guides that you can find using this link In the steps below we will install Java on Ubuntu.

https://docs.azul.com/core/#