I'm a longtime (more than 22+ years) PowerBuilder developer. We have upgraded to PowerBuilder 2017 R2 through Appeon.
I have a question about the support for “Impersonation” using a different Windows AD System account after logging into the system. Right now we use a system account with a password to login (using MS SQL Server Native Client). Effectively, the individual users won’t have any access to any database objects. Only the system account will have access. Now, our SQL admins are implementing some changes in the process & wanted to stop using the SQL accounts (with user id & password). So, they wanted us to login to the system using Windows Authentication & then use “Impersonation” using a different Windows AD System account. This way they don’t need to give data objects access to individual users & can stop using SQL User accounts.
All the non-PB .net applications are already migrated to work this way. But, we couldn’t do that in our applications, as we couldn’t find a way to make this works with PowerBuilder 2017 R2. Is this supported by PowerBuilder?
Please note that if this is not possible, this could be the end of PowerBuilder development in our company (we’re using PowerBuilder since version 4 – since 1996). I sincerely hope for a resolution for this issue.
Thanks much for your help & support.