Matthew Kakde
New Member
- Joined
- Feb 27, 2021
- Messages
- 1
- Office Version
- 2019
- Platform
- Windows
Hello everyone,
I have an Excel application (like an end user computing app) used by employees to communicate with a remote database through ODBC calls.
The ConnectionString use a generic account and a password stored in a third-party file, when users open the Excel tool the connection is automatically refreshed.
The thing is, mainly for auditability purposes, I would like to stop using a generic account for everyone and make them using their own account to use the Excel application and pulling or pushing data from/to the database.
But I have no ideas how to to that.
Is Integrated Windows Authentication a solution?
How to manage a unique user ID/password by user?
How to manage the passwords, where to store them, will users need to enter each time their password to use the Excel too?
Hope you'll have some advices !
Thanks
I have an Excel application (like an end user computing app) used by employees to communicate with a remote database through ODBC calls.
The ConnectionString use a generic account and a password stored in a third-party file, when users open the Excel tool the connection is automatically refreshed.
The thing is, mainly for auditability purposes, I would like to stop using a generic account for everyone and make them using their own account to use the Excel application and pulling or pushing data from/to the database.
But I have no ideas how to to that.
Is Integrated Windows Authentication a solution?
How to manage a unique user ID/password by user?
How to manage the passwords, where to store them, will users need to enter each time their password to use the Excel too?
Hope you'll have some advices !
Thanks
