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.

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

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.

It covers how users authenticate using enterprise-managed identity providers (such as Azure AD, Google, or Okta), how access and refresh tokens are managed, and how user data is synchronized with backend systems. This information is relevant for developers, implementers, and security teams configuring the authentication layer in customer deployments.

Component Overview

The authentication flow involves multiple systems working together to validate user identity, issue secure tokens, and enable access to backend services. The table below summarizes the core components involved:


Component	Description
Innovapptive DB	Stores tenant-specific configuration such as Tenant ID, SSO method (e.g., Azure, Google), Client ID, and Client Secret.
Tenant ID	A unique identifier assigned to each customer environment.
SSO Method	Specifies the identity provider (e.g., Cognito, Azure AD, Google, Okta) used for user authentication.
Client ID & Secret	Credentials associated with the Innovapptive application registered in the tenant's SSO provider.
Mobile App	The application being used — such as mWorkOrder, mRounds, or mTag — initiates the authentication request.
Auth Server	Innovapptive’s authentication microservice, deployed in the tenant's cloud, is responsible for token issuance and user validation.
Users Table	Managed by the Auth Server. Stores user records, including internal User ID, SSO identifier, and SSO-issued refresh tokens.
SSO Server	The tenant-managed identity provider is responsible for authenticating users and issuing authorization codes and refresh tokens.
Mongo User Directory	MongoDB Realm directory is used to authorize users for offline data sync and database access.