Perceptive Content requires user and password authentication against a directory service, such as LDAP or Microsoft Active Directory, a local machine, or the server platform operating system. In addition, Perceptive Content also supports authentication against a SQL table structure. Rather than storing user passwords, Perceptive Content checks to make sure the user name and password offered at sign-on identically match the user name and password stored in the external directory service.
In addition, you can configure Perceptive Content to support client validation. For example, Perceptive Content can authenticate a user based on his or her domain log on, bypassing the Perceptive Content sign-on process if the user has authenticated to the domain with a valid user ID known by the Perceptive Content Server.