If Native Directory is not configured for custom authentication, do not use Native Directory users to test custom authentication.
Note: | It is your responsibility to identify and correct any issues with the custom authentication module. Oracle assumes that your custom module works flawlessly to map a user from the user directory used by the custom module to a user on a custom authentication-enabled user directory available in EPM System search order. |
To test your deployment, log in to EPM System using user credentials from the user directory, for example, an RSA SecurID infrastructure, used by the custom module. These credentials may be different from the EPM System credentials.
Your implementation is considered successful if EPM System products allow you to access their resources. An error indicating that the user was not found is not always an indicator of an unsuccessful implementation. In such cases, verify that the credentials that you entered are present in the custom user store and that a matching user is present in one of the custom authentication-enabled user directories in EPM System search order.