Oracle® Identity Manager Connector Guide for SAP Enterprise Portal Release 9.0.3 Part Number B32370-01 |
|
|
View PDF |
The following are known issues associated with this release of the connector:
The configuration details of the SAP Enterprise Portal database are in plaintext in the sapum.properties
file, the location of which is available in the IT resource definition. 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.
After the connector is deployed, the first task that can be performed is lookup reconciliation. If the size of the lookup field that is being reconciled is more than 100, then 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 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.
During lookup fields reconciliation, the Role field is reconciled in English. This is because SAP Enterprise Portal does not allow you to specify the role ID in non-English languages, although a non-English language can be used for the role name.
The connector does not support Secure Network Communication (SNC) or Secure Sockets Layer (SSL).
Some Asian languages use multibyte character sets. If the character limit for the fields in the target system is specified in bytes, then the number of Asian-language characters that you can enter in a particular field may be less than the number of English-language characters that you can enter in the same field. The following example illustrates this limitation:
Suppose you can enter 50 characters of English in the User Last Name field of the target system. If you were using the Japanese language and if the character limit for the target system fields were specified in bytes, then you would not be able to enter more than 25 characters in the same field.