I have a case where I have installed a new KNIME Server instance (4.13) on a Windows Server machine (2019 Server).
The Server and Executor run as a Windows system process. Everything runs fine.
However, the business wants to use Windows Authentication when connecting to their SQL Server database (not SQL Server Credentials). They have provided me with Windows user credentials that have access to the SQL Server Database.
So I need to get the KNIME Executor process to run as this Windows user. However, when I change the executor to run as this user, then the executor fails to spin up the workflow on Execute.
I believe the new Windows user I have been provided with needs more rights to access run the KNIME executor - but I am not sure what rights it needs or how to add these. Minimal rights would be ideal.
Does anyone have any pointers on this?
Many thanks for your assistance with this. The closest existing post I could see related to this was the following - but it doesn’t quite cover it.
Configure KE to run as this new service principal that you’ve been given (Services> KNIME Executor> Properties> Log on> configure user/pass);
Configure the file permissions on the knime_executor and executor_workspace directories so that the new service principal account has full access to be able to read/write in those areas. I think this is the step you had an issue with.
At that point, you should be able to start up the executor, running as the new service principal, and shouldn’t see any logs. If it doesn’t work for you, though, please reach out to us at firstname.lastname@example.org so we can discuss particulars in detail, obtain logs, etc.