Hi Aditi,
Maximo, like any other enterprise-grade secure solution, requires authentication before it can authorize a user to access any of its applications or modules. In simple terms, authentication ensures that the user is who they claim to be, while authorization determines what actions or data that verified user can access.
There is no scenario where authorization can occur without authentication—this is a fundamental security principle. For example, before a maintenance planner can approve a work order in Maximo, the system first verifies their identity using credentials (such as a username and password, or a token). Only after successful authentication does Maximo check the user’s assigned security groups or roles to authorize access to specific applications like Work Order Tracking, Inventory, or Purchasing.
When Single Sign-On (SSO) or LDAP/Active Directory (AD) integration is configured, it might appear that users are logging into Maximo without entering credentials. However, in reality, authentication still takes place—just not directly within Maximo. Instead, the verification happens through an external identity provider (such as Azure AD, IBM Security Verify, or Okta), and Maximo trusts the session token provided by that service.
For example:
-
In an enterprise using LDAP, when a technician logs into their Windows workstation, their credentials are validated by Active Directory. When they later open Maximo, the system recognizes their AD session and seamlessly authenticates them without re-entering credentials.
-
Similarly, with SSO using SAML or OIDC, a manager might access Maximo via a corporate portal. The authentication is handled by the organization’s identity provider, which then issues a secure token that Maximo accepts for login.
In both cases, authentication still occurs—just through federated identity mechanisms—ensuring that Maximo remains compliant with enterprise security standards and audit requirements.