This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Customize & extend the power of Alteryx. SDKs, APIs, custom tools, and more!
General Discussions has some can't miss conversations going on right now! From conversations about automation to sharing your favorite Alteryx memes, there's something for everyone. Make it part of your community routine!
I have written an HTML + Python Oauth tool for a platform. I Oauth in the HTML fine and it saves the auth token and refresh token which is made available to the Python. The issue is that once the access token expires, I refresh it. The refreshing brings with it a new refresh token which I have to use for subsequent refreshes. I need to replace the (now defunct) refresh token stored in the config with the new one. How do I write configuration data back to the tool config, or should I persist this elsewhere?
Unfortunately, once you start using the tokens, the original ones become invalid, so if you use them in the engine, the UI ones need to now get re-authed, which invalidates the ones in the engine etc.
But I hear you about not being able to write config from the engine, that is what I have found as well. I am thinking of setting up an online service which both UI and engine can access to manage and persist tokens.