Known issues and limitations

Certain product features assume that the system is deployed by using a centralized deployment model where services share the file system and product binaries. With containerized deployments, services no longer have a common file system and are working in isolation.

Following is the list of known issues and limitations.
Feature Admin UI Containerized deployment
System Administrator > Properties Displays all the properties that are listed in the configuration files such as common.properties and db.xml. Displays property values that are configured for the ipm-admin container.
System Administrator > Log Files Displays all the log files for each service in the log folder. Display log files present in the ipm-admin container.
  • After the SAML SSO is enabled, the default Admin user as well as any local user that does not exist on the Identity Provider is not be able to log in to the Admin UI and the Persona-based UI applications.
  • Roles that are created by the SAML SSO login grant default ACG permissions hence the Administrator needs to set correct permissions for such roles.
  • Any deletion of users or roles on the Identity Provider is not synced with the Product Master database as part of SAML SSO. This should be handled by the customer as a routine administrative task.
  • User attributes for users who are created by the SAML SSO login cannot be edited from the Product Master Admin UI as the user edit screen is in read only mode.
  • Even though the Logout option is available on the Admin UI and Persona-based UI once the user clicks the Logout option, the user gets redirected to the main application URL. This triggers the SAML SSO flow again.
  • There are different session timeouts users need to be aware of. Each UI has its own configured timeout as well as SAML token have the expiry set by the Identity Provider. It is recommended to increase the session timeouts for both the application UI as well as SAML token to have a better user experience when SAML SSO is enabled.
  • REST API access with SAML SSO through external source (custom code) is not yet supported. This is a known limitation.
  • Scheduler > Scheduler Status page does not display job progress details and progress percentage on the Admin UI.