So currently have a live environment that spans across two application servers and a separate database server as well. 3 servers total. Both app servers write and read from the DB server.
Now the problem I am seeing with Laravel Passport is when i create a Personal Access Token. It seems to only authenticate on the original issuing server (that or the first one it hits on the first submit) ... I have a round robin setup right now - so basically every other request is saying i am unauthenticated...
If my two app servers (identical) are reading from the same DB server... then what is the issue? Is laravel passport storing something in a file? not 100% sure on the ins and outs of Passport...
Will also note my sessions are stored in Redis on the DB server both app servers are pointing to that.
Thanks Citti
via Citti