Skip to main content
Question

?Comprehensive, centralized way to store published parameter passwords used by multiple workspaces in FME Server?

  • February 1, 2017
  • 6 replies
  • 52 views

I am running multiple workspaces that have the same published parameters that are passwords. Is there centralized way to store published parameter passwords that are used by multiple workspaces?

I can't find anything in the documentation about how to do this.

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.

6 replies

erik_jan
Contributor
Forum|alt.badge.img+26
  • Contributor
  • February 1, 2017

What kind of passwords are you referring to.

If it is database connections, FME stores these in a connection file outside the FMW file.

They are references by connection name, so the username, password and database name are not stored in the FME file.


erik_jan
Contributor
Forum|alt.badge.img+26
  • Contributor
  • February 1, 2017

What kind of passwords are you referring to.

If it is database connections, FME stores these in a connection file outside the FMW file.

They are references by connection name, so the username, password and database name are not stored in the FME file.

And FME 2017 has the same option for Web service connection information as for database connections.

 

 


itay
Supporter
Forum|alt.badge.img+18
  • Supporter
  • February 1, 2017

unfortunately this is not the case for published parameter even password type and they are quite easy to reveal.

There are several ways to accomplish that for example a centralized file containing passwords that is read via a startup python script.

I am sure other users have other ideas and experiences to share.

Hope this helps


  • Author
  • February 1, 2017

What kind of passwords are you referring to.

If it is database connections, FME stores these in a connection file outside the FMW file.

They are references by connection name, so the username, password and database name are not stored in the FME file.

I'm referring to passwords that are stored as published job parameters, not database connections. I was aware of the fact that FME stored database connections differently from his article: https://knowledge.safe.com/questions/22574/fmeserverjobsubmitter-logging-password-in-clear-te.html

 

 

Basically, I'm looking for a centralized way to pass published job parameter passwords to scheduled jobs on FME server......

 

My apologies for not being more clear in my question.

 


  • Author
  • February 1, 2017

unfortunately this is not the case for published parameter even password type and they are quite easy to reveal.

There are several ways to accomplish that for example a centralized file containing passwords that is read via a startup python script.

I am sure other users have other ideas and experiences to share.

Hope this helps

@itay, thanks for this reply!

 

Yes-You've suggested a decent work around that I hadn't thought of. It would definitely be possible for me to grab passwords from centralized file via a python script. That being said, I wish there was an easier way.... lol.

 


david_r
Celebrity
  • February 2, 2017
@itay, thanks for this reply!

 

Yes-You've suggested a decent work around that I hadn't thought of. It would definitely be possible for me to grab passwords from centralized file via a python script. That being said, I wish there was an easier way.... lol.

 

The easier way is to use the FME Server / Desktop named connection functionality ;-)

 

It's also a lot more secure.