Error in the uimapi.log:
2025-04-30 16:26:39.554 [https-jsse-nio-443-exec-33] DEBUG com.ca.uimapi.config.UimApiJWTVerificationFilter:doFilter:87 config.UimApiJWTVerificationFilter - Recieved request from: xx.xx.xx.xx
2025-04-30 16:26:39.554 [https-jsse-nio-443-exec-33] ERROR com.ca.uimapi.config.UimApiJWTVerificationFilter:doFilter:97 config.UimApiJWTVerificationFilter - Missing or invalid authentication information
Steps:
Notice in the wasp.cfg, the setting "useBasicAuthFor..."
...If JWT token enablement is done on OC wasp then it is recommended to set useBasicAuthForUIMAPI = false to honor the JWT session handling.
Similarly for the OI Connector, you must also enable the https_enabled checkbox in the OC configuration section of the OI Connector configuration UI.
Also for JWT session handling set the OC wasp probe-> useBasicAuthForRest = false
In UIM, Basic Authentication is enabled by default for wasp and web service endpoints.
JWT authentication
These are the primary checks UIM performs to execute any UIM API endpoint.
We have tested with both a NimBUS user defined via IM and an Account user (using LDAP and account admin) and everything works as expected.
1. Make sure you're not hitting the wrong endpoint,
and
2. The current account user MUST have permission to view the data.
For all APIs, users need to have "Web Service" permission:
In addition, each API has functional specific permissions. For /uimapi/devices call, users need to have "Basic Management" permission.
A list of each API call type and the required ACL/permission seems to be missing from the UIMAPI techdocs/swagger.
For webservices this IS documented for each call type. Please refer to: