Opqo 24.05.0 supports setting Maximo configuration information via managed configuration provided by Mobile Device Management (MDM) software.
When a managed configuration is present, Opqo will automatically configure the Maximo configuration details:
- On first launch.
- When the application is activated to the Login screen, if the managed configuration is in use.
- When a user logs out and is returned to the Login screen, if the managed configuration is in use.
This means that Maximo configuration details can be not only provided via MDM managed configuration for the initial configuration, but also maintained via managed configuration should these details change.
Currently, the user is able to switch to a non-managed Maximo configuration. The managed configuration will remain in the list of "discovered" environments allowing the user to easily switch back to the managed configuration.
The managed configuration properties that can be set are as follows:
Note: Some MDMs only allow String values to be provided as part of managed configurations. In this case:
|
| Name | Data Type | Notes |
| host | String | Required. The hostname of the Maximo environment to connect to. Should contain only the hostname. |
| name | String | Optional. The name of the connection to display to the user. |
| type | String | Optional. "PROD" for production environments, any other value for non-production The value for non-production environments is displayed to the user. |
| ssl | Boolean | Optional. Whether the connection should use SSL. If not specified, the default is: true. |
| port | Integer | Optional. The port to connect to the Maximo server on. Must be a valid TCP port. If not specified, will use the standard HTTP/S ports (80/443), depending on whether ssl is used or not. |
| utcert | Boolean | Optional. Whether to accept untrusted/self-signed SSL certificates when connecting to Maximo and ssl is enabled. If not specified, the default value is "false". |
| app | String | Optional. The Maximo app context. If not specified, the default value is "maximo". |
| api | String | Optional. The Maximo API context for the REST API. If not specified, the default value is "oslc" |
| auth | String | Optional. The authentication method to use when connecting to Maximo. Valid values are:
"standard": For Maximo environments configured with internal authentication, LDAP (BASIC auth) or Forms authentication. This also includes MAS development environments. "maxauth": For Maximo environments configured with internal authentication. This option will only send the MAXAUTH header for authentication. Typically not required, as "standard" should suffice. "ldap": For Maximo environments configured with LDAP authentication. This option will only send the HTTP BASIC authentication header for authentication. Typically not required, as "standard" should suffice. "saml": For Maximo environments configured with SAML authentication. If not specified, the default value is "standard" |
| csrf | Boolean | Optional. Whether Opqo should request a CSRF protected session when connecting to Maximo. CSRF protected sessions are required when applying updates to Maximo, when the system property mxe.oslc.enforcecsrf is enabled. Note that Opqo will automatically upgrade a non-CSRF session to a CSRF protected session if an update fails by disconnecting and establishing a new connection. However, setting this value to "true" if your Maximo environment requires it will be more efficient. If not specified, the default value is "false". |