Hi Bve,
Thanks a lot for your reply.
The post User name and password you linked doesn’t give a solution of my problem. @Corey shows there how to propagate workflow variable into a component. The problem I described is Credentials Configuration node ignores flow variable which stores password so it produces credentials containing blank password when the Credential Configuration node is wrapped in a component.
But apart from solving partial issues with possibly misbehaving components I’d like to get an answer for a question at a bit higher level. The question is, what is the recommended design pattern of creating and configuring KNIME workflows when we have several workflows in a workspace, these workflows connect to a number of databases of different types with different connection parameters, these workflows decide which database to connect to at runtime and we need to store connection parameters externally e.g. in a properties file to make them easily replaceable in order to make workflows work with different sets of databases in different environments of different clients.