|
The
following limitations existed prior to the 4.0 Controlled Release and have
not been resolved:
·
You must select a workflow when mapping the View Service Membership
event in a Service Role. The workflow is ignored but is needed to
view users in the service.
· Modifying a user through the use
of a Web Service does not use the view associated with a Modify
event. Instead, it uses the Add User view.
· Create User will not be rolled back
in OVSI when the user is added in the resource if the entitlements are not
created successfully for the associated user.
·
Search response time within OVSI may be negatively impacted if a
large number of values are entered for the context attribute in a service.
·
When defining a parent Service Role, you may
assign multiple workflows for a single event for the purposes of passing
those workflows down to other child Service Roles. However, if you attempt to add, modify,
or delete a user that references a context with multiple templates assigned
to an event, the action will fail.
The
following limitations existed in the 4.0 Controlled Release and have not
been resolved:
·
3.3.1 Workflow configurations imported to 4.0 will not operate
properly.
·
The following attributes should not be imported to avoid issues:
o
<Resource>_ENTITLEMENTS
o
<Resource>_KEY
o
SIAdminRole
o
SIService
·
Some pages contain multiple vertical scroll bars.
·
Service Reconciliation jobs do not appear in the Reconciliation Job
List.
·
When modifying an Administrator, there is no “Add” button to enter
context values. As the “mouse over” instruction indicates, press the
“Enter” key to add a value.
· HP Open View Select Identity
does not recover all tasks in process after a catastrophic failure (system
or database crash):
o
After a restart or database loss, some
requests will not resume processing and complete.
o
When the database goes off-line the messages
are still being retrieved from the JMS queues and ignored. The requests affected
by these missed messages remain in the pending state forever. In most cases
there is no UI screen to re-process them.
These losses should be limited to less than
ten (10) requests and the recovery procedure is documented in the
Administrator Guide.
·
Not all drop-down lists are sorted.
· Unconstrained context attributes
do not always return values when context is searched:
o
Move User with a wild card context on the
Service.
o
Creating specific Admin with specific
Context.
Note: To ensure
proper results, use attribute constraints to limit wild card scope.
·
User Names should not be created with double quotes (“).
·
If Service Reconciliation is not done after adding or removing
resources or fixed entitlements, users will not display the current
resource and entitlement information correctly even after the modify action
is done
·
The HP OpenView Select Identity Installer still requires that you
set the “JTA Timeout Seconds = 300” (set under domain
-->Services -->JTA in the WebLogic console)
·
The “Results per Page” dropdown used to select the number of items
displayed is working correctly on all screens except User Import ->
Service Assignment.
The
following problems and limitations exist in the 4.01.000 Commercial
Release:
·
The Resource Reconciliation
Report will not run using the Run
Now or Add and Run Now
buttons. This report should be scheduled because it can take a long time to
generate and should be emailed rather than placed on the server. These
buttons will be removed in a future patch release.
·
Approver comments for migrated requests cannot be viewed.
·
In Workflow Approval blocks the Create
work flow approver task must
come before the Notify approvers
task. In 3.3.1 the order did not matter. Default workflows are correct,
but manual update of migrated workflows is required.
·
When scheduling reconciliation or bulk tasks, use 24 hours instead
of 1 day if creating a job to run daily. Otherwise, the task will run at
midnight instead of the scheduled time.
·
Using the Resource “Edit” button to open the Attribute Mapper for
database connectors opens a new window with an error. On the new window,
select the connector, enter the resource access information, and click
“Connect”. The Attribute Mapper page then correctly displays.
·
When generating the User Configuration Detail Report, a context must be selected.
·
Profile attributes must be constrained at the Attribute level
instead of the Service level or the constrained values are not enforced
when modifying the attribute from the User Profile.
·
When importing a changed
Workflow Application Definition file, the modifications aren't visible in
other members of the cluster until a restart is performed.
·
If SI is doing its’ own authentication, only the standard Password
attribute should be used. 2 way password attributes can be used as long as
SI is not authenticating the user.
·
CSV Report format is not available for the User Configuration Detail
Report.
·
Specific Service Admins can only manage the users on their specific
service. Therefore, a Specific Service Admin cannot add their managed
service to a new user.
·
When an Admin user is added to the specific Service he manages, the
Admin role is lost. After adding the user to the business service, modify
the administrators’ role to a temporary role, and then modify the
administrator back to the original administrator role.
·
Approval cannot be used when moving an Admin User on all Services.
·
If all components are not completely installed during Installation,
uninstall will display the error “Error During Uninstall”. This simply
means that the uninstall program could not find all components to
uninstall.
·
A problem exists when adding service to an existing user. If the
administrator does not have the Add
New User role, then Subscribe to
Service fails with error "Requestor not authorized for current
operation".
·
JMS expired message redirection
function is not supported in WebSphere. When the system is working on the
heavy workload, some low priority messages might not be picked up in a
short time.
·
WebSphere platform customers please note: It is possible that there may be some
conflict between some of the connectors released with the 4.01.000 version
of SI with any of the connectors released with SI v4.0 or SI v3.3.1. This
is due to potential class loading conflicts on WebSphere which may result
in incorrect behavior at deployment time or runtime. If you experience
these problems please contact HP Support for help to work around them.
·
Due to time constraints, the following
instructions regarding the deployment of online help files on WebSphere has
not been added to the installation guide.
The help file is a .war (Web Application Archive) file,
located in the same directory as the websphere_lmz.ear file deployed to
activate Select Identity. This is the only .war file in that director. The
precise name of this file varies according to the localized version of
Select Identity that you are using.
To deploy this file, perform the following steps:
1. Locate the OVSI .war file, which is stored on the HP
OpenView Select Identity product CD, in the application directory with the
websphere_lmz.ear application file.
2. Copy the .war file into the <OVSI_INSTALL_DIR>/deploy
directory.
3. Use the instructions provided in Deploying Select Identity
on the installation guide (Chapter5, Installing Select Identity on IBM WebSphere,
Page 124), to locate and deploy the help files in the same way as you did
for websphere_lmz.ear. On this occasion, however, you must deploy the help
files as a Web Application module, by first navigating to Applications>
Install New Application. Please make sure that the Context Root
should be set as the name of the help war file without the “.war” file
type. For example, for the ovsil10n_help_enUS.war, the relative
Context Root should be ovsil10n_help_en_US.
·
The following Sensitive Attributes imitations exist:
o
The sensitivity of UserIDAndDomainName and PrimaryAcctValue are not
incorporated in this release. Values for above fields will not be encrypted
if they are unmapped and/or sensitive.
o
Bulk-Add requests are grouped into sub-batches before processing. If
a SPML request within a bulk-add sub-batch fails with a decryption failure
the corresponding sub-batch is not processed.
o
If an attribute within a bulk-add request is not found in SI, the
whole batch is not processed.
o
If the encrypted XML value contains escape characters like
"<" ">" the XML parser will throw an exception
unless it is enclosed in a CDATA section.
|