Home
Authentication Identity Configuration
This chapter explains how Innovapptive’s mobile applications (such as mWorkOrder, mRounds, and mTag) handle user authentication in a multi-tenant deployment environment. The authentication framework is based on federated Single Sign-On (SSO) and secure token-based session management.
Token-Based App API Flow
After the user is authenticated via SSO, the mobile app uses access and refresh tokens issued by the Auth Server to interact securely with backend services. This section explains how these tokens are generated, validated, and refreshed across service calls.

Title and Copyright
Copyright and Terms of Use page for iMaintenance Configuration.
Preface
Understand audience, know related documents and products and conventions followed in this document.
Introduction
The iMaintenance Configuration Guide is your blueprint for shaping how iMaintenance works in your organization.
Log in to Application
Navigate to the iMaintenance Configuration
Customer Tenant Onboarding with Azure IDP
This chapter provides step-by-step instructions to configure a customer’s Azure Active Directory (Azure AD) for federated Single Sign-On (SSO) with Innovapptive mobile applications. It applies to IT administrators and implementation engineers performing customer onboarding.
Authentication Identity Configuration
This chapter explains how Innovapptive’s mobile applications (such as mWorkOrder, mRounds, and mTag) handle user authentication in a multi-tenant deployment environment. The authentication framework is based on federated Single Sign-On (SSO) and secure token-based session management.
- Federated SSO Login Flow
  Innovapptive’s mobile apps authenticate users using federated SSO, integrating with tenant-managed identity providers like Azure AD, Google, or Okta.
- Token-Based App API Flow
  After the user is authenticated via SSO, the mobile app uses access and refresh tokens issued by the Auth Server to interact securely with backend services. This section explains how these tokens are generated, validated, and refreshed across service calls.
- Use the Token After Login
- Refresh Token Handling
- Alternatives for Users Table Synchronization
  If the Users Table cannot always be reliably synchronized with the tenant’s SSO server, alternative mechanisms may be considered to maintain alignment between user records and identity provider data.
Manage Users & Roles
Maintain Master Data
Configure iMaintenance Core Settings
The Core Settings in iMaintenance define how the product behaves across your entire organization. These settings control fundamental aspects of daily use, such as session timeouts, chat availability, measuring points, auto-timers, AI enablement, issue creation, root cause analysis, attachments, and more.
Integrate External Systems
Manage Maintenance Operations
Review Observations
The Observations module allows supervisors to view and manage issues reported through the iMaintenance mobile app. These issues are typically tied to specific assets and locations within a plant.
Design and Manage Forms
Forms are essential for capturing structured field data in the iMaintenance mobile application. This chapter covers everything from manually creating and publishing forms to leveraging AI for auto-generation to managing archived forms.
Set Up Configurations with RACE
Configure Risk Evaluation with the Risk Matrix
Customize Platform Settings
Set Up Notifications
Build Dashboards and Reports

Token-Based App API Flow

After the user is authenticated via SSO, the mobile app uses access and refresh tokens issued by the Auth Server to interact securely with backend services. This section explains how these tokens are generated, validated, and refreshed across service calls.

This flow assumes that the mobile app interacts with one or more backend services behind a common authentication layer.

What Happens at Login

Once the user logs in, the Auth Server generates both an access token and a refresh token, which are stored in the Users Table and also sent to the mobile app.
Both tokens are formatted as JWTs (JSON Web Tokens).
The access token is short-lived (default: 15 minutes, configurable).
The refresh token has a longer lifespan (default: 30 days, configurable).
Tokens are signed using asymmetric encryption:
- The Auth Server holds the Private Key used to sign tokens.
- All other backend services use the Public Key to verify access tokens.