Easy Solution to Update JWT Login Credentials for Adobe Analytics Connector

[OneandOnly13]

Hi Everyone,

As of today, Adobe Analytics make us change our JWT login credentials on an annual basis. This means we're having to go into every workflow and change every connector with the new login info each year. This is quite a task yearly since the connector is in many of our workflow and most workflows have way more than one connector in them. Has anyone found an easier way to maintain the login credentials and they don't have to do this? Would love to see what others are doing. Thanks for any ideas/help!

[matthewbechard]

I need to watch this thread.  I just set this up.

[cjaneczko]

I havent use the Adobe connector, but if its anything like Oracle or MySQL, you can create an Alias for your data connection which stores the login credentials. Whenever the credentials are updated you only need to update the UID and PW in the Manage Data Connections and it will update all the workflows that use that Alias. Once the Data Connection is setup you can just reference the Alias in the connection. For Example it will be aka:Adobe instead of whatever connection path you are using.

Here is the link on how to setup an Alias for your data connection.

https://community.alteryx.com/t5/Alteryx-Designer-Knowledge-Base/Database-Connections-Creating-an-al...

[matthewbechard]

The tool is not a typical database  connection tool.  It looks like it's essentially a macro. So maybe the client secret, token and other things are pointed to a file on a UNC Path that is secure, and the other questions done as normal.  I wish I had time to explore this. 

[cjaneczko]

Ah, yeah that is quite a bit different than the ODM connections. 

[matthewbechard]

Another idea on this...

I am using Macros with the tool to pass granularity and dates to the tool.  I just noticed that you may be able to pass the key with a Macro.

I would love to collaborate on a solution if anyone wants to sync up.

Matt

[OneandOnly13]

Thanks @matthewbechard  and @cjaneczko for the ideas! Our issue with putting the connector behind a macro is that my whole team would want to use it and each workflow might have many Adobe connectors (one has almost 40 itself). What might be possible is creating a text input tool "template" that would pass all of the Adobe tool pieces (granularity, dates, segments, elements, etc.) and then have a separate data input that has the credentials that would join (or possibly append) to the data input pieces. This can then be passed onto a macro with the connector inside. Not sure how fast it would pull the data though but in theory this would have a centralized place to store the credentials that would mean only changing the credentials once. This is just a brainstorm and would definitely need to be thought through much more.

[matthewbechard]

FYI-  Alteryx just updated the adobe connector to v 3.1.  I built a workflow that automated this process in updating  my macros.  This could be done with regular workflows but they will need to be reuploaded to the Alteryx Server.