jh1

Hi Luc,

for my requirements (at the moment) password rotation & heartbeat is sufficent but the whole feature set with also connecting to the DB with a privileged SQL-local user would make sense too in future. Currently my/your customers process is checking out the privileged user in PAM, copy the password and enter it in their sql magement studio connection window. when this process can be done completley in PAM without any copy/paste actions everybody would be happy too I guess but for our current purpose this has not the same priority as password rotation and heartbeat.

Cheers

Joachim

as we are currently switching PAM providers from connection through application server to a connection using a gateway it would complete our design when the MSSQL PAM provider could be configured with a gateway connection, too.

As of now we can use it for AD Authentication (login), PAM AD/local Windows/SSH provider but not for our ~100 MSSQL servers which also have uniquie local sysadmins per User

Would be helpful to get the function that we can also route PAM provider MSSQL connection through a gateway server too

Custom PAM provider is not an option for us, as the environment ist pretty much hardened and resticted and we cannot simply use remote powershell without interuptions