If one had to write a migration for sfGuardUser or some inherited form
of it. How would this issue affect the implementation.
With best regards,
Alex Stoneham
On Oct 14, 1:55 am, Matt Robinson wrote:
> On Oct 13, 3:13 pm, Pablo Godel wrote:
>
> > I am using sfDoctrineGuard plugin. When I run
On Oct 13, 3:13 pm, Pablo Godel wrote:
> I am using sfDoctrineGuard plugin. When I run doctrine:data-dump and then
> data-load the passwords which are encripted by default with sha1 get
> corrupted.
As others have said, sfGuard's setPassword method is called by the
data-load task, and re-hashes
I tried this one briefly and did not fix the problem. The password keeps
changing.
The other patch looks like it would be the fix but when doing the data-load
I get an exception and nothing gets loaded. Need to look further when I get
some time.
On Tue, Oct 13, 2009 at 11:40 AM, david wrote:
>
There appears to be another work-around:
http://trac.symfony-project.org/ticket/6196
On Tue, 13 Oct 2009 17:15:08 +0200, Pablo Godel wrote:
> shouldn't this be applied to the plugin code?
>
>
> On Tue, Oct 13, 2009 at 11:10 AM, david
> wrote:
>
>>
>> Checkout: http://forum.symfony-project.
shouldn't this be applied to the plugin code?
On Tue, Oct 13, 2009 at 11:10 AM, david wrote:
>
> Checkout: http://forum.symfony-project.org/index.php/m/83831/ for more
> info
>
> On Tue, 13 Oct 2009 16:40:25 +0200, david
> wrote:
>
> >
> > The password is hashed when it's set - expecting a plai
Checkout: http://forum.symfony-project.org/index.php/m/83831/ for more info
On Tue, 13 Oct 2009 16:40:25 +0200, david
wrote:
>
> The password is hashed when it's set - expecting a plaintext password
> rather than a hashed one.
> There was a post a while ago about this issue - you need to crea
By default, data-load loads the raw data from the yml, but
sfGuardPlugin has overwritten setPassword() to make sure passwords are
stored encrypted.
As doctrine:* tasks use doctrine (and therefore the overwritten
setPassword()) the only way to load the raw data is to go around
doctrine completely.
The password is hashed when it's set - expecting a plaintext password
rather than a hashed one.
There was a post a while ago about this issue - you need to created a
method on the model that skips the hashing process.
On Tue, 13 Oct 2009 16:35:07 +0200, Pablo Godel wrote:
> That's what I th
That's what I thought is happening, but since the data-dump is raw that,
shouldn't data-load load the raw data ? is there any existing method to load
the raw dumped data directly to the DB ?
thanks for your reply.
On Tue, Oct 13, 2009 at 10:19 AM, Gábor Fási wrote:
>
> The data-dump task export
The data-dump task exports the raw values found in the database, ie.
the encrypted ones. While doing the data-load, the plugin's
overwritten setPassword() setter is called, that expect to get a
plaintext value, so it encodes it. Your passwords get corrupted
because of being encrypted again.
On Tu
10 matches
Mail list logo
