SQL Server
SQL Server
SSH Authenticate with a SecureString Password and Private Key
See more SSH Examples
Demonstrates the Chilkat Ssh.AuthenticateSecPwPk method, which performs the same combined password/private-key authentication as AuthenticatePwPk but receives the username and password as SecureString objects. The third argument is the SshKey private key.
Note: The private-key path is relative to the application's current working directory. Supply the path to your own key file.
Background: This is the
SecureString form of multi-factor SSH authentication: the password is held encrypted in memory and combined with a private key for servers that require both. It is the most protective option when a deployment mandates two-factor SSH and you also want to minimize plaintext credential exposure in the process.Chilkat SQL Server Downloads
-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
DECLARE @hr int
DECLARE @iTmp0 int
DECLARE @sTmp0 nvarchar(4000)
DECLARE @success int
SELECT @success = 0
-- Demonstrates the Ssh.AuthenticateSecPwPk method, which authenticates using SecureString login
-- and password objects together with a private key. The 1st argument is the username, the 2nd
-- is the password, and the 3rd is an SshKey private key.
DECLARE @ssh int
EXEC @hr = sp_OACreate 'Chilkat.Ssh', @ssh OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
-- Connect to the SSH server. Port 22 is the usual SSH port.
DECLARE @sshPort int
SELECT @sshPort = 22
EXEC sp_OAMethod @ssh, 'Connect', @success OUT, 'ssh.example.com', @sshPort
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @ssh, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @ssh
RETURN
END
-- Normally you would not hard-code the password in source. You should instead obtain it
-- from an interactive prompt, environment variable, or a secrets vault.
DECLARE @password nvarchar(4000)
SELECT @password = 'mySshPassword'
-- Load the SSH private key. LoadText reads the file's text, which is then imported.
DECLARE @privKey int
EXEC @hr = sp_OACreate 'Chilkat.SshKey', @privKey OUT
DECLARE @keyStr nvarchar(4000)
EXEC sp_OAMethod @privKey, 'LoadText', @keyStr OUT, 'qa_data/id_rsa'
EXEC sp_OAGetProperty @privKey, 'LastMethodSuccess', @iTmp0 OUT
IF @iTmp0 = 0
BEGIN
EXEC sp_OAGetProperty @privKey, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @ssh
EXEC @hr = sp_OADestroy @privKey
RETURN
END
EXEC sp_OAMethod @privKey, 'FromOpenSshPrivateKey', @success OUT, @keyStr
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @privKey, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @ssh
EXEC @hr = sp_OADestroy @privKey
RETURN
END
-- Place the login and password into SecureString objects.
DECLARE @secureLogin int
EXEC @hr = sp_OACreate 'Chilkat.SecureString', @secureLogin OUT
EXEC sp_OAMethod @secureLogin, 'Append', @success OUT, 'mySshLogin'
DECLARE @securePassword int
EXEC @hr = sp_OACreate 'Chilkat.SecureString', @securePassword OUT
EXEC sp_OAMethod @securePassword, 'Append', @success OUT, @password
EXEC sp_OAMethod @ssh, 'AuthenticateSecPwPk', @success OUT, @secureLogin, @securePassword, @privKey
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @ssh, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @ssh
EXEC @hr = sp_OADestroy @privKey
EXEC @hr = sp_OADestroy @secureLogin
EXEC @hr = sp_OADestroy @securePassword
RETURN
END
PRINT 'Authenticated.'
EXEC sp_OAMethod @ssh, 'Disconnect', NULL
EXEC @hr = sp_OADestroy @ssh
EXEC @hr = sp_OADestroy @privKey
EXEC @hr = sp_OADestroy @secureLogin
EXEC @hr = sp_OADestroy @securePassword
END
GO