We created a service account with non-expiring credentials for a Microsoft SQL Server DB. We want to give users the ability to publish productionalized workflows to our gallery using these credentials, but do not want the users to actually have the credentials. To complicate matters more, the DB is a replica of the one the users actually have access to so it is a different connection/dsn than they will be using for development. I thought about creating a custom connector and masking the credentials in it and allowing specific users access to download and use the connector, but if they are like me they will right click on it and open it up which will reveal the credentials. Is there any way to mitigate that risk and use this method? Is there any other way of handling this that I might be missing short of everyone's workflows being published to the gallery by someone with this access and these credentials?
