Preventive Service Planning
Abstract
When you configure security in Maximo Asset Management, you can use either Maximo authentication or application server-based authentication.
Content
When integrating data with external applications, Maximo authentication requires some configuration to enable inbound transactions.
Maximo authentication is enabled by setting the mxe.useAppServerSecurity system property to 0 (false). When Maximo authentication is used, all HTTP-based inbound transactions must specify an HTTP header with the following attributes:
The user credentials must be encoded to base64 in the following format: <username>:<password>.
Services that are called through the integration servlet and SOAP-based web services do not require an HTTP MAXAUTH header if the default integration user is enabled. You can enable the default integration user by setting the ALLOWDFLTLOGIN value to 1 (true) in the ejb-jar.xml deployment file as shown in the following code example:
<env-entry>
<env-entry-name>ALLOWDFLTLOGIN</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>1</env-entry-value>
</env-entry>
The ejb-jar.xml deployment file can be found on your Maximo administrative workstation in the following directory: c:/maximo/applications/maximo/mboejb/ejbmodule/META-INF.
The ALLOWDFLTLOGIN value must be set to 1 (true) for each of the following services in the XML file:
Enterprise Services
Object Structure Service
Standard Services
Workflow service
Maximo authentication is enabled by setting the mxe.useAppServerSecurity system property to 0 (false). When Maximo authentication is used, all HTTP-based inbound transactions must specify an HTTP header with the following attributes:
| Field | Value |
| Name | MAXAUTH |
| Value | <User credentials encoded to base64 format> |
Services that are called through the integration servlet and SOAP-based web services do not require an HTTP MAXAUTH header if the default integration user is enabled. You can enable the default integration user by setting the ALLOWDFLTLOGIN value to 1 (true) in the ejb-jar.xml deployment file as shown in the following code example:
<env-entry>
<env-entry-name>ALLOWDFLTLOGIN</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>1</env-entry-value>
</env-entry>
The ejb-jar.xml deployment file can be found on your Maximo administrative workstation in the following directory: c:/maximo/applications/maximo/mboejb/ejbmodule/META-INF.
The ALLOWDFLTLOGIN value must be set to 1 (true) for each of the following services in the XML file:
Enterprise Services
Object Structure Service
Standard Services
Workflow service
The default integration user is not supported if you use the REST API or OSLC API. After you update the ejb-jar.xml deployment file, you must rebuild and redeploy the Maximo EAR file.
Related Information
[{"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Security Authentication","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"7.6","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Was this topic helpful?
Document Information
More support for:
IBM Maximo Asset Management
Software version:
7.6
Operating system(s):
AIX, Linux, Windows
Document number:
727603
Modified date:
15 November 2019
UID
swg21965724
Manage My Notification Subscriptions