First-Time FlightIQ Setup

When FlightIQ starts without tenant apps configured, it opens a focused Configure Tenant setup page. Use that page to save the PingOne worker app credentials and, when required, the PingOne user login app settings.

Complete this setup before trying to load environments, domains, comparisons, repository-backed workflows, or FlightIQ Director.

Before You Start

Create or identify the required PingOne applications first:

  1. Create the worker application used for backend PingOne and DaVinci API access.
  2. Create the OIDC web application used for FlightIQ user login if your deployment requires authentication.
  3. Capture the environment ID, client IDs, client secrets, auth base URL, redirect URI, and scopes.

Use the PingOne-specific setup pages when you need step-by-step configuration guidance:

Startup Configuration Page

The startup setup page contains the same core settings available later under Settings > Access & Authentication, but it is presented as a focused recovery flow so a new or partially configured deployment can be completed.

The page includes:

  • Tenant Configuration for the worker app and tenant context.
  • User Authentication Settings (Login App) for browser sign-in.
  • Help buttons for setup context.
  • Save and test actions for each configuration area.

If authentication is optional in your deployment, complete the worker app configuration first. If authentication is required, complete both sections before users rely on the app.

Configure the Worker App in FlightIQ

In Tenant Configuration:

  1. Enter the tenant name you want to display.
  2. Enter the PingOne environment ID for the tenant context.
  3. Enter the worker app client ID.
  4. Enter the worker app client secret.
  5. Save the settings.
  6. Click Test Backend API Credentials.

A successful test confirms FlightIQ can mint a backend API token with the saved worker app credentials.

Configure the Login App in FlightIQ

In User Authentication Settings (Login App):

  1. Enter the Auth Base URL.
  2. Enter the login app client ID.
  3. Enter the redirect URI.
  4. Enter the login app client secret.
  5. Enter the required scopes.
  6. Save the settings.
  7. Click Test Authentication Settings.

A successful test confirms FlightIQ can discover and validate the configured OIDC endpoints.

After Setup

After the required settings test successfully:

  1. Close the setup page.
  2. Select the Org Root from the top header.
  3. Select a source environment.
  4. Select a destination environment or repository target when the workflow requires one.
  5. Open a read-only workspace first to confirm data loads.

FlightIQ remembers the selected Org Root and environments in browser storage so the context can be restored after reload.

Troubleshooting

Setup Page Keeps Returning

Check:

  • Tenant configuration was saved.
  • Backend API credentials test successfully.
  • Authentication settings test successfully when login is required.
  • The backend can persist settings.

Backend Credential Test Fails

Check the worker app environment ID, client ID, client secret, grant type, enabled state, and role assignments.

Authentication Test Fails

Check the auth base URL, redirect URI, scopes, login app client ID, client secret, and whether the redirect URI is saved exactly in PingOne.