Oracle® Identity Manager Connector Guide for SAP Enterprise Portal Release 9.0.1 Part Number B31136-01 |
|
|
View PDF |
The following are known issues associated with this release of the connector:
The configuration details of the SAP-EP database are in plaintext in the SAPUM.properties
file, the location of which is available in the IT Resource. This poses a security threat.
The connector uses the UME APIs that communicate directly with the data sources on the target systems instead of going through the SAP system. These data sources could be SAP Base, the Database, or LDAP.
For certain functionality, such as Portal Role lookups, a SAP Enterprise Portal plug-in must be installed on the SAP Enterprise Portal server. Therefore, there is a dependency on the availability of the SAP Enterprise Portal server and deployment overhead.
During provisioning, if values for the Valid From
and Valid To
date fields are not specified, then the default date value of 1970-01-01
is used.
Immediately after the connector is deployed, the first task that can be performed is to only lookup reconciliation. If the size of the lookup field that is being reconciled is more than 100, an exception may be thrown. To resolve this issue, you must change the size of the column in the LKV table by running the following commands on the database:
ALTER TABLE LKV MODIFY (LKV_ENCODED VARCHAR2(300 BYTE));
ALTER TABLE LKV MODIFY (LKV_DECODED VARCHAR2(300 BYTE));
Suppose a user is created in SAP Enterprise Portal and then locked. If this user is reconciled for the first time, then the user might not get locked because the linking in Oracle Identity Manager takes place in an asynchronous manner. If the same user is reconciled for the second time, then the user gets locked.