Error: Failed to authenticate SharePoint Files

Hi there,

I am trying to authenticate myself within the SharePoint Files Input tool via "Profivde Authentication Information". The reason I use this way is that I want to schedule this on the server.

When I look at the XML I notice that the client_id, tenant_id, and client secret are blank even though I filled it out. I am assuming this is something that needs a patch?

Workflow

Connectors

Server

Bug

Sharepoint

Accepted answers

All comments

robertditonno

I am using "service principal (app-only authentication)" due to this being needed in order to schedule on server

FlorianC

Hi @robertditonno,

The configuration of the SharePoint Files tools should indeed be stored as encrypted values in the XML Alteryx workflow file as can be seen below.

<Configuration>
          <ClientId>301000000D08C9DDF0115D1118C7A00C04FC297EB010000007B08E066C4F07742934555717058A29B0000000008000000500057004400000003660000C0000000100000002272CF8C7103EA6C2D3C2F8CEE1A80720000000004800000A0000000100000005466053DB39A5A353C8E6AAB44B8C98B8802000011612C3218AE1F64C81EFFF2657AB46B1DFFCB5B389353B0C637EF849417FF6DD26E3F6786E0633EC1DCD831051F0B7FBB2A4292389A71D497579E09A869AF85059C3CC99A8F4361C3702EA3419BBD42B3C41B9869110BFA4BA65C265B71BDDF85CDAA3837B3E95021688C03D48C60858052CE2C59020342C42404D03753C34133D67D077969A8C6A70FCD4FBABE12689412FD2AE7B11B87E50647E076994EB4D9AE0C03349A2FAE7BAC227B8D988BAE985A0555C8E71844731C5FCE7E31DD70A098EC9B8DD5C696001921544703D4281316A6C8AE98B7A25426403147E2CD058BEBAEC6A5F72C73F89F6A4959D6CDAECBD4B4DAC1E458A994651C0B0A41141944346C84BB7CFA5A83A77980B36931955767448E3E19359E863F9AF60A384EF52DA1232EA5272A96D613D31A8BBFAB4F34643A4DCFD74597FF190903774E33F01BA44C379AA6CDFB448FC464A24965D85DE7AEEE919E9763EE6B785E7A3AE7FD8D120CD95B03B35FB2C1F1C3459316EAD977B3F9958A3C6BD92A1B23D4583EAFE0C53A8C483B361DD623A442ED27847B1AE45AE709422B98C9415698EA12BAE83903C5F3618F1E8C3A212BF0242B83B6120E0D43AE0560DA00E4AEB3A790CBCB6749381AE1227698EAA4CB0F8F63BC20DDCF7C02245EBA64F9D183969232444F5577265410E03DB6C2F0925A1C5FF4D6FAA87FD62D13292ECD1703B1CDE3F9CCAB02E18270795FB770384DA46766D52F81FD4900816BF21026F27540F1C1AC1F7E516B6EA00D361969DB0BD59609317B2A4BD335AA31DD33BE8B9D84B16E279056D99D7295B6517007A54DD7014C5B65972A7585E49573E41454DE5A3BDAF677236151720D079D978F49789B13013AD22FC9E56607883513AEF7ECC26DCAEE402CD612E93A09660C140000003798C6905FABF82E80CBA60F284259A28330CDFD</ClientId>
          <TenantId>301000000D08C9DDF0115D1118C7A00C04FC297EB010000007B08E066C4F07742934555717058A29B0000000008000000500057004400000003660000C000000010000000D1CF9256B84B4C37CD1444AED5FEB18D0000000004800000A0000000100000004EF3C05D87BC3C3696CC406903CB11FE880200008BEC56C813D3C80D30F1BE9AD6E0BD4A116D6F9D8E9FF44BD4D884947AC44FC5E9BB71C0A4D87428A1CDDF771E9CA103106B92F4626F6D6E945C53F0909CAC7D8FFCD7F2780840F3481E0E290A5FA067B81073C545D6D215CF3412D001096E7905BDEC8259C38C714E4313458A3E5F88E855B58CA2127CCC9EFF76EABDC8C9890334A4322586F0A67177276AB284E66E16152AF3E5AD95C45EDF247969B16CFA620286CEBFA7A21B8CA44D1A023E0C2658B503E62E64D6639FECD83FB9AD447DB29D55C943E8D20810048CF89811CCCAFFC6D6419BECD33F7F2B72FAB9EB4E9AFC02031B1CA91840B343F9F8574C5CB5C223A2F9E23925602B4629C0C59347B471D00EDC13FEF49EA023ADB7A92F9F90FCEF89AB5C8E4092E5BA357A52A98E0043846646A718E49CB6BF5395698D79F6E3E8FEB92ACA494C9ABA03E33B7B1E022CAB7641A4FCBA33B57CC707FE0CB67A057D95E31674531282A31BB32A006A513C665EB5466C1F604A77479F50BE65BE4DB862F0DCA556546B915B8DFE2CAE63816C198FF7E556F789F71340C1EBE9F31F75127F3B1E4352E77C42479BD8D15579B80A697E2C47B8CBF394B30E4579F97DD245DC13C017DB9EB3A412F0ABE9F9E38650D0C828F87AC0AE80AE109244D6AA12BEE9F71A8AE2CB1AE783797032B5BA1B022882B91A47C4741D08CE57EDBCDEC168BE51958CF8FAF5EF5FAB1C741ADE6B60DD065F75F94BB63E7D5AC0B15490F9D9FE5005A6D2B82DFEA7214BDA0E377EE45758A76CCFC05EDE012F541A77791576DA1D52C51755D48946A37A53B2F181E162C62B6381D2689EC64D6BE12D61833638C838A56C499F0C020AA84DEB2E2F21E01A44EA457EFCC7344C5A31CEBCF2635FC773F0F5FB6F5339143547E85F1970CE7EA1970114000000D763D78C8EDFE3C16070396861F0EF58F927564A</TenantId>
          <ClientSecret>301000000D08C9DDF0115D1118C7A00C04FC297EB010000007B08E066C4F07742934555717058A29B0000000008000000500057004400000003660000C0000000100000008903CC073D08340359D704766A374CCE0000000004800000A000000010000000135ECD5B3A680E2DE2C389D61970114E880200005A014249737822D9D7F318CB0AF3939BFD47D9A50D1719171CDD1FE9FA409DCBF75E836B4D301B74C551EC6828297B5BE0C9BF121C1F3AB684EBB6F4671673BE4368AE9B3BFFC53F64E2631C1ABB0C1A3570F881E0AF8B0771020EFB2148C8F4D00A93D96F47B7DAE75DF6249184C933B1EF2AF3568DA50616F25E58EC5E715636F875A7B4709EF8979EE6908EDAE1EB022241BD70090B871003E6FBB319E83F4D8E92D0A1AD28596D4086D774BACAA9E036E30AF0ACB7217418BC26516CD9B47A2DF8E2AAE0394316CBCAB8C8AF26250F5468E22DEA5A064B5B81340CF3DA87EAFA2033A2A8B719A4EF7E527B8212858ADC0FBFCFC92F4AA77699C30E080D418FED202B1D29CE2376DEA197F1379B70C5320AB06F82C2B5F2DF04D98FD631D04A2D07F8F93BD5F369C0FA8F4309866F4A5FE79997AB471CC214647CC093590612351DE2488FA412CEAE082ED5AB576D433C9EB0D862E2F556CA3DD0A868CAF6D35A51EE1C08AA8D3F943B8DBE9DB7557DAF7EE2E0269E2AB2E406D2ECC380989CBA8E4D3936374BF58FBE30F447355C0DC12C30B94E1FB6122ADAEDD25AD07712A45034D4A4C5E15031A1CCCCADE184B0689F4BA8E0B4827D7A295F7C808040AEACA590577586C40FD6A2289B52DE32BDED8FF11B729D706115C8882D6E0D74B6A862FCBB6B9715A1A449E97CDDD5BDF4F782C775143F4DE4B316D23F8A4778E6ED9FE3AE9C90128B65A35E6BAC252B209E79E0316B45481D57F1E1E972B4F3D4DCF1EF6E9A32D1407FEBD26FEE3EC363E2A8E1B38A4136F8BFCE599985DAE343FFA0DC1A6C26938BE7A74ECD4EA44FED62FE38A9E42C97B6B3A7852B9802EAC9ED5A9410F5261DC50652FB145A29D13B15FB14CA1180185E2D10F02AA8FF783B0120F716159765140000000929888212CA2C08F37E80B9936D8B68501FEFDC</ClientSecret>
