Using sitedefault.yml for a SAS® Viya® 3 deployment leads to an unexpected configuration for the sas.logon.kerberos definition


When you use sitedefault.yml to automate part of your configuration in a SAS Viya deployment, you might observe duplicate entries in Consul but not in SAS® Environment Manager for the "sas.logon.kerberos" definition.

Here is an example of the duplicate entries:

config/SASLogon/sas.logon.kerberos/debug=true
config/SASLogon/sas.logon.kerberos/disableDelegationWarning=true
config/SASLogon/sas.logon.kerberos/holdOnToGSSContext=true
config/SASLogon/sas.logon.kerberos/keyTabLocation=file:///etc/xxx_http.keytab
config/SASLogon/sas.logon.kerberos/servicePrincipal=HTTP/server.customer.com@CUSTOMER.COM
config/SASLogon/sas.logon.kerberos/spn=HTTP/server.customer.com@CUSTOMER.COM
config/SASLogon/sas.logon.kerberos/stripRealmForGss=true

config/application/sas.logon.kerberos/debug=true
config/application/sas.logon.kerberos/disableDelegationWarning=true
config/application/sas.logon.kerberos/holdOnToGSSContext=true
config/application/sas.logon.kerberos/impersonate=true
config/application/sas.logon.kerberos/keyTabLocation=file:///etc/xxx_s1_http.keytab
config/application/sas.logon.kerberos/servicePrincipal=HTTP/server.customer.com@CUSTOMER.COM
config/application/sas.logon.kerberos/spn=HTTP/server.customer.com@CUSTOMER.COM
config/application/sas.logon.kerberos/stripRealmForGss=true


These duplicate entries do not have any known impact on the deployment.