Welcome to the Alteryx Knowledge Base
Created/Edited -
- Failed to authenticate.
- Connection to platform was not successful.
- ConnectionError ('Failed to authenticate.') has type ConnectionError, but expected one of bytes, unicode
- Alteryx Designer
- 2021.4.2 Patch 4, 2022.1 Patch 2, and later.
- NEWER python-based Connector versions where Windows Certificate Store is utilized (MMC) (Note: Most Connectors are Python-based)
- You will need Administrator privileges to perform the steps below in this article
You will complete four Sections below
- Determine if this article applies to your Connector version
- Gather the Certificates used by the site's Log On Page
- Add the Certificates to the Microsoft Management Console (MMC)
- Re-run the Workflow
For Alteryx One - Workspace Execution
Please follow only Section 2 below and then follow the article documented here - Packaging SSL certificates for Alteryx One Workspace Execution
Section 1 -- Determine if this article applies to your Connector version
Determine if your tool version is at or above the version that starts using the Windows Certificate Store by searching for the tool page on the Community Gallery and reviewing the tool release notes. If your tool version is lower than the version that starts to use the Windows Certificate Store, please use the following article instead: https://knowledge.alteryx.com/index/s/article/Connection-Errors-with-Python-based-Connector-Tools-on-RUNhon-based-tools-1583461568264 ,
Below is an example tool release note where you will see this listed:
Section 2 -- Gather the Certificates used by the site's Log On Page
1. In a browser, go to the login page for the Data source related to the Connector Tool you are trying to use.
Salesforce Input -- https://login.salesforce.com
Microsoft Based Connector -- https://login.microsoftonline.com,
Box Tools -- https://account.box.com/login, etc)
NOTE: You will want to make sure you are on the sign-in screen, not logged in. It is recommended to use an incognito window to keep you from potentially being automatically logged in to your tenant.
a. Choose Lock > Connection is Secure
b Choose the Certificate Icon, which can appear as
OR
2. Navigate to the Details tab
3. Click on EACH of the certificate levels below and Export the certificate. Note the file names as later steps will ask for the Root, Intermediate, and Personal certificate files specifically.
Section 3 -- Add the Certificates to the Microsoft Management Console (MMC)
You will need Administrator privileges to perform the steps below.
1. Enter mmc in the Windows search bar and launch the mmc Windows app)
2. Choose File > Add/Remove Snap-in
3. Select Certificates then Add
4. Select Computer account then Next.
5. Select Local Computer then Finish.
6. Select OK.
7. Add the Root certificate.
a. Expand Certificates and Trusted Root Certification Authorities
b. Right-click Certificates and choose All Tasks > Import...
c. Select Next.
d. Import the matching certificate (Root, Intermediate, or Personal) saved in the first section of this article (you may need to choose to show all file types), then select Next
e. Select Next
f. Select Finish
8. Repeat the previous step for the
a. Intermediate Certification Authorities certificate
b. Local certificate
9. If you were adding Certificates for a Connector, you can proceed to the next step. If you were adding Certificates to work through an SSL error experienced using File > Manage Connections > Synchronize or calling an API endpoint from the Download Tool:
b. If SSL errors continue, create a PeerValidationBypass.txt file, see: Peer Validation Allow List
10. Close out of Microsoft Management Console.
Section 4 -- Re-run the Workflow
Attempt to re-run the workflow that contains the Python-based connector.