โ03-11-2020 11:26 AM
It is my understanding that when we create a Triggered Task for a pipeline there are only two ways of securing the API endpoint, 1) the bearer token and 2) basic authentication in the endpoint URL as a parameter.
I know others that use SnapLogic that have had their triggered tasks hacked (via figuring out the bearer token) and pipelines have been kicked off by people that werenโt authorized. My question is this: how can we add additional security to the Triggered Task API endpoint?
Solved! Go to Solution.
โ03-11-2020 12:41 PM
Like who? I assume folks who didnโt keep the bearer token private, or changed it to something badโฆ
A few ways to add โextraโ security to triggered tasks:
โ03-11-2020 12:41 PM
Like who? I assume folks who didnโt keep the bearer token private, or changed it to something badโฆ
A few ways to add โextraโ security to triggered tasks:
โ03-11-2020 12:58 PM
I wonโt say who it happened to, but I know the company he works for has had an issue in the past and I would like to avoid it at my company.
@christwr thank you for your suggestions! These are all great suggestions and we will probably employ IP whitelisting and an API gateway to lock things down a little more. Thanks!