Skip to main content
Released

FME Server proxy settings in admin GUI

Related products:FME Flow
  • September 5, 2016
  • 8 replies
  • 125 views
david_r
Celebrity

Setting the proxy info in FME Server currently involves using the command line, see https://docs.safe.com/fme/html/FME_Server_Documentation/Content/AdminGuide/Using_FME_Server_with_Proxy_Server.htm

I suggest including these settings in the admin GUI to make them easier to maintain without needing console access to the server.

These settings should override whatever proxy setting is defined in published workspaces (HTTPCaller, etc).

The most important bit is to set the proxy server and enter the authentication details. Defining custom proxy maps is probably less important.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

8 replies

C
Forum|alt.badge.img
  • crayxt
  • September 5, 2016

Currently, setting proxy in HTTPCaller is not supported, it relies on system settings.

While I agree that setting common proxy in admin GUI is very useful, I can't understand why it should overwrite proxy settings in workspace (even if there aren't such settings currently, lets suppose proxy setting is implemented in HTTPCaller). By overwriting per-workspace/per-transformer settings you will lose the ability:

a) to define different proxies for workspaces within one FME server.

b) to selectively enable internet access for workspaces within on FME server. E.g. suppose common proxy is not set, so if proxy details are entered in workspace/transformer, only then it has access to internet.

david_r
Celebrity
  • david_rCelebrity
  • Author
  • September 5, 2016
Ah, thanks for claryfing about the HTTPCaller, I forgot that Safe had removed the proxy settings.

 

 

I can see your point regarding the use cases, although I personally would not have any use for this functionality on behalf of any of my clients; I prefer to solve these issues using global configuration files.

 

 

Maybe there could be an option in FME Server on whether its proxy settings should be global or not, that might cover both of our use cases.
rylanatsafe
Safer
Forum|alt.badge.img+14

Something great is coming soon to an FME Server 2019.1 installation near you...

'

Screenshot from FME Server 2019.1 Build 19570.

---

Please note that this feature is currently included with the beta version of FME Server and its functionality and appearance are subject to change as the product continues to evolve before the official release.

Should this feature or its implementation not address your concerns, related to this Idea posting, please let us know by leaving a comment.

As with all beta features and beta versions of our software, they are not considered production-safe and should be incorporated into your workflows with consideration and testing.

david_r
Celebrity
  • david_rCelebrity
  • Author
  • May 27, 2019

This looks very promising! Just one question: will it be possible to manage exceptions to the proxy server, e.g. for local servers?

rylanatsafe
Safer
Forum|alt.badge.img+14

Hi @david_r, we do not have the option to bypass local addresses right now. Would this be more preferable over supporting custom proxy maps – or, phrased a different way, which do you feel is more important? They are both different levels of effort to implement... Please get in touch if you would like to discuss further.

D

Just wondering if this option is available at repository folder level as we have an internal FME server with firewalls closed to the internet. We can only get outside via a proxy account. This account has to be define on which sites we can go too. We don't want to list all our internal url's with this account if set global. Could break existing jobs if not listed. This is the reason I added https://knowledge.safe.com/idea/48415/fme-server-add-a-option-to-set-the-proxy-to-indivi.html at individual level. I'll be happy if it can be at repository folder level

rylanatsafe
Safer
Forum|alt.badge.img+14
  • rylanatsafeSafer
  • Safer
  • August 6, 2019

Hi @darren_george, the settings will affect all of FME Server – we do not have the ability to define proxy settings per workspace, per repository, or per feature.

If you were able to define an exclusion list using wildcards for any internal URLs – and it would apply to all of FME Server – would that help?

rylanatsafe
Safer
Forum|alt.badge.img+14
  • rylanatsafeSafer
  • Safer
  • August 6, 2019

FME Server 2019.1 was released July 11th, 2019 and included the ability to configure proxies in the web interface.

This idea will have its status changed from In Beta to Released. If you have any feedback, please add comments or get in touch with our Support Team.

Community Stats

32,750
Posts
124,205
Replies
41,255
Members
Terms & ConditionsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.