Authentication tab

• None — No authentication method will be used.
• Standard — Uses Active Directory or an LDAP server to authenticate users. After you select this option, configure the Standard Authentication and User Info Lookup settings.
• NetWare — Uses NetWare authentication. After you select this option, configure the NetWare Authentication settings.
• CustomPlugin — Administrator defines prompts for authentication for a custom application. After you select this option, configure the Plug-in Authentication settings.

• Against the Active Directory domain which the AutoStore server is a member
• Against the local user database of a standalone AutoStore server (workgroup environment)
• Against another LDAP server

Choose the correct option for your authentication environment:

• Windows Bind — This option is selected by default. If authentication occurs within the same Active Directory domain, the entry for Server or LDAP Path can be omitted. If authenticated against the local user database, the LDAP path should contain WinNT://autostore_server_NetBIOS_name .
• Simple Bind —This option is used for third party LDAP servers. The full LDAP path is required in the format LDAP://ldap_server,port . Check with your system administrator if you are uncertain about what path to use. These are the default LDAP ports:
  • Standard LDAP: 389
  • Active Directory Global Catalog: 3268
  • LDAP over SSL: 636
  • Active Directory Global Catalog over SSL: 3269

For either Simple Bind or Windows Bind, you can select the following options:

• Fast Bind — Select this check box to have the Active Directory or LDAP server return a limited set of user attributes to the workflow. If you do not select this check box, all user attributes are returned to the workflow server.
• Use SSL — Select this check box to encrypt communications between the workflow server and the Active Directory or LDAP server. If you do not select this check box, the connection will not be encrypted.  To use this option, you must have a server certificate for the ADAM service. If the LDAP server is in a different domain from the workflow server, enter the server name and port number (that is, LDAP://server_name,port ). Click Test to verify that the user name created on the server authenticates successfully.
• Server Bind — If this option is disabled, the Active Directory or LDAP server will attempt to connect to the DNS server in order to resolve the IP address of the Workflow server.

  Refer to the Microsoft web site for more information about setting the LDAP bind options.

• NDS Tree — Enter the default NDS tree.
• NDS Context — Enter the default NDS context.

If the device is configured to use an authentication server with the authentication type being NDS, then the provided credentials will be used by workflow server. If the authentication type of the device is other than NDS, then in addition to the workflow server logon screen, the device authentication screen is displayed to the user.

• Snap-In path — This is the path to the compiled Snap-In (.NET assembly) that contains the code to respond to form and field events. You can click the browse button (...) to locate a .NET assembly file containing an existing Snap-In.
• Source path — This is the path to the source code of the Snap-In created by the built-in Snap-In editor. You can use this option to compile a source file on startup instead of using the Snap-In path for a compiled assembly.
• Create/Edit Snap-In — Click this button to create or edit a Snap-in DLL. A sample custom script is available with this component. For details about the code editor window and the object model, click the Help button in the code editor to refer to the HP OXPd Capture Component Snap-in Documentation.

For information about specifying the LDAP server settings, see LDAP Lookup Settings Dialog Box.