Hi Everyone,
Recently Snowflake started using the MFA to login the snowflake connection, How we can Ignore this MFA connection in In Database Connection for Input, I need to schedule this workflow in Alteryx server, So every time i will get the notification to approve. is there any other alternative way to do this. Currently we are using the ver 2022.1 version.
Have a read of this article - https://community.alteryx.com/t5/Engine-Works/Impact-of-Snowflake-s-MFA-by-Default-for-New-Accounts-...
You may struggle on the version of Alteryx you're on though..
@davidskaife : Can you tell us now which version we need to use to reslove this issue.
You should be able to do it using the version you're on, i think, however 2022.1 is over a year out of support so any issues you encounter may have already been fixed in a newer version
your problem is not Alteryx --- your problem is that you have not figured out how you are avoiding Snowflake MFA for service accounts. You can use use PATs or you can use JWT/Key Pair auth. See:
https://docs.snowflake.com/en/user-guide/programmatic-access-tokens
For users you will use externalbrowser to connect - I have written on this numerous times. This will not work on Server but is efficient on Designer where your user is connecting.
I strongly recommend that you use JWT (key/pair) auth for all Snowflake service accounts (Alteryx or otherwise). If you are having issues - hire a Snowflake consultant. I believe @alexnajm can help you out.
Hi @apathetichell , now my snowflake team is Providing the service user with private key and passphrase. I am using the Alteryx 2022.1 version, where i need add private key and passpharse in this version.
I can see only below
once you have your private key you can start with step 3... you also much associate the public key with a user in Snowflake.
Hi, you mention that this doesn't work on Server, is there a workaround for this? Are we no longer able to use service accounts on server?
@akasubi --- hey there is a a good deal of nuance here. externalbrowser/saml auth will (may) not work on server. That is because an Alteryx server is a standalone server in your companies infra. When it opens a browser --- it opens a browser on the server --- vs on your local machine. It does not have access to the session information needed by the ODBC driver to establish that connection locally from your machine to Snowflake as you. the Snowflake OAUTH integration is a potential work around but that would require some substantial work by Alteryx to build in that integration. I do not believe it exists.
This is irrelevant to username/password phase out. This is just how things work. The private key/passphrase should work on Server. As long as the server has access to the private key file.
User | Count |
---|---|
60 | |
24 | |
24 | |
21 | |
21 |