Oracle® Identity Manager Connector Guide for Microsoft Windows NT 4.0 Release 9.0.2 Part Number B32160-01 |
|
|
View PDF |
The following are known issues associated with this release of the connector:
If the target system and Oracle Identity Manager are on different subnets, then you cannot provision a Microsoft Windows NT 4.0 user by using Oracle Identity Manager.
The following example illustrates this limitation:
Suppose M1 is the computer on which Oracle Identity Manager is installed and M2 is the target Microsoft Windows NT 4.0 server. If you provision a Microsoft Windows NT 4.0 user through Oracle Identity Manager, then the provisioning operation fails if M1 and M2 are on different subnets.
For example, if the IP address of M1 is 192.168.6.23 and the IP address of M2 is 192.168.0.28. Then, the provisioning operation fails because the subnets, 0 and 6, are different.
However, if you put M1 on the same subnet as M2 (for example, if the IP address of M1 is 192.168.0.23 and the IP address of M2 is 192.168.0.28), then the Microsoft Windows NT 4.0 user is provisioned successfully.
The Create Folder at File Server function is rejected if the Oracle Identity Manager server and the Microsoft Windows NT 4.0 server are not in the same domain. This function works only if the computer on which Oracle Identity Manager is running and the file server computer are in the same domain, but not on the same computers. This function also works if the Oracle Identity Manager server is in a workgroup and not in a domain, and the file server is on a different domain.
There are some known response codes that have not yet been added in the Create NT User function. These codes and their descriptions are given in the following table.
Response Code | Description |
---|---|
0x8007005 | Your NT account is locked out. |
0x80070056 | The old NT account password is invalid. |
0x800708ad | The specified NT account does not exist. |
0x800708c5 | Your new password cannot be the same as any of your previous passwords. In addition, your new password must meet the password uniqueness rule set for the domain. |
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 locale 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.