The following User-Agent mappings are supplied with Forefront TMG: No. Forefront TMG supports forms for forms-based authentication that are written in the following formats: The types of authentication that are supported in User-Agent mappings include forms-based authentication using forms written in a specific format and Basic authentication. A User-Agent mapping whose UserAgent property is set to a string that begins and ends with a wildcard character applies to any User-Agent header that contains the substring between the wildcard characters. A User-Agent mapping whose UserAgent property is set to a wildcard character (*) applies to all User-Agent headers. The User-Agent headers to which a User-Agent mapping applies are specified by the UserAgent property, which holds a string that may contain wildcard characters (*). When a Web listener is configured to use forms-based authentication, Forefront TMG uses the User-Agent header in Web requests and the User-Agent mappings configured in the array to ascertain whether forms-based authentication can be performed and to determine the specific form that should be provided for forms-based authentication. Servers use the User-Agent header in a request to return a response that is suited to the Web browser that sent the request. Web browsers include a User-Agent header in Web requests to identify themselves to servers. Each FPCUserAgentMapping object represents a mapping of User-Agent headers to a type of authentication. The FPCUserAgentMappings collection contains an ordered set of all the FPCUserAgentMapping objects defined in a Forefront TMG array.