|
Tom What do you think of Java and Websphere hard coding profile/passwords? It seems to me it's done thru-out this new stuff. No? John Carr And second, rather than hard-coding, use soft-coding. The application itself should never need the actual profile/password. It should only need to know where and how to obtain it. Accessing it externally (and securely, of course) helps reduce the impact of the situation that started this debate -- i.e., even if the QUSER password is changed, big deal; the location containing the profile/password should simply be changed as well. Of course, in that original situation (QUSER being used within an application without the knowledge of the tech responsible for QUSER), the system is effectively being held hostage by the application(s). If QUSER is being used without knowledge, it now becomes difficult to change QUSER password. The impact is currently unpredictable; and I'd find that unacceptable. Tom Liotta
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.