Hi @ruben, welcome!
Glad to see the amount of homework you did. A good example to be followed! Looks like a very nice summary of the current (Feb 2018) status of SQL Server support, and problems people ran into - in particular if Windows Authentication is needed.
Anyways I'm a bit pressed for time righ now - so will try to answer direct questions quick and then maybe get back later if needed:
It depends on if you are:
-
a) happy to live with an SQL user defined locally on the SQL server:
it’s yes 1- SQL server user setup is needed (unless you already have one) 2- No kerberos setup shouldn’t be needed -
b) or want/need it to work with a Windows domain user account
1- I'm in doubt myself. Didn't get to the bottom of it in the Connect to SQL Server via Windows Authentication thread you linked to above. 2- yes kerberos in your linux client with Metabase server is needed
Hope that gives you the options to choose from.
Yes that's the rough steps if you want/need Windows Authentication.
Agree - better guidance/simpler setup is needed. But if anyone came up with a more clear guide I'm not aware of it. Last effort I was involved in with Windows Auth you already linked here, it's just that it ended without Connect to SQL Server via Windows Authentication - #19 by Bungle - but only a local SQL Server user "bailout", which is understandable if it suited the bill.
Hope this helps!