I’m trying to setup a Servoy Database connection with JDBC driver and with Integrated Security which allows you to connect to the database using your Windows Account.
But when I try to save it I get the following error:
This driver is not configured for Integrated Authentication
Here are my details:
Server name: aName
User Name: blank
Password: blank
URL: jdbc:sqlserver://localhost:1433;DatabaseName=dbName;SelectMethod=cursor;integratedSecurity=true;
Driver: com.microsoft.sqlserver.jdbc.SQLServerDriver
Why not using SQL Security. What is the advantage when using Integrated Security?
Just make a user /password special for Servoy with datareader / datawriter permissions (maybe even db-owner)
The password will be encrypted in the Servoy properties file, so no security problem
Just make sure that you have Mix Security Mode installed on your server.
I think you make it more difficult than necessary, but perhaps you have a special reason for this?
martinh:
but perhaps you have a special reason for this?
Yes. In my company we use the same logins and passwords as Windows domain accounts. And, the most important reason, our Windows passwords are changed every 3 month. So every 3 month we need to manually change our Servoy passwords
All actions from Servoy Application Server are using the user/pass that is defined in the database server settings.
If you use Mixed Security and use 1 single SQL security user/passwd for access Servoy AS to SQL Server then you don’t have the problem of changing Windows passwords if you say that this SQL account (within SQL-Server) doesn’t require password change every x days.
But maybe one of the Servoy guys (Rob) can tell you if it is possible to use integrated security like you want it.
But since Integrated Security = Windows and Servoy uses JDBC (and not ODBC) I’m afraid it will not work like that.
The JDBC driver is limited and will only use possibilities that are available on all platforms and it will not use Windows or SQL Server specific functionality.
So I think it will not work, but maybe you have some luck and there will be a surprise
I totally forgot that the application server needs only one login and password to access the database, and users login/pwd are managed by Servoy!
So in fact for this to work, Servoy should provide another option (specific for Windows), or you need a plugin which provides that.
Foobrother:
I totally forgot that the application server needs only one login and password to access the database, and users login/pwd are managed by Servoy!
I still would like to know why I’m getting this error. Normally integrated security should work for the account used by Servoy Application Server to deal with SQL Server?!
I have checked that the account running Servoy Service is present in SQL Server logins (windows login) and has enough rights.
Sorry to jump in on your thread, but I have a question related to this. I was told by Servoy sales that you can now have individual user sessions into the SQL DB from Servoy. This is somewhat critical to our security model. Can you confirm this is possible? Do you know where setting this type of access up is documented?
Sorry to jump in on your thread, but I have a question related to this. I was told by Servoy sales that you can now have individual user sessions into the SQL DB from Servoy. This is somewhat critical to our security model. Can you confirm this is possible? Do you know where setting this type of access up is documented?
Thanks,
Lee
I’m not sure, but normally you have only one session which is for the only user of the database (configured when you create your database server in developer). Then each user in a solution can work on the database using transactions.
By the way, could someone answer this question: Normally integrated security should work for the account used by Servoy Application Server to deal with SQL Server?!