I can't find anything in the documentation about how FME Desktop stores published parameters that are passwords. Are these encrypted? Or does FME desktop store these parameters as clear text behind the password stars?
For instance, in the workspace below, I have published parameters that are passwords (I've set the published parameters to password type) How is FME Desktop storing these?
Best answer by jeroenstiers
Hi @j9recurses
If you open your workspace in Notepad(++) and you search on the parameter name, you will see that the fme_decrypt function is being used to store the password.
I am afraid that is all I know. Reading this post, made me conclude the community doesn't know more than this.
+7Hi @j9recurses
If you open your workspace in Notepad(++) and you search on the parameter name, you will see that the fme_decrypt function is being used to store the password.
I am afraid that is all I know. Reading this post, made me conclude the community doesn't know more than this.
+20Right, we do encrypt them. So they are not stored in plain text. As much as possible, we've moved to using "connections" in FME 2016/2017 that adds even more protection by moving even the encrypted passwords out of workspaces and into centralized, even more encrypted, data stores.
Right, we do encrypt them. So they are not stored in plain text. As much as possible, we've moved to using "connections" in FME 2016/2017 that adds even more protection by moving even the encrypted passwords out of workspaces and into centralized, even more encrypted, data stores.
We would like to be able to manage encrypted credentials centrally so that multiple separate workspaces that depend on the same connection can be updated simultaneously and securely.
+23
We would like to be able to manage encrypted credentials centrally so that multiple separate workspaces that depend on the same connection can be updated simultaneously and securely.
Or go into Tools > FME Options > Default Paths. Under connection storage you can set the location. Setting that to a shared location means you can share "public" connections between workspaces. So no need to have multiple people create exactly the same connection, you can have one connection used by mutliple workspaces and only one connection to edit..
I have set these in our install setup via registry edits a few years ago. Don't think these options are available during setup yet?
+38Right, we do encrypt them. So they are not stored in plain text. As much as possible, we've moved to using "connections" in FME 2016/2017 that adds even more protection by moving even the encrypted passwords out of workspaces and into centralized, even more encrypted, data stores.
