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
  • Prepare
  • Verify
  • Restart
  1. The Service
  2. Installation

Using a container

PreviousLinuxNextOperations

Prepare

Begin by obtaining authentication credentials from your Fortified ID representative. Use the credentials to log in to the FortifiedID Docker Registry by any available method, .

Example for Unix/Linux:

Transfer the token from customer_access_credentials.json to password.txt:

  1. Open the customer_access_credentials.json file that you have received.

  2. Locate and copy the access_token value.

  3. Open or create the password.txt file.

  4. Paste the access_token value into password.txt.

  5. Replace <username> with your username that you have received in the following command and execute it.

cat ./password.txt | docker login fortifiedid.jfrog.io --username <username> --password-stdin

Depending on your system configuration, you may need to run the logon command with different user rights, such as the root user and the current user account.

Verify

To verify the Docker setup, run the default Integrity server:

Replace <container_display_name> with the container name and replace <product_name>:<version> with the image product name and version.

docker run -p 8080:8080 --detach --name integrity fortifiedid.jfrog.io/docker/fortifiedid/integrity:<version> -c Node config/config.json

Parameter explanation:

-c

Direct system output to stdout.

Node

Start the Node module.

config/config.json

Use the given configuration file. Path is relative to SERVER_HOME inside the container.

Check the log to ensure that the server was successfully bootstrapped:

docker logs -f integrity

Restart

Stop, start and restart are handled by Docker commands.

Finally, check that the server is up and running by pointing your browser at

see here for instructions on Unix/Linux and Windows
http://localhost:8080