Okiok

OKIOK announces the availability of RAC/M Identity 3.20.0

Okiok



RAC/M Identity™ is our simple and effective identity governance (IGS) solution that enables large and small enterprises to understand and manage the complex relationships between users and their access to physical and digital resources, on-premise or SaaS.

IMPORTANT IMPROVEMENTS

Export administration lists to CSV or Excel

List pages in the administration portal that use DataTables now include an action to export the current result set (respecting active filters) as CSV or Excel, making it easier to work with data outside predefined reports. #474

Self-service: matrix view of team members’ accesses

A new self-service screen shows a matrix of accesses and groups for identities the user is responsible for—similar in spirit to role campaign review grids—so managers can see how access is distributed across their team. #4190

Self-service: role version detail

Role owners can open a dedicated self-service screen for a role version: choose which version to display, review the access matrix, and use panels that highlight differences versus the active version when reviewing a non-active version. #4194

Top bar: clearer identity presentation, photos, and multi-identity selection

The signed-in user is presented more clearly in the top bar of both the administration portal and self-service, including round profile photos and contextual identity information where appropriate. When the external authentication account is linked to several identities, the user can select which identity is active for the session so governance, approvals, and tasks apply to the correct employment context. #4250 #4379

Jump to a specific page in long lists and campaign reviews

Pagination controls let users go directly to a chosen page instead of stepping page by page—both on DataTables in the product and in multi-page campaign review flows—so large volumes of items are easier to navigate. #4448 #4704

System configuration page

A dedicated administration page brings system settings together with clearer names and descriptions. Starting with this version, most settings that previously lived in config.properties are stored in the database; the first startup after upgrade migrates them automatically. See the migration guide for details and for what remains in the file. #4718

OTHER IMPROVEMENTS

FIXES

Breaking change

The scripted-api-connector.jar connector in version 1.23.0.0 is not compatible with RACM 3.20 because this connector uses an old version of Groovy (4) which is not compatible with Java 25. Furthermore, since Groovy 5 is stricter about script syntax, the Groovy scripts must also be updated.

1. Procedure to update the Groovy scripts

You must ensure that enums end with a semicolon. They can no longer end with a comma.

Before

enum OracleFusionLocationAttribute implements ScriptedAPIAttribute<JSONObject, RESTObjectClass>
{
    LOCATION_ID("LocationId"),
    LOCATION_NAME("LocationName"),

After

enum OracleFusionLocationAttribute implements ScriptedAPIAttribute<JSONObject, RESTObjectClass>
{
    LOCATION_ID("LocationId"),
    LOCATION_NAME("LocationName");

2. Update procedure for the scripted connector

  1. Delete all files from previous versions of the scripted connector:
    scripted-api-connector-*.jar (1.16, 1.23.0, etc.)

  2. Place the new version of the connector in the appropriate folder:
    ICF/server/connectors/scripted-api-connector-1.23.0.2.jar

  3. Create the folder ICF/reference-scripts/scripted-api-1.23.0.2 and copy the scripts updated in step 1 into it.

  4. Retrieve the script ID (TARGET_SYSTEM_ID) from the database using the following query. Choose the appropriate script row using the name and description, then copy the corresponding TARGET_SYSTEM_ID.

    SELECT TARGET_SYSTEM_ID, NAME, DESCRIPTION FROM TARGET_SYSTEM

    Example: For the BPM Helix script, the value to copy is 285

  5. Execute the following SQL query, replacing <TARGET_SYSTEM_ID> with the value retrieved in the previous step:

    UPDATE TARGET_SYSTEM SET VERSION = '1.23.0.2' WHERE TARGET_SYSTEM_ID = <TARGET_SYSTEM_ID>

  6. In the connector configuration in RACM, update the Script Path so that the value reflects the name of the directory created in step 3.
    Relative URL: /gui/configurationTargetSystem.action?targetSystemId=<TARGET_SYSTEM_ID>

  7. Run the sequence linked to this script to test that everything works.

Previous versions

Exit mobile version