Change Details

Replaces the use of tymon:jwt with laravel:passport. A password grant client is used create tokens for the webclient in the same fashion as we used to the tymon:jwt solution. The same password grant client can be used for other client applications. Notes: * The TTL is currently set to 15 days. Should we just set it to 1h again? * We might be able to simplify the SPA's token handling by using the passport middleware that automatically stores the access_token in the session. * We're not currently purging invalidated/expired tokens. This can be done via artisan command or scheduled task from php.

Replaces the use of tymon:jwt with laravel:passport. A password grant client is used create tokens for the webclient in the same fashion as we used to the tymon:jwt solution. The same password grant client can be used for other client applications. Notes: * We're not currently purging invalidated/expired tokens. This can be done via artisan command or scheduled task from php.

Replaces the use of tymon:jwt with laravel:passport. A password grant client is used create tokens for the webclient in the same fashion as we used to the tymon:jwt solution. The same password grant client can be used for other client applications. Notes: * The TTL is currently set to 15 days. Should we just set it to 1h again? * We might be able to simplify the SPA's token handling by using the passport middleware that automatically stores the access_token in the session. * We're not currently purging invalidated/expired tokens. This can be done via artisan command or scheduled task from php.