Hi Derek,
The password AFAIK is not stored in the password field in the
TURBINE_USER table. All information is stored in the (BINARY)
OBJECTDATA field in the database. So changing the PASSWORD_VALUE field
in the TURBINE_USER table will not work.
You might want to try the following (I haven't tried this to verify, but
should work in theory):
1. Turn off secure passwords.
2. Write a screen class that will encrypt the currently logged in user's
password (using TurbineSecurity class I think), and update it to the
database.
3. Restart Turbine and with secure passwords turned on.
You should be able to log into the system using the user you logged into
the Screen with.
cheers,
CP
Derek Stevenson wrote:
> Doesn't look like that works for me... I'm not sure the mysql hashing
> algorithm matches that of TurbineSecurity, either, so I don't think I
> can use the mysql password() function to create the password in my
> TURBINE_USER table.
>
> Is the solution to perhaps write a dummy script that uses
> TurbineSecurity.encryptPassword() to generate a string for that I
> manually update in mysql/TURBINE_USER?
>
> Derek
>
> At 12:15 PM 10/9/2002, you wrote:
>
>> You can change your password manually in the database with the
>> encrypted one. For example, in mysql, the password "test" sand for
>> "qUqP5cyxm6YcTAhz05Hph5gvu9M=", at least for me :). This is the value
>> I use to initialize my database with default sql scripts. From there,
>> go back into your turbine app, change the property
>> "services.SecurityService.secure.passwords" to the value "true",
>> restart and login with the password "test".
>> Another solution will be to make a sql statement to update your
>> account with the new password. It is db specific but, for mysql, the
>> function is "password('test')".
>>
>> David Worms
>>
>> On Wednesday, October 9, 2002, at 11:36 AM, Derek Stevenson wrote:
>>
>>> I'd like to enable the secure passwords feature of turbine by setting
>>> the following in my TurbineResources.properties:
>>>
>>> services.SecurityService.secure.passwords=true
>>>
>>> However, when I enable this, none of the existing accounts' passwords
>>> will work as the value stored in the database won't match the hashed
>>> result of the user's entered password. So, I thought if I could at
>>> least get my admin account to have a secure password, I could log in
>>> with that and set the hashed password in the database for new users
>>> by creating new accounts. The question is, how do I set the hashed
>>> password in the database for the admin user if I can't actually log
>>> in with the admin account?
>>>
>>> Using TDK 2.1, mysql.
>>>
>>> Thanks,
>>> Derek
>>>
>>>
>>> --
>>> To unsubscribe, e-mail:
>>> <mailto:[EMAIL PROTECTED]>
>>> For additional commands, e-mail:
>>> <mailto:[EMAIL PROTECTED]>
>>
>>
>>
>> --
>> To unsubscribe, e-mail:
>> <mailto:[EMAIL PROTECTED]>
>> For additional commands, e-mail:
>> <mailto:[EMAIL PROTECTED]>
>>
>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
>
>
--
R E D S H E R I F F
C.P. Lim - Software Engineer
Level 1, 10 Queens Road +61 3 9864 0733 tel
Melbourne VIC +61 3 9864 0778 fax
Australia +61 413 781 846 mob
This message and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you are not the intended recipient, you are hereby
notified that any use or dissemination of this communication is strictly
prohibited. If you have received this message in error please notify us
immediately by return email or telephone +61 (3) 9659 0432, then delete
this message. Any views expressed in this message are those of the
individual sender and many not necessarily reflect the views of Red Sheriff.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