</Configuration>

A new version of the connector was just released (see SharePoint Files Tool v1.1.1), have you tried installing it?

robertditonno

Thanks Florian!

Unfortunately, the configuration is not being stored for any of these ids.

That is indeed the tool version I am on.

FlorianC

Hi @robertditonno,

This may be due to compatibility limitations. Which version of Alteryx Designer and Server are you using?

Sometimes information is also cached in the tool and might not refresh as expected. Have you tried removing the tool and replacing it with a new one?

Undertak

I'm running into this same issue. Complicating my use case is that I have the SharePoint Files Input embedded in a macro since I need to read dynamically from SharePoint.

I replaced the SharePoint Files Input in my macro and reloaded it to Server and the errors still persist.

Using SharePoint Files 1.1.1 and Server/Designer 2021.34.00445.

When I load the workflow off of Server, I see all of the credentials being populated. When I run the downloaded version locally on my laptop, it runs without any issues.

I'm running everything on Server as the service account rather than my own login. I would not think that would make any difference since I'm connecting as service principal. (Just for fun I tried telling the workflow to run as me, and that makes no difference--it still errors out saying it failed authentication.)

Help!

-John

ben_hopkins

Having the same issue using SharePoint Files 2.0.1 and Designer 2021.4.1 and signing in to Sharepoint using the browser sign-in option.

Undertak

If you're trying to run a workflow on Server that had embedded credentials (such as SharePoint Files), there is a registry setting that is needed. As of 2021.3.4, you have to manually create it--not sure if this has been added 2021.4.

Instructions from Alteryx Support:

The SharePoint Files connector is a Python-based connector, so it will require the following registry key to exist in both the end users machine as well as each worker node on the server. 

Type regedit in Windows Start Menu
Browse to the folder location: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SRC\Alteryx
Right click and select New > String Value

Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SRC\Alteryx
Value Name: PythonAllowHideEncryption
Value Data: true

Once this key has been added, the user would need to reauthenticate the Salesforce tool on his workflow in Designer and republish the workflow to gallery

ben_hopkins

I have tried this. Is it really as simple as opening up regedit on the local machine and virtual machine the Alteryx Server is on and typing these in? Authorising the SharePoint tool in Designer on the local machine was unsuccessful.

Anyway, when saving the workflow with the SharePoint tool authorised from the virtual machine's instance of Designer to the Server, the connection works.

Regards,
Ben

Undertak

This has to be done on both the Designer AND Server machines, in my experience.

rhipp87

Change this extension to .reg and then run it. Windows will ask if you trust the file before merging it with your registry. You know the file is safe because if you right-click to edit you will see:

Spoiler

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SRC\Alteryx]
"PythonAllowHideEncryption"="true"

And nothing else!

PythonAllowHideEncryption.txt

rhipp87

Are you syncing the saved connection with the server? Try File -> Manage Connections -> Synchronize -> click your server -> Sync.

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703