In addition to ensuring that "Database Connections" are used for workspaces, ensure no plain text passwords remain anywhere in an FME Server installation.
Released
Tighten Security within FME Server
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.
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.
+22- Safer
With the arrival of Database Connections in FME 2016.0, I believe this may be done.
+4- Safer
Absolutely, We have done a number of things on this with FME 2016.1 and the work continues. This has a very high priority at safe as well.
+14- Safer
Since the timestamp of this posting, there have been numerous improvements to how FME Server handles passwords – including preventing them from appearing in plain text in the Web Interface, log files, and configuration files (including database passwords in fmeCommonConfig.txt).
If you identify any place where a plain text password is exposed in the latest version of FME Server (2018.1 or newer as of this writing), please contact our Support Team.
Plain text passwords should not be observed. We would like to treat these occurrences separately from Ideas.
This Idea will be marked as Released.
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.