Bcrypt not working in Lumen 5.4: Call to undefined function bcrypt()

Question

I created a new Lumen 5.4 project and tried to seed some data. In the seeder, I used bcrypt to hash the password. But when I run php artisan db:seed, I get this error:

Call to undefined function bcrypt()

Why can't I use bcrypt in Lumen? I have used it in Laravel previously.

score 46 · Accepted Answer · answered Mar 08 '17 at 06:05

46

You could try:

app('hash')->make('yourpassword');

answered Mar 08 '17 at 06:05

Amr Aly

3,871
2
16
33

True, this is more or less a workaround of the bcrypt implementation but why not use it directly? – JackSlayer94 Mar 08 '17 at 06:06
1

really i don't know but what i know is `bcrypt()` in its source code returns this `return app('hash')->make($value, $options);` – Amr Aly Mar 08 '17 at 06:10
1

Okay thanks! Might be worth adding that this is a work around so people will be aware of it. – JackSlayer94 Mar 08 '17 at 06:11
Is there any way to get hash key. Actually, I took over someone's project and now getting same error and now the previous developer is not responding. And I know what is encrypted key generated as I have access to database. – Tanish bansal Jan 09 '21 at 15:01

score 14 · Answer 2 · answered Aug 07 '18 at 15:20

14

another solution would be to use Facades\Hash

use Illuminate\Support\Facades\Hash;

code

'password' => Hash::make('your_password')

answered Aug 07 '18 at 15:20

Ernesto Aguaysol

141
1
4

score 9 · Answer 3 · answered Jun 11 '18 at 02:11

9

Try to do it this way

'password' => password_hash('123456', PASSWORD_BCRYPT)

answered Jun 11 '18 at 02:11

krrskl

91
2
5

1

This answer will marked as low quality. Please provide more information. – Wahyu Kristianto Jun 11 '18 at 11:08

Bonny Ham · Answer 4 · 2019-07-10T15:10:03.523

-1

try, I can do it fine in my project

 function bcrypt($value, $options = [])
        {
            return app('hash')->make($value, $options);

        }

edited Jul 10 '19 at 15:10

answered Jul 10 '19 at 12:40

Bonny Ham

9
1

3

Please provide more information to this answer. Also, to me this does not seem to be a real solution to the problem, just a quick workaround to "just get it running". – PhilMasteG Jul 10 '19 at 14:06
what should be included in options? – Tanish bansal Jan 09 '21 at 15:25

score -2 · Answer 5 · answered Oct 13 '17 at 12:10

-2

As you mentioned, bcrypt() doesn't exist in Lumen. As another workaround, since you mentioned seeding in Lumen, you could just use this in \Faker\Generator for the password: $faker->password

answered Oct 13 '17 at 12:10

kakoma

1,179
13
17

Yeah, so you will not know the generated password and you will not be able to test the script using the generated users. Nope. – Sergiu Nov 08 '17 at 17:01
@Sergiu There are a number of use-cases where you aren't going to login with the generated users; I believe this option is a viable one especially in those scenarios. The question asked actually didn't restrict the need to test the script using the generated users so this approach is valid. – kakoma Nov 09 '17 at 20:40
I do not agree, in a testing/dev environment it's always a good practice to use the same password for all users, for obvious reasons. In a production environment, you would not use Faker. – Sergiu Nov 11 '17 at 13:35

Bcrypt not working in Lumen 5.4: Call to undefined function bcrypt()

5 Answers5