Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Connection String Possibilities

We are trying to implement a QlikView app in our environment and we are struggling with one thing,

In the QVD generating QVW's we have to connect to an ODBC that has a username and password on it, so we type that in. However, our system requires us to change our password every 90 days. When everything is said and done we plan on having 4 QVD generators that we schedule to run (daily, weekly, monthly, and quarterly).

What do you think is the best way to handle the password situation? We would prefer to not have to go into all 4 and change that string every 90 days. Surely we can automate this someway? We thought about passing UserID and Password to all 4 from an Excel file, however then we have to push that Excel file to the server and that's a security risk because that Excel file cannot be encrypted in order for QlikView to use it. Could we somehow get it from an encrypted file? Just throw ideas at me, because this is a new development environment for us, I'm open to all suggestions.

We've also talked about automating the change on our side with Windows Scheduler or some kind of similar macro that runs on a back-machine. We are just now dabbling in that realm too, is anyone familiar with it and how well it would work with QlikView?

Any ideas/suggestions/thoughts/examples of how you handle something similar?

-Neil

4 Replies
Anonymous
Not applicable
Author

Maybe use NT security to make the Excel file available only for the QV service "user" (and admins).

Not applicable
Author

Thanks for the tip, still looking for other options to bring to the table to let my team discuss!

Clever_Anjos
Employee
Employee

Maybe you could store your credentiais into server Windows Registry and retrive them using

GetRegistryString (path, key)

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

Use a $Include() to pull the connection string in from an external file. Generate the connection string in Qlikview using the scrambled password option, so the password will not be stored in clear text. This is still a manual process, so a developer will have to regenerate the connection string when the password changes.

You didn't say what ODBC driver you were using, but some driver allow saving the password in the ODBC def. That's another possibility.

-Rob