The most common forms of authentication to use with REST API are:
- Native - (MaxUser Tables)
- LDAP - (Directory service authentication)
Update: In Mas Manage, The former methods of utilizing maxauth (native authentication) or basic auth (LDAP) are no longer supported because MAS provides its own OIDC identity provider OOB. So we need to utilize API key and utilize the /maximo/api route.
Native Authentication
is configured to manage users' credentials within Maximo MaxUsers tables. Maximo is responsible for authenticating all the incoming REST calls.
The Below System property tells us the application security is off. Also, the HTTP request header and return are shown below:
|
System Property |
||
|
|
mxe.useAppSecurity |
0 |
|
URL call |
||
|
|
http://localhost/maximo/oslc/login |
|
|
Request Headers |
||
|
|
MAXAUTH |
<BASE64encoded user:password> |
|
Response in Return |
||
|
|
JSESSIONID |
As cookie to maintain the same session |
NOTE: Postman automatically save these cookies and utilize them for subsequent calls, but it can be handled programmatically.
LDAP
The Below System property tells us the application security is ON.
|
System Property |
||
|
|
mxe.useAppSecurity |
1 |
in LDAP Maximo uses directory authentication and validates users' credentials from the directory configured in WebSphere.
In this case, security settings are defined in WEB.XML file in below mentioned 4 files
maximo/application/maximoweb.xml maximo/application/maxrestweb.xml maximo/application/mboweb.xml maximo/application/meaweb.xml
in these files <login-config> section needs to be uncommented to use either FORM or BASIC authentication.
