wt.org.electronicIdentity.engines
Class LDAPFDACompliantSignatureEngine

java.lang.Object
  wt.org.electronicIdentity.engines.LDAPFDACompliantSignatureEngine

All Implemented Interfaces:

SignatureEngine

public class LDAPFDACompliantSignatureEngine
extends Object
implements SignatureEngine

A signature engine which requires a username and password to be supplied. It verifies that the username and password belong to the currently logged in user. This signature engine is in compliance with FDA rule 21 CFR Part 11 section 11.200 which requires at least two distinct identification components for a signing. An LDAP-based directory service is used for authentication.

Note: the electronic signature feature is only supported when user authentication is done using an LDAP-based directory service. If a site is using a flat file or some other means of authentication, then they must provide their own signature engine implementation.

The wt.federation.org.directoryService property lists the names of the Info*Engine JNDI adapters that windchill uses to query one or more LDAP-based directory services for principals. The same services will be used for user authentication of electronic signatures. The following property is only needed in the wt.properties file if the LDAP-based directory service used for authentication is not one of the services identified by the wt.federation.org.directoryServices property.

wt.org.electronicIdentity.authenticationService: The name of the Info*Engine JNDI adapter that the signature engine will use to access the LDAP-based directory service for user authentication.

Supported API: true

Extendable: true

See Also:

SignatureEngine

Method Summary

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait