Skip to main content


 

Symptoms


Trying to use Static authentication for Sql Server but, does not work.
I have security to the database but, can’t get Static to work.
We usually use Service Account but, am pursuing options for a situation and want to use Static With a UserId/password
'DENALLIXCodi' is part of a security group that has reader, writer, owner, and execute.
 

Diagnoses


When using "Static Authentication" with a SQL server service instance, you will need to specify a SQL account (such as 'sa' instead of a Domain Account 'DENALLIXCodi') and SQL will need to be configured for SQL authentication. Please see the documentation below:

http://help.k2.com/onlinehelp/k2blackpearl/userguide/current/webframe.html_ws_sql_01.html

Only 3 modes of authentication are supported in the SQL Server Service at this time:
• Static - i.e. SQL Authentication will be used. So a SQL User (like sa) will be specified here.
• Impersonation - Logged On user will be impersonated and executed in that context.
• Service Account - Authentication will be reverted to the Service Account and executed in that context.
 

Resolution

It is currently not possible to use Static Authentication and specify a Windows account (DENALLIXCodi). Perhaps using K2 Service Account Authentication would accomplish the same behavior.




 
Be the first to reply!

Reply