Here is the response I received from SAS TS.
It appears SAS does not provide must support it relates to the OS and third party drivers.
This is why The Hartford is planning to migrate from SAS within the next 4 years.
I received confirmation that these options should be supported as DSN options (which is expected). Unfortunately we do not have the authentication built into the engine options at this time. The CONOPTS is the best bet, but I haven't had a chance to test it for myself yet.
In general, the way I like to think about the authentication is that it is primarily handled outside of SAS. It is a method configured at the system level and SAS only needs to be pointed to it with the relevant options. So in short, so long as the authentication is working outside of SAS it should have no issues in SAS. However this also limits how much documentation we typically maintain since its not a SAS process.
Note that I have experienced issues trying to construct a defined DSN connection to our Snowflake private link using our DataDirect ODBC manager. We must leverage DataDirect since we have this ODBC manager and driver defined for SQL Server already. Only one odbc.ini file can be referenced.
Currently our connections can only be supported using DSN less connections, which it appears to the method that SAS mainly implemented for Snowflake.
With the cost of these connectors and the lack of true support, I will expect other companies will be abandoning SAS soon.
