I used the following to diagnose my mistakes and misunderstandings....
1.) I was successfully creating a token with the following code placed in src/illuminate/Foundation/Auth/AuthenticatesUsers/Authenticated
So After the user is logged in I am creating a token.
$token = $user->createToken('Token Name')->accessToken;
2.) Upon login the table oauth_access_tokens is creating a record with a field "ID". I mistakenly thought the ID field was the token....IT IS NOT THE TOKEN.
3.) I logged the token to the error log. Then I took the token from the error log and plugged it into Postman....Shazam....it worked.
Followup question. Why isn't the token stored in one of the 6 tables that passport creates when I installed it and then ran the migrations? Do I need to manually store the token into the user field...???
OH...As I write out my thoughts...I think that the key and secret are encrypting and decrypting the ID field that is stored with the oauth_access_token table....Is that what is happening?
I am going to write my frontend app in React JS...So react will just need to store a cookie or something on the client to continually send over the token for access....is that correct?