Skip to main content

At the moment I get a token with a normal HTTPCaller with username and password as User parameters. However, I would like to store username and password secure. For this reason I tried to use a Web Connection. Unfortunately this didn't work. Any recommendation hwo this should be done?

 

This is my HTTPCaller that works fine but with the drawback that username and password are defined as user parameters in plaintext.

Bild 1

I think you should be able to create your own Web Connection to do this. (Tools, Options, Web Connections, Manage Services, + to create new Web Connection, I think Token Service.)


I think you should be able to create your own Web Connection to do this. (Tools, Options, Web Connections, Manage Services, + to create new Web Connection, I think Token Service.)

Plus one for this option - the fme doc could use a little love in this space but you should be able to get it to work with some experimentation


Plus one for this option - the fme doc could use a little love in this space but you should be able to get it to work with some experimentation

I was also looking for a tutorial or article on how to do this, but I found none. Is there other documentation than the help?


Plus one for this option - the fme doc could use a little love in this space but you should be able to get it to work with some experimentation

Here's a tutorial for a token based service - it's pretty light though: https://community.safe.com/s/article/Creating-a-TOKEN-based-Web-Service-in-FME-Yelp

 

There's also this one on Oauth 2 - https://community.safe.com/s/article/Web-Connections-and-FME

 

And here's a more general overview: https://community.safe.com/s/article/Web-Connections-and-FME


Plus one for this option - the fme doc could use a little love in this space but you should be able to get it to work with some experimentation

Thanks!


Reply