Subject | TIB_Connection and Passwords |
---|---|
Author | Geoff Worboys |
Post date | 2001-08-11T01:37:24Z |
Hi All,
Firstly thanks to those that took the time to offer their comments and
opinions to my survey thread.
Just to let everyone know that we went with a slight variation of the
option 2 I described in the survey thread. This change is now
available as part of the IBO_4_2_Ea release.
Jason has rebuilt the IBO4 help file so that the online help for the
new PasswordStorage option is available. Please install this update
so that you have the full explanation of the options available with
this property.
IBO will automatically upgrade existing apps to use the
PasswordStorage property. If you had previously set
PasswordRemembered to true then PasswordStorage will be set to
psKeyFromUserReg, otherwise it will default to psNone (password will
not be saved).
To explain briefly...
By default PasswordStorage will be set to psNone, so the password will
NOT be saved to the DFM (and executable). This means; At designtime
you will need to enter the password everytime to load the module
containing the connection - if you want to connect during design. At
runtime you must prompt the user for the password, or assign the
password directly from code.
If you wish to save the password only while developing I recommend you
set PasswordStorage to use the psKeyFromUserReg option. This is the
same as the previous PasswordRemembered option. That is; The
password will be stored but can only be read on the current machine by
the current user since the decryption key is stored in the user
registry. This will offer some protection against accidently
distributing your password. When ready to deploy simply set
PasswordStorage back to psNone.
If you wish to distribute the password in the executable, set
PasswordStorage to psNotSecure. The password will be obscured, but
it can be read on any machine and by any user - because the decryption
key is hardcoded into IBObjects. This is not recommended but, as
explained by some users, there can be legitimate reasons for taking
this approach.
If you want to change the default action simply define your own
derivation of TIB_Connection and alter the default appropriately. The
VCL online help has information about creating your own components.
Geoff Worboys
Telesis Computing
Firstly thanks to those that took the time to offer their comments and
opinions to my survey thread.
Just to let everyone know that we went with a slight variation of the
option 2 I described in the survey thread. This change is now
available as part of the IBO_4_2_Ea release.
Jason has rebuilt the IBO4 help file so that the online help for the
new PasswordStorage option is available. Please install this update
so that you have the full explanation of the options available with
this property.
IBO will automatically upgrade existing apps to use the
PasswordStorage property. If you had previously set
PasswordRemembered to true then PasswordStorage will be set to
psKeyFromUserReg, otherwise it will default to psNone (password will
not be saved).
To explain briefly...
By default PasswordStorage will be set to psNone, so the password will
NOT be saved to the DFM (and executable). This means; At designtime
you will need to enter the password everytime to load the module
containing the connection - if you want to connect during design. At
runtime you must prompt the user for the password, or assign the
password directly from code.
If you wish to save the password only while developing I recommend you
set PasswordStorage to use the psKeyFromUserReg option. This is the
same as the previous PasswordRemembered option. That is; The
password will be stored but can only be read on the current machine by
the current user since the decryption key is stored in the user
registry. This will offer some protection against accidently
distributing your password. When ready to deploy simply set
PasswordStorage back to psNone.
If you wish to distribute the password in the executable, set
PasswordStorage to psNotSecure. The password will be obscured, but
it can be read on any machine and by any user - because the decryption
key is hardcoded into IBObjects. This is not recommended but, as
explained by some users, there can be legitimate reasons for taking
this approach.
If you want to change the default action simply define your own
derivation of TIB_Connection and alter the default appropriately. The
VCL online help has information about creating your own components.
Geoff Worboys
Telesis Computing