Closed Derilka closed 5 years ago
Did you try these steps?
I am impressed - THANK YOU. The DB Upgrade helped a great deal and I did not naturally think to do it like this.
Interestingly since this is a virgin setup I reapplied the newest schema.sql (which recreates tables). After that the passwords were still created unhashed in the database - so it seems that your DB Upgrade is needed even for new installs. Maybe you can add that to the documentation of the manual install process... Anyway, do not want to complain - just thank you.
Thanks @Derilka — glad that worked out!
@bjgajjar — this issue should have been resolved in the last release. We need to make sure that schema.sql
is clean now, so let's re-generate it... and then we need to make sure that it gets updated whenever migrations change.
@rijkvanzanten — can we add "build boilerplate SQL" to the deploy/release docs?
the schema should be updated whenever a migration is made, not when the api is released
Bug Report
Steps to Reproduce
Expected Behavior
password is hashed and I can log in with the user
Actual Behavior
password is not hashed in database and I cannot log in with that user
Other Context & Screenshots
I am operating my site on Amazon EC2 with IIS and a mysql-database.
I have different things in my site - so here is how I sort of 'interlace-configured' Directus:
My web-config looks like this:
I can create users in general and create/delete/change collections, however the configuration was fully manual.
In the C:\inetpub\wwwroot\a\config\api.php those strings are still on default, simply because I do not know how render those strings in a way, that they fit together:
Technical Details