Archives of the TeradataForum
Message Posted: Mon, 16 Mar 2009 @ 17:28:24 GMT
| Subj: || || Re: BTEQ question: How to handle login/password |
| From: || || Curley, David |
I'm not sure you can do what you need if your Unix setup is such that a mix of authorized and unauthorized people have access to the same set
of directories. If it's mixed access, how can you save a password anywhere such that unauthorized users cannot access it?
Here's an alternative: have one Unix ID for each developer plus whatever application-level accounts you need, each with a consistent directory
structure under ~home. Each one has their own ~/secure/td.dat that is readable only by them. Now anybody can write a script using
.run=/path/to/home/logon/td.sec. When run, it will use the logon of whoever's running it and the consistent directory structure means that
nothing should be out of place from one user to the next. You can also add so groups so maybe all developers can read/write each other's files
(for good or ill). If you have development and production application IDs, you can use soft links to supply development IDs to everybody while
keeping the prod ones hidden.