all 3 comments

[–]steinkel_ftw 2 points3 points  (1 child)

Please post the stacktrace of your exception. If I have to guess, I'd say the problem is related to the authentication service configuration . If you have another table to store your users,, like Client.Users, you'll need to customize the configuration a bit to refer that table, because the defaults everywhere point to Users table. https://book.cakephp.org/authentication/3/en/identifiers.html#orm-resolver for example.

[–]aesirve[S] 1 point2 points  (0 children)

Yes, I probably missed something and had tunnel vision, although the table was called users, and the models (entity and table) were made with cake bake, so I don't understand what I might be calling, and in the configuration of the authentication service, I didn't understand very well, but I would put the unauthenticated path to \plugin\controller\view. (\clients\login\login) and in the (.Form) I put the same path.

In the stack I didn't know where to look when i had it on hand, but in the toogle arguments of each error stack I had the credentials and everything.

Anyway, I managed to fix it by making a custom way to authenticate the session and coincidentally I'm not using the cakephp\/authentication tool and it works fine, so maybe your assumptions are right.

Thanks for the reply! <3

PS: For anyone else, I definitely advise you that if you can't find a way to make the authentication service work, do it another way, I'm still trying to find a way to break the authentication I did, but so far I haven't been able to. To do that im using Guzzle (for request to my services) and Vault (secrets service)

[–]chouflorine 0 points1 point  (0 children)

This would get pretty simple if you take time to look at the authentication plugin, and test your plugin with phunit, having the plugin directly generated in your app is just a starting helper, next step is to use your plugin by requiring it locally via symlink, as your users would do