Windows Authentication with Kerberos Issue with FQDN

[aarongiesinger]

Hy Community,

We have enabled Windows authentication with Kerberos on the Alteryx Server.

When I open the gallery using the machinename (DN), no Windows login popup appears.

However, when I open the gallery with the machinename.domain.loc (FQDN), the Windows login popup does appear.

The server service is running with a domain user that has kerberos delegation rights.

Additionally, the SPN entries for all possible variants of the server are configured. In the Alteryx system settings, all 'paths' are specified with the FQDN.

Do you have any idea what else this might be related to?

Thank you in advance.

Aaron

[gawa]

@aarongiesinger 
It depends on how they specified "Hostname" in system setting. Usually it is FQDN but can be host name(machine name) only.

If you configured FQDN in system setting, your described behavior makes sense.

As far as domain user access w/ Windows auth, only host name suffices.(of course FQDN works, too)

In case SAML auth is applied, it shall be FQDN to properly issue CA certificate.

Hostname
This should be a fully qualified domain name for the machine. If a fully qualified domain is not required, a hostname is fine. The hostname or FQDN you specify will be used to build default recommendations for later URL/URI configurations.

https://help.alteryx.com/20223/en/server/configure/system-settings/environment.html#idp109798

[aarongiesinger]

@gawa

I checked the systemsettings of alteryx server and everything is configured with the fqdn. so to my opinion it should work without windows popup for username and password.

Do you have any idea to avoid the windows popup for the login?