Limitations
PingIDM 8.0 has the following known limitations:
Bouncy Castle FIPS with custom JVM
You can’t use the Bouncy Castle FIPS provider with a custom JVM.
End-user UI installation
The end-user UI is no longer bundled with PingIDM. You can download and install the end-user UI separately from the ForgeRock/end-user-ui GitHub repository. Learn more in the End-user UI.
Workflow limitations
-
Workflows are not supported with a DS repository. If you are using a DS repository for IDM data, you must configure a separate JDBC repository as the workflow datasource.
-
The embedded workflow and business process engine is based on Flowable and the Business Process and Notation (BPMN) 2.0 standard. As an embedded system, local integration is supported. Remote integration is not currently supported.
Queries with a DS repository
For DS repositories, relationships must be defined in the repository configuration (repo.ds.json). If you do not explicitly define relationships in the repository configuration, you will be able to query those relationships, but filtering and sorting on those queries will not work. For more information, refer to Relationship Properties in a DS Repository.
Queries with an OracleDB repository
For OracleDB repositories, queries that use the queryFilter syntax do not work on CLOB columns in explicit tables.
Queries with privileges
Query filters used for privileges can only reference direct attributes of the object. For example, relationship fields cannot be referenced in a privilege filter.
Connector limitations
When you add or edit a connector through the admin UI, the list of required Base Connector Details is not necessarily accurate for your deployment. Some of these details might be required for specific deployment scenarios only. If you need a connector configuration where not all the Base Connector Details are required, you must create your connector configuration file over REST or by editing the provisioner file. For more information, refer to Configure connectors.