MAS 9: inbound integration authentication — API key vs mutual TLS
In Maximo Application Suite 9, inbound REST and Integration Framework calls authenticate with a per-request API key that runs in the context of a specific Maximo user; mutual TLS secures the transport channel but does not replace the API key. Classic maxauth/session login is not used on MAS 9.
An API key is created for a given Maximo user and API calls made with it run in that user's context with that user's permissions enforced; by default no server-side web session is created, and the apikey header is recommended over the query parameter. Mutual TLS authenticates the calling system at the transport layer (both sides present certificates) and is complementary to the application-layer API key, not a replacement.