When configuring a remote LDAP server on FortiAuthenticator, server type templates (e.g., Microsoft Active Directory, OpenLDAP) are used to simplify the setup process. These templates contain pre-defined schema information specific to the selected LDAP server type. By choosing a template, FortiAuthenticator automatically populates the query element fields, such as the Username attribute, User object class, Group object class, and Group member attribute, with the standard values used by that directory service. This saves the administrator from having to manually look up and enter these schema-specific attributes.

A. They autopopulate the simple and regular bind settings.

Bind settings require specific administrator credentials (username and password) to connect to the LDAP server, which a generic template cannot provide.

B. They automatically set the LDAP user auto provisioning settings.

User auto-provisioning is a separate configuration option that determines if and how users are created on FortiAuthenticator; it is not controlled by the server type template.

D. They define the connection security and domain authentication settings for each LDAP server you integrate with.

Connection security (e.g., LDAPS, STARTTLS) and server IP/FQDN are environment-specific settings that must be configured manually for each individual server connection.

1. FortiAuthenticator 6.4 Administration Guide

Page 111

Section: "Authentication > Remote Auth. Servers > LDAP > Create New".

The guide states: "The Server type drop-down list allows you to select a template for the LDAP server you are connecting to. The template will automatically populate the query element fields with the appropriate defined attribute and class values." This directly supports the correct answer (C) and refutes the other options. The fields populated are listed as Username attribute

User object class

Group object class

etc.