NetIQ Identity Manager 4.7 Service Pack 2 Release Notes
NetIQ Identity Manager 4.7 Service Pack 2 provides new features, improves usability, and resolves several previous issues. Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the Identity Manager Community Forums on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.
The documentation for this product and the latest release notes are available on the NetIQ Web site on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at the Identity Manager Documentation Web site.
2.0 Installing or Updating to This Service Pack
Log in to the NetIQ Downloads page and follow the link that allows you to download the software.
The following files are available:
|
Filename |
Description |
|---|---|
|
Identity_Manager_4.7.2_Linux.zip |
Contains files for Identity Manager Server (Identity Manager Engine, Remote Loader, Fanout Agent), Identity Applications, and Identity Reporting for Linux platform. NOTE:This file also contains JDBC Fanout and Managed System Gateway driver files. |
|
Identity_Manager_4.7.2_Windows.zip |
Contains files for Identity Manager Server (Identity Manager Engine, Remote Loader, Fanout Agent), Identity Applications, and Identity Reporting for Windows platform. NOTE:This file also contains JDBC Fanout and Managed System Gateway driver files. |
|
Identity_Manager_4.7.2_Linux_Designer.tar.gz |
Contains Designer for Linux |
|
Identity_Manager_4.7.2_Windows_Designer.zip |
Contains Designer for Windows |
|
Identity_Manager_4.7.2_MacOSX_Designer.dmg |
Contains Designer for MacOS 10.13 (High Sierra) |
|
SentinelLogManagementForIGA8.2.0.0.tar.gz |
Contains Sentinel Log Management for Identity Governance and Administration (IGA) files. NOTE:This installation is supported only on Linux. |
For more information about the order of upgrading the components, see Update Order.
2.1 Supported Update Paths
You need to be on Identity Manager 4.7 to update to Identity Manager 4.7.2. If you are currently on Identity Manager 4.6.2 or a prior version, you must first upgrade to 4.7 and then update to 4.7.2 version.
The update process requires you to update Identity Manager components in a specific order. NetIQ recommends that you review this information from the release notes for your current version.
|
Base Version |
Updated Version |
|---|---|
|
Identity Manager engine and eDirectory |
|
|
Identity Manager 4.7 or 4.7.1 with eDirectory 9.1 or 9.1.1 |
Identity Manager 4.7.2 with eDirectory 9.1.2 |
|
Remote Loader |
|
|
Identity Manager 4.7 or 4.7.1 with Remote Loader 4.7 |
Identity Manager 4.7 with Remote Loader 4.7.2 |
|
Identity Manager 4.7.2 with Remote Loader 4.7 |
|
|
Identity Manager 4.7.2 with Remote Loader 4.7.2 |
|
|
Identity Manager Designer Identity Manager Designer 4.7, 4.7.0.1, 4.7.1, or 4.7.1.1 |
|
|
Identity Manager Designer 4.7.2 |
|
|
|
|
Identity Applications |
|
|
Identity Applications 4.7 or 4.7.1 |
Identity Applications 4.7.2 |
|
|
|
Identity Reporting |
|
|
Identity Reporting 4.7 or 4.7.1 |
Identity Reporting 4.7.2 |
2.2 Update Order
You must update the components in the following order:
-
Identity Vault
-
Identity Manager Engine
-
Remote Loader
-
Fanout Agent
-
iManager Web Administration
-
Identity Applications (for Advanced Edition)
-
Identity Reporting
-
Designer
-
Sentinel Log Management for IGA
-
One SSO Provider (OSP)
NOTE:Standalone update of OSP is supported only on Windows.
-
Self-Service Password Reset
2.3 Updating the Identity Manager Components on Linux
This service pack includes a Identity_Manager_4.7.2_Linux.zip file for updating the Identity Manager components on Linux platforms.
Updating the Identity Vault
-
Download and extract the Identity_Manager_4.7.2_Linux.zip file from the download site.
-
Locate the directory in the extracted folder.
-
Run the following command:
./nds-install
Updating the Identity Manager Components
You can update the following components interactively or silently:
NOTE: Before updating the Remote Loader, ensure that the following components are stopped:
-
Identity Vault
-
Driver instances running with the Remote Loader
-
Remote Loader instances
-
Remote Loader console
Interactive Update
-
Download and extract the Identity_Manager_4.7.2_Linux.zip file from the download site.
-
Run the following command from the extracted directory:
./install.sh
-
Select , then choose the components to update from the list of available components.
NOTE:You can update only one component at a time.
If you want to update the Identity Vault, select and follow the steps from Updating the Identity Vault.
Silent Update
Locate the silent.properties file in the extracted directory and modify the file to update the required components.
-
To update to the Identity Vault, set IDVAULT_SKIP_UPDATE=False
-
To update the Engine, set INSTALL_ENGINE = true
-
To update the Remote Loader, set INSTALL_RL = true
-
To update the Fanout Agent, set INSTALL_FA = true
-
To update iManager, set INSTALL_IMAN=true
-
To update the Identity Applications, set INSTALL_UA = true
-
To update Identity Reporting, set INSTALL_REPORTING = true
NOTE:
-
You must set the value to True for only one component at a time.
-
When you update iManager, it will automatically update the iManager plug-ins (if any).
Perform the following actions to update the components silently:
-
Download and extract the Identity_Manager_4.7.2_Linux.zip file from the download site.
-
Modify the file to update the required components.
-
Run the following command:
./install.sh -s -f silent.properties
Performing a Non-Root Update
Perform this action only if you have installed Identity Manager engine as a non-root user.
-
Run the following command from the extracted directory:
./install.sh
NOTE:Do not use the idm-nonroot-install script located under /<Linux zip file extracted location>/IDM/ directory to perform a non-root installation. If you use that script, the netiq-zoomdb-1.1.0-0.noarch.rpm and novell-IDMCEFProcessorx-1.0.0-0.x86_64.rpm will not be installed.
-
Select and press Enter.
-
Specify the non-root install location for Identity Vault.
For example, /home/user/eDirectory/.
-
Specify to complete the update.
Post-Update Tasks
Perform the following actions after applying service pack. This section is applicable when updating from 4.7 to 4.7.2.
Extending the Identity Vault Schema
This section applies if you have performed a root installation of Identity Manager Engine.
To extend the Identity Vault schema, perform the following steps:
-
Navigate to /opt/novell/eDirectory/bin directory.
-
Run the following command:
./idm-install-schema
Post-Update Steps for Identity Applications
-
Ensure that you clear the browser cache after you update the Identity Applications.
-
Perform this action only if the following conditions are true:
-
Identity Applications are installed silently.
-
NETIQ_DATABASE_CONFIG_ADMIN is different than NETIQ_DATABASE_ADMIN. For example, idmadmin and postgres.
If the schema does not update properly, run the liquibase command with NETIQ_DATABASE_CONFIG_ADMIN credentials.
-
This command is located in the /var/opt/netiq/idm/log/idmconfigure.log file. Ensure that you modify the parameters as per your need. For example,
/opt/netiq/common/jre/bin/java -Dwar.context.name=IDMProv -Ddriver.dn="cn=User Application Driver,cn=driverset1,o=system" -Duser.container="o=data" -jar /opt/netiq/idm/apps/UserApplication/liquibase.jar --databaseClass=liquibase.database.core.PostgresDatabase --driver=org.postgresql.Driver --classpath=/opt/netiq/idm/postgres/postgresql-9.4.1212.jar:/opt/netiq/idm/apps/tomcat/webapps/IDMProv.war --changeLogFile=DatabaseChangeLog.xml --url="jdbc:postgresql://:5432/idmuserappdb?compatible=true" --contexts="prov,newdb,updatedb" --logLevel=debug --username=***** --password=**** update >> /var/opt/netiq/idm/log/db.out
Performing a Standalone Update of SSPR
NOTE:Use this method if SSPR is:
-
Installed on a different server than the Identity Applications server.
-
Installed in a Standard Edition.
Perform the following steps to update SSPR:
-
Download and extract the Identity_Manager_4.7.2_Linux.zip file.
-
Locate the sspr directory in the extracted file.
-
Run the following command:
./install.sh
Updating PostgreSQL
(Conditional) If you are using PostgreSQL as your database, this service pack requires you to update your existing PostgreSQL database version to 9.6.10.
The following considerations apply when you update PostgreSQL:
Update PostgreSQL used with Identity Manager 4.7: The PostgreSQL update program backs up the existing PostgreSQL home directory and appends the existing PostgreSQL version number. For example, the existing PostgreSQL directory is renamed from /opt/netiq/idm/postgres to /opt/netiq/idm/postgres9.6.6. The new PostgreSQL is installed in the /opt/netiq/idm/postgres directory.
-
Download and extract the Identity_Manager_4.7.2_Linux.zip file from the download site.
-
Navigate to the Identity_Manager_4.7.2_Linux/common/scripts directory in the extracted file and run the pg-upgrade.sh script.
NOTE:If you want to specify a different directory apart from the existing directory, then you need to run the SPECIFY_NEW_PG_DATA_DIR=true ./pg-upgrade.sh command.
The upgrade script performs the following actions:
-
Takes a backup of the existing postgres to a different folder. For example, from /opt/netiq/idm/postgres to /opt/netiq/idm/postgres-201810221903-backup.
-
Updates the existing Postgres directory. For example, /opt/netiq/idm/postgres.
-
-
Specify the following details to complete the installation:
Existing Postgres install location: Specify the location where PostgreSQL is installed. For example, /opt/netiq/idm/postgres.
Existing Postgres Data Directory: Specify the location of the existing PostgreSQL data directory. For example, /opt/netiq/idm/postgres/data.
Existing Postgres Database Password: Specify the PostgreSQL password.
2.4 Updating the Identity Manager Components on Windows
This service pack includes a Identity_Manager_4.7.2_Windows.zip file for updating the Identity Manager components on Windows platforms.
Updating the Identity Vault
-
Download and extract the Identity_Manager_4.7.2_Windows.zip file.
-
Locate the IDVault directory in the extracted file.
-
Run the eDirectory_912_Windows_x86_64.exe file:
NOTE:The Identity Vault update process restarts the Identity Vault (eDirectory) server.
- Tree Name
-
Specify a tree name for Identity Vault.
- Server FDN
-
Specify a server FDN.
NOTE:Though Identity Vault allows you to set the NCP server object's FDN up to 256 characters, NetIQ recommends that you restrict the variable to a much lesser value because Identity Vault creates other objects of greater length based on the length of this object.
- Tree Admin
-
Specify an administrator name for Identity Vault.
- Admin Password
-
Specify the administrator password.
-
In the field, specify the location where Identity Vault is installed.
-
In the field, specify the location where the DIB files are located.
-
Select the check box.
-
Click .
Updating the Identity Manager Engine and Remote Loader
-
Download and extract the Identity_Manager_4.7.2_Windows.zip file.
NOTE:This file also contains JDBC Fanout and Managed System Gateway driver files.
-
Stop the Identity Vault and Remote Loader instances.
-
Stop all drivers.
-
Stop all Remote Loader instances.
NOTE:You must close the Remote Loader console before upgrading the Remote Loader.
-
Stop the Identity Vault.
-
-
Locate the IDM directory in the extracted file.
-
Install the updates by interactive or silent mode of installation.
-
For interactive mode: Run <patch_path>\install.bat and select the component that you want to update from the list.
To update Identity Manager Engine, select .
To update the 32-bit Remote Loader, select .
To update the 64-bit Remote Loader, select .
To update the .NET Remote Loader, select .
-
For silent mode: Run <patch_path>\install.bat -i silent -f patchUpgradeSilent.Properties.
When you update the Identity Manager engine, the JDBC Fanout and Managed Service Gateway drivers are also updated.
-
-
(Conditional) If you added a custom trusted root certificate to the existing Java keystore (C:\NetIQ\idm\jre\lib\security\cacerts), import the certificate to the new keystore.
keytool -importkeystore -srckeystore <Old-cacerts> -destkeystore C:\NetIQ\idm\jre\lib\security\cacerts -srcstoretype JKS -deststoretype JKS -srcstorepass <storePassword> -deststorepass changeit -srcalias <mycertAlias>
Run this command for each custom certificate created. Alternatively, copy the keystore to the new location.
For example, the old cacerts files are backed-up in the following locations on Windows:
-
\backup location\cacerts.32 from 32-bit JRE
-
\backup location\cacerts.64 from 64-bit JRE
-
Manually Updating the Fanout Agent
IMPORTANT:The update program does not detect the already installed Fanout Agent on your computer. Therefore, it does not provide an option for updating this component.
-
Replace the existing FanoutAgent.jar and fanout_web.war, files in C:\NetIQ\IdentityManager\FanoutAgent\lib folder from the \Identity_Manager_4.7.2_Windows\IDM\patch\Windows\FanoutAgent\lib folder in the Identity_Manager_4.7.2_Windows.zip file.
-
(Conditional) Add the IDMCEFProcessor.jar and zoomdb.jar files from\Identity_Manager_4.7.2_Windows\IDM\patch\Windows\FanoutAgent\lib to C:\NetIQ\IdentityManager\FanoutAgent\lib and use the latest JDBC 4.2.0.0. Fanout driver.
-
Restart the Fanout Agent.
-
Restart the Identity Vault.
Updating Identity Applications
-
Download and extract the Identity_Manager_4.7.2_Windows.zip file.
-
Locate the IdentityApplications directory in the extracted directory.
-
Perform one of the following actions:
GUI: install.exe
Silent: install.exe -i silent -f silent.properties
The Identity Applications update program will update User Application, OSP, SSPR, Tomcat, and JRE.
-
On the page, click .
-
Review the page, then click .
This page lists the currently installed components with their versions.
-
On the page, click .
This page lists the available updates for the installed components.
-
To restore the certificates for communication between the identity applications and the LDAP server, specify the JRE truststore password and then click .
For example, if your certificate is located in C:\netiq\idm\jre\lib\security\cacerts, specify the password to access the certificate.
The identity applications need certificates (cacerts or custom keystore) for communicating with the Identity Manager server.
-
Review the required disk space and available disk space for installation in the page, then click .
The installation process might take some time to complete.
Before applying the service pack, the installation process automatically stops the Tomcat service.
The process also creates a back-up of the current configuration for the installed components.
In case, the installation reports any warnings or errors, see the logs from the Service Pack Installation/Logs directory.
For example, C:\netiq\idm\apps\Identity_Apps_4.7.2.0_Install\Logs. You must fix the issues and manually restart the Tomcat service.
-
Start the Tomcat service.
-
(Optional) To verify that the service pack has been successfully applied, launch the upgraded components and check the component versions.
Updating Identity Reporting
-
Download and extract the Identity_Manager_4.7.2_Windows.zip file.
-
Stop Tomcat.
-
Create a backup directory outside of the Tomcat installation path.
-
Locate the C:\NetIQ\idm\apps\tomcat\webapps directory in the extracted file and copy the following files to the backup directory you created in Step 3.
-
IDMRPT-CORE.war
-
IDMRPT.war
-
idmdcs.war
-
IDMDCS-CORE.war
-
dcsdoc.war
-
-
Delete the following files from these directories:
-
IDMRPT-CORE, IDMRPT, idmdcs, IDMDCS-CORE, and dcsdoc folders from the C:\NetIQ\idm\apps\tomcat\webapps directory.
-
localhost folder from the C:\NetIQ\idm\apps\tomcat\work\Catalina directory.
-
All files and folders from the C:\NetIQ\idm\apps\tomcat\temp directory.
-
cache and plugins folders from the C:\NetIQ\idm\apps\IdentityReporting\reportContent directory.
-
-
Locate the Reporting directory in the extracted file in Step 1.
-
Copy the following files to the C:\NetIQ\idm\apps\tomcat\webapps directory.
-
IDMRPT-CORE.war
-
IDMRPT.war
-
idmdcs.war
-
IDMDCS-CORE.war
-
dcsdoc.war
-
-
(Conditional) Delete or take a back-up of the existing logs from the C:\NetIQ\idm\apps\tomcat\logs directory.
-
Clear your browser cache before accessing Identity Reporting.
-
Start Tomcat.
Post-Update Tasks
Perform the following actions after applying this service pack. This section is applicable when updating from 4.7 to 4.7.2.
Extending the Identity Vault Schema
To extend the Identity Vault schema, navigate to the C:\NetIQ\eDirectory\ directory and run the following command:
ice -l <schema_update_log> -C -a -S SCH -f <Identity_Manager_4.7.2_Windows.zip Extracted location>\Identity_Manager_4.7.2_Windows\IDM\patch\Windows\engine\schema\edirectory-schema.sch -D LDAP -s <eDirectory DNS name/IP> -p <LDAP port> -d <eDirectory_admin_dn> -w <eDirectory_admin_password>
where,
-C -a updates the destination schema.
-f indicates the schema file (sch).
-p indicates the port number of the LDAP server. The default port is 389. For secure communication, use port 636. Secure communication needs an SSL Certificate.
-L indicates a file in DER format containing a server key used for SSL authentication.
-s indicates the DNS name or IP address of the LDAP server.
For example,
ice -l schemaupdate.log -C -a -S SCH -f C:\Identity_Manager_4.7.2_Windows\IDM\patch\Windows\engine\schema\edirectoryschema.sch -D LDAP -s idmorg.com -p 636 -d cn=admin,ou=idm,o=microfocus -w password -L cert.der
Post-Update Steps for Identity Applications
-
Clear the browser cache.
-
If the LDAP server name in the LDAP server certificate subject is different from what is used in the Identity Applications, change the name of the LDAP server in the Identity Applications configuration to the name of the LDAP server available in the LDAP server certificate subject.
Identity Manager 4.7.2 upgrades Java to 1.8.0_192. Java has enabled endpoint identification on LDAPS connections from JRE 1.8.0_181. This requires you to use the same server name for connecting to the Identity Manager server that was provided with the LDAP server certificate subject. Otherwise, the connection fails.
To change the name of the server in the Identity Applications configuration:
-
Open the ConfigUpdate utility (configupdate.sh or configupdate.bat).
-
Navigate to the tab, click , and change the name of the server to what is provided with the LDAP server certificate subject.
This action updates the DirectoryService/realms/jndi/params/AUTHORITY property in the ism-configuration.properties file.
-
-
(Conditional) Perform this action only if the following conditions are true:
-
Identity Applications are installed silently.
-
NETIQ_DATABASE_CONFIG_ADMIN is different than NETIQ_DATABASE_ADMIN. For example, idmadmin and postgres.
If the schema does not update properly, run the liquibase command with NETIQ_DATABASE_CONFIG_ADMIN credentials to update it.
The command can be found in the C:\netiq\idm\apps\UserApplication\NetIQ-Custom-Install file. Ensure that you modify the parameters as per your need.
For example:
"C:\netiq\idm\apps\jre\bin\java" -Xms256m -Xmx256m -Dlog4j.configuration=file:C:\netiq\idm\apps\tomcat\conf\userapp-log4j.xml -Dwar.context.name=IDMProv -Ddriver.dn="cn=UserApplication,cn=Driver Set,o=system" -Duser.container="o=data" -jar "C:\netiq\idm\apps\UserApplication\liquibase.jar" --databaseClass=liquibase.database.core.PostgresDatabase --driver=org.postgresql.Driver --classpath="C:\NetIQ\idm\apps\postgres\postgresql-9.4.1212.jdbc42.jar;C:\netiq\idm\apps\tomcat\webapps\IDMProv.war" --changeLogFile=DatabaseChangeLog.xml --url="jdbc:postgresql://:5432/idmuserappdb?compatible=true" --contexts="prov,newdb,updatedb" --logLevel=info --username=******** --password=******** update >> C:\netiq\idm\apps\UserApplication\db.out
-
Updating the PostgreSQL Database
(Conditional) If you are using PostgreSQL as your database, this service pack requires you to update your existing PostgreSQL database version to 9.6.10.
-
Stop and disable the PostgreSQL service.
-
Rename the postgres directory from C:\Netiq\idm\apps.
For example, rename postgres to postgres9.6.10.
-
Remove the old PostgreSQL service by running the following command:
sc delete "postgres_service_name"
For example, sc delete "postgresql-x64-9.6"
-
Download and extract the Identity_Manager_4.7.2_Windows.zip file.
-
Navigate to the Identity_Manager_4.7.2_Windows\common\packages\postgres directory and run the NetIQ_PostgreSQL.exe file.
-
Stop the newly installed PostgreSQL service. Go to , search for PostgreSQL version service, and stop the service.
NOTE:Appropriate users can perform stop operations after providing valid authentication.
-
Change the permissions for the newly installed PostgreSQL directory by performing the following actions:
Create a postgres user:
-
Go to > > > .
-
Click .
-
In the page, specify postgres as the user name and provide a password for the user.
Provide permissions to postgres user to the existing and newly installed PostgreSQL directories:
-
Right click the PostgreSQL directory and go to > > .
-
Select to provide complete permissions.
-
Click .
-
-
Access the PostgreSQL directory as postgres user.
-
Login to the server as postgres user.
Before logging in, make sure that postgres can connect to the Windows server by verifying if a remote connection is allowed for this user.
-
Delete the data directory from the new postgres install location.
For example, C:\NetIQ\idm\apps\postgres9.6.10\data.
-
Open a command prompt and set PGPASSWORD by using the following command:
set PGPASSWORD=your pg password
-
Change to the newly installed PostgreSQL directory.
For example, C:\netiq\idm\apps\postgresql9610\bin.
-
Execute initdb as postgres database user from the new PostgreSQL bin directory.
initdb.exe -D <new_data_directory> -E <Encoding> UTF8 -U postgres
For example, initdb.exe -D C:\NetIQ\idm\apps\postgres9.6.10\data -E UTF8 -U postgres
-
-
Upgrade PostgreSQL from new PostgreSQL bin directory. Run the following command and click :
pg_upgrade.exe --old-datadir "C:\NetIQ\idm\apps\postgres9.6.9\data" --new-datadir
"C:\NetIQ\idm\apps\postgres9.6.10\data" --old-bindir
"C:\NetIQ\idm\apps\postgres9.6.9\bin" --new-bindir
"C:\NetIQ\idm\apps\postgres9.6.10\bin"
-
After successful upgrade, replace the pg_hba.conf and postgresql.conf files located in the new postgres data directory (C:\NetIQ\idm\apps\postgres\data) with the files from old postgres directory (C:\NetIQ\idm\apps\postgres9.6.9\data).
-
Start the upgraded PostgreSQL database service.
Go to , search for the upgraded PostgreSQL service, and start the service.
NOTE:Appropriate users can perform start operations after providing valid authentication.
-
(Optional) Delete the old data files from the bin directory of the newly installed PostgreSQL service.
-
Log in as postgres user.
-
Navigate to the bin directory and run analyze_new_cluster.bat and delete_old_cluster.bat files.
For example,C:\NetIQ\idm\apps\postgresql9610\bin
-
2.5 Installing and Upgrading Designer
You can install Identity Manager Designer using an executable file, binary file, or in text mode, depending on the target computer. For more information on the files available, see Installing or Updating to This Service Pack.
Installing Designer on Linux
-
Download the Identity_Manager_Linux_Designer.tar.gz from the NetIQ Downloads website.
-
Navigate to a directory where you want to extract the file.
tar -zxvf Identity_Manager_Linux_Designer.tar.gz
-
Run one of the following commands to install Designer.
Console: ./install -i console
GUI: ./install -i gui
or
./install
-
Follow the prompts and complete the installation.
Installing Designer on Windows
-
Download and extract the Identity_Manager_4.7.2_Windows_Designer.zip from the NetIQ Downloads Website.
-
Run the install.exe file.
-
Follow the steps in the wizard until the installation process completes.
Installing Designer on MacOS 10.13 (High Sierra)
NetIQ provides Identity_Manager_4.7.2_MacOSX_Designer.dmg file for installing Designer on MacOS 10.13.
Regardless of the method of installation, ensure that the computer on which you are installing Designer meets the following system requirements:
-
Processor: 1 GHz
-
Disk space: 1 GB
-
Memory: 1 GB
Perform the following actions to install Designer from the Identity_Manager_4.7.2_MacOSX_Designer.dmg file:
-
Download Identity_Manager_4.7.2_MacOSX_Designer.dmg from NetIQ Downloads Web Site.
NOTE:Sometimes quarantine attributes such as com.apple.quarantine are included in the Designer application that prevents you from launching Designer. To resolve this issue, see Unable to Launch Designer Application on Macon NetIQ Designer for Identity Manager Administration Guide.
-
From the pop-up window that appears, drag and drop the Designer folder into the location where you want to install it.
By default, Mac prompts you to download Designer into the Applications folder. If you choose to install Designer in this folder, Mac creates a Designer shortcut on the launchpad.
IMPORTANT:The following considerations apply to installing two instances of Designer on your operating system:
-
Install the instances in two different folders.
-
Install the new instance in a folder that has an existing instance of Designer. In this case, ensure that you rename the first instance before placing a new instance of Designer.
-
-
If you are launching Designer for the first time and see the following message, you must run the updateInfoPlistScript.py script. It updates the Info.plist files of the Designer and Azul Zulu JDK applications with missing capabilities in absence of which you see this message.
If you do not see this message, directly go to Step 4.
Figure 1 Install legacy Java SE 6 message
NOTE:In case you do not have the Azul Zulu JDK version 1.8.0_192 installed in the system, install it from <jdk>.dmg file only before you run the updateInfoPlistScript.py script.
Perform the following actions:
-
Open a browser and specify the following URL: https://nu.novell.com/designer/IDM-Designer-MacOSX/.
-
Download the updateInfoPlistScript.py file.
-
Launch a terminal window and run the following command from the directory where you have downloaded the updateInfoPlistScript.py file:
sudo python updateInfoPlistScript.py
-
Specify the value corresponding to the Azul Zulu JDK version 1.8.0_192.
-
From the list of Designer versions displayed, specify the value corresponding to the required Designer version.
The Info.plist file is updated.
-
-
Launch Designer by clicking the icon on the launchpad or the Designer application from the installed folder.
For more information about using Designer, see NetIQ Designer for Identity Manager Administration Guide.
Uninstalling Designer
To uninstall Designer, right click the Designer folder and select .
After Designer is uninstalled, the shortcut is automatically removed from the launchpad.
For troubleshooting Designer, see Troubleshooting Designer in NetIQ Designer for Identity Manager Administration Guide.
Upgrading to Designer 4.7.2
For information about the supported upgrade paths, see Supported Update Paths.
For instructions on upgrading Designer, see Installing and Upgrading Designer.
2.6 Updating Azul Zulu OpenJRE 1.8.0_192 for Analyzer
This service pack updates Analyzer to support Azul Zulu OpenJRE 1.8.0_192 (32-bit).
-
On the server where you installed Analyzer, create a directory for Java 1.8.
For example, opt/netiq/jre1.8.0_192.
-
Download and install the Java 1.8 files in this directory.
-
Open the Analyzer.ini file located in the Analyzer installation directory.
-
Update the Java path in the Analyzer.ini file.
2.7 Support for Integration with Identity Governance
Identity Governance 3.5 uses OSP JSON Web Tokens (JWT). For integrating Identity Governance with Identity Manager 4.7.2, you must configure OSP to create JWTs.
To configure OSP for JWTs, see Configuring Identity Manager for Integration.
2.8 Updating Sentinel Log Management for IGA
This service pack includes a SentinelLogManagementForIGA8.2.0.0.tar.gz file for updating the Sentinel Log Management for Identity Governance and Administration (IGA) component. For update instructions, see the steps listed in the Sentinel Readme file.
-
Download the SentinelLogManagementForIGA8.2.0.0.tar.gz file to the server where you want to install this version.
-
Run the following command to extract the file:
tar zxvf SentinelLogManagementForIGA8.2.0.0.tar.gz
-
Navigate to the SentinelLogManagementforIGA directory.
-
To install SLM for IGA, run the following command:
./install.sh
2.9 Enabling CEF Audit for SSPR
For more information on enabling CEF audit for SSPR, see Auditing for Self Service Password Reset in Self Service Password Reset Administration Guide.