Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Talend Cloud AWS EU Scheduled Outage: Starting Tues 26 May 21:00 CEST with expected completion Wed 27 May 01:00 CEST
cancel
Showing results for 
Search instead for 
Did you mean: 
SHARMA-G
Contributor III
Contributor III

Issue with Key Pair Authentication for Snowflake in Qlik Replicate (May 2024 Version)

Hi all, I’m currently transitioning an existing Snowflake user setup in Qlik Replicate from password-based authentication to key pair authentication.

I’ve followed Qlik’s official documentation, but ran into an issue after upgrading to the May 2024 version (previously I was on an older build). I’ve attached a screenshot of the new screen/interface for reference.

Here’s my setup:

I’ve generated .p8 and .pub keys

The public key (.pub) is assigned to the Snowflake user

The private key (.p8) is stored locally

I'm entering the following in the connection config:

username = abc

privateKeyFile = X:\FILENAME.p8

privateKeyPassphrase = [passphrase created during key generation]

Despite providing all the required details, I receive the error: "failed to decrypt password".

Has anyone run into this issue after upgrading? Could it be related to the format of the key file or compatibility with the new version?

Labels (1)
11 Replies
SHARMA-G
Contributor III
Contributor III
Author

Just a further question on this, my qlik server is running in ec2 instnace and replication is running with password. I have moved .p8 keys over to ec2 instnace /opt/keys....p8 and there is corrosponding user in snowflake with .pub keys. so to move exisitng user to this new user do i have to stop services first by stoping does is mean :

stop qlik server using 'systemctl restart'

or

Just the stop/resume task in qlik (I am using 2024.5) Qlik version? 

john_wang
Support
Support

Hello @SHARMA-G ,

I may not have fully understood your question, but if you’re asking whether a service restart or task restart is required after changing the authentication in the endpoint, the answer is no — a full service restart is not needed. Simply re-running the task will be sufficient.

Thanks,

John.

 

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!