[Flow] Passwords not working if existing database is used for deployment

[David Sporer]

Good morning,

I found the problem……………
Copied the encryptionKey file to the wrong folder.

*pushesheadagainstwall*

Thanks nonetheless :-)

Regards,
David


> Am 21.06.2015 um 18:06 schrieb Aske Ertmann <aske at moc.net>:
> 
> Hi David,
> 
> Haven't had that problem when doing the same. Make sure you copy the
> file Data/Persistent/EncryptionKey correctly, as AFAIK not doing that can
> cause what you're experiencing.
> 
> Cheers,
> Aske
> 
> On Sun, Jun 21, 2015 at 4:07 PM, David Sporer <david.sporer at gmail.com>
> wrote:
> 
>> Hi,
>> 
>> I’ve today deployed a Flow application and used an existing database for
>> it.
>> In general it worked fine, the only problem I got was, that the passwords
>> were not working any longer.
>> I’m using the PersistedUsernamePasswordProvider as provider.
>> I’ve copied the files under Data/Persistent to the new deployment.
>> 
>> If I use my forgot password feature which sets a temporary password in the
>> background, I can log in again just fine.
>> 
>> Do you know how to prevent that behaviour as I’m planning to deploy my
>> live application with Surf also but that would mean that all users need to
>> set a new password if I can’t prevent that.
>> 
>> Thanks,
>> David
>> _______________________________________________
>> Flow mailing list
>> Flow at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
> 
> 
> 
> 
> -- 
> Venlig hilsen Aske
> 
> Webudvikler, team lead
> MOC A/S
> 4692 3435 / 4333 2200
> moc.net
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow