System information

Known Issues
Page 42 Identity Manager 7.1 Update 1 • Release Notes
• When installing Password Synchronization, be sure to use the binary that is appropriate for
the operating system on which you are installing. The binary for 32-bit Windows is called
IdmPwSync_x86.msi and the binary for 64-bit Windows is called IdmPwSync_x64.msi . If you
install the wrong binary, it may appear to succeed, but Password Synchronization will not
operate properly. (ID-17290)
When uninstalling Password Synchronization, use the Windows Add or Remove Programs
feature from the Control Panel to ensure correct removal.
• Identity Manager’s round robin account policy might not generate sequential order
assignment of authentication questions. (ID-17295)
• A Sealing violation exception might occur when you use Identity Manager 7.1 or 7.1
Update 1 with Oracle 10g on Sun Java
™
System Application Server Enterprise Edition 8.2.
The problem can be caused by having more than one Oracle JDBC JAR file in the
CLASSPATH
or by having an incompatible version of the JDBC JAR file in the
CLASSPATH . (ID-17311)
Be sure there is only one Oracle JDBC JAR file in the
CLASSPATH and that it is a compatible
version, such as the JAR file supplied during the Oracle install.
• WRQ looks though the
classpath to discover its own entry. From that entry, WRQ
computes the directory where the
JAR is stored, and then uses that directory to read the
.JAW (licensing file). However, both BEA and WebSphere use non-standard protocol names
(BEA uses
zip , and WebSphere uses wsjar ) rather than the standard JAR , which is the
protocol the WRQ code assumes exists. (ID-17319)
Workaround: Add the following option to the
java command in the
startWeblogic.sh file:
-Dcom.wrq.profile.dir="< dir containing JAW file >"
• Before creating a new resource, be sure to enable the resource type in the list of configured
types. Otherwise, the newly created resource object may not have all the required fields.
(ID-17324)
• When editing or updating a user, if you try to assign an idmManager that does not yet exist
(for example, the idmManager is missing), you will see the following error message and the
change cannot be saved. (ID-17339)
'Item User:[idmManager that doesn't exist] was not found in the repository, it may have
been deleted in another session'
You do not see this problem when creating a new user.
• Report configurations are not preserved when upgrading from 7.1 to 7.1 Update 1. Please
save the report configuration objects prior to upgrading. (ID-17363)