ILLiad previously used the name ILLiadFieldName as it was entered in HTTP HEADERS; however, as of v9.1 ILLiad now uses the name in the HTTP HEADERS (RAW). The ILLiad 9.1 update script will copy the value from the RemoteAuthUserVariable customization key, strip the initial "HTTP_prefix, and place it in the new RemoteAuthValidations table.
When setting up RemoteAuth new, the value for the username should be identified by the corresponding header value in the HTTP Headers (RAW) section of getbuildinfo shown in GetBuildInfo. This is typically the HTTP header value without the "HTTP_"prefix.
The GetBuildInfoShowDetailed Customization Key controls whether HTTP Headers and Server Variables are displayed when using the GetBuildInfo in the Web DLL. If set to Yes, the HTTP headers will display once and then toggle to change the key's value to no. Note: This is a system-level setting and should not be changed by sites.
Go to https://site.illiad.atlas-sys.com/illiad/illiad.dll?getbuildinfo to locate the HTTP Headers (RAW), then locate the ILLiadFieldName. See example below:
Below, the username being imported is jsmith12345. This is shown in the HTTP_HTTP_EZILL_VALUE under HTTP Headers and HTTP_EZILL_VALUE from GetBuildInfo. The mapping should be added to the RemoteAuthValidation table using the HTTP_EZILL_VALUE as shown under HTTP Headers (RAW).
HTTP_USER_AGENT:Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.120 Safari/537.36
HTTP Headers (RAW)
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.120 Safari/537.36
Using Server Variables Instead of HTTP Headers
Since it's more secure to retrieve the web request's special fields from the IIS server variables than from the HTTP headers, as of ILLiad v9.1.2, by default ILLiad will now only consider server variables when retrieving the values of RemoteFieldName from the RemoteAuthValidation table. Legacy behavior is still supported, where ILLiad will consider both server variables and HTTP headers when mapping RemoteAuth fields. The UseLegacyRemoteAuthHandling Customization key was added to retrieve RemoteAuth fields from HTTP headers and server variables in support of the legacy behavior. This key is set to No for new installations but will be set to Yes by default for all sites upgrading to v9.1.2, in order to not break existing RemoteAuth configurations.