Probar la autenticación

Hi @Alkiviadis-D

Hm looks like session is not working correctly between requests, or maybe login request was not fully successful... have you tried to use ->actingAs($user) shortcut to see if it works correctly?

Cheers!

Okkk.. had a typo inside getRoles(). Sorry for this. Thanks for your help.

Hey @sujal_k ,

Does your User entity have $id field? Does that field has the same mapping as in this course code? i.e. it should be :

    #[ORM\Id]
    #[ORM\GeneratedValue]
    #[ORM\Column]
    private ?int $id = null;

Also, make sure you don't have an invalid Doctrine mapping by calling this command:

bin/console doctrine:schema:validate

Ad make sure both mapping and DB are OK.

I hope this helps!

Cheers!

I'm getting the exact same error.

Started my project from latest ApiPlatform Distribution (AP 3.4, Symfony 6.4). When I log in making POST to json_login path I'm able to fetch resources which require full authetication, but when I swap login process with ->actingAs($user) I get 500 error described above while trying to fetch any resource.

I checked my schema as recommended above (everyting is ok) and my User entity is rather standard (created by make:user). It's id is on place.

Do you have any other ideas what can be wrong here? :(

Hey Kriss,

Hm, difficult to say without further debugging, probably try to find the place where that error is thrown and before that exception try to dump the actual user to make sure it really has an ID.

Also, if you’re customizing serialization groups, ensure that the identifier field is included in the serialization group used when the API Platform serializes the user.

Cheers!

Hey Victor,

I performed some further debuging and I discovered that when I use $entityManager to create my $user object like so:

static::bootKernel();
$entityManager = static::$kernel->getContainer()->get('doctrine.orm.entity_manager');
        
$user = new User();
$user->setEmail(self::TEST_USER_EMAIL);
$user->setPassword('password');
$user->setIsConfirmed(true);

$entityManager->persist($user);
$entityManager->flush();

then I'm am able to use $browser->actingAs($user) normaly. Also when I get type of created entity using getMetatadaFor method I get App\Entity\User.

When I create $user using UserFactory and try to get object's type using the same method I get an error:

Doctrine\Persistence\Mapping\MappingException: The class 'AppEntityUserProxy' was not found in the chain configured namespaces App\Entity, Vich\UploaderBundle\Entity, CoopTilleuls\ForgotPasswordBundle\Entity

Looks like there is something wrong with doctrine mapping? Or maybe It's something wrong with UserFactory configuration?
I used ApiPlatform distribution as a starter, created Facotry with make:facotry and didn't mess with doctrine mappings at all, so why would they be wrong... Do you have any idea? :)

Hey Kriss,

Ah, good catch! Yeah, that's actually on purpose, entity factories from the Foundry lib need that to add more magic in tests - those proxy objects helps you to do not worry about the problem with refreshing the entity in tests. But that AppEntityUserProxy actually extends your User class, so instanceof User still should work.

In short, nothing is wrong with this behavior, that's how it's suppose to work in Foundry, you just need to keep this in mind. If it bothers you or causing some issues - you can create objects manually bypassing creating it via Foundry factories.

P.S. Sorry for the long reply, I somehow missed this ticket 🙃

Cheers!

Hey Victor,

thanks for your explanation, however it seems that this does not resolve the issue this thread is about.

Namely: why in the tutorial Ryan was able to use browser->actingAs($user) with $user created with Foundry factory and when I try to do this I get the 500 error mentioned by @sujal_k at the beginning of this thread? And why am I able to use this method when creating user using entity manager?

Do you think it can have something to do with the fact I stared my project from AP Distribution, not from cli installation?

Hey @Kriss_G!

Can you tell me what version of zenstruck/browser & zenstruck/foundry you are using?

composer show zenstruck/browser
composer show zenstruck/foundry

(I'm thinking you may be on foundry 2+ but your browser version does not support it yet - I'm hoping upgrading zenstruck/browser will fix)

--Kevin

Hey Kevin @kbond!,

Indeed, I used foundry v2.1.0 and browser v1.9.0.
I ran composer update zenstruck/browser, which brought my browser version to 1.9.1 and it seems to solve the issue.

I can now use browser->actingAs($user) with $user generated with UserFactory class!

Thank you for your help! :)

Kriss

Awesome, great to hear!

Hey @sujal_k!

These invalid credentials can be tricky as you can't really see what's going on since the passwords are all hashed. And I don't see any obvious problems. Triple check that the password IS being hashed before saving to the DB. You could also temporarily change the hashing algo to plaintext. It may help you see the underlying problem.

Cheers!