MarkGidman's avatar

Stateless API with HMAC

I'm porting a SlimFramework API to Laravel 5. The app is stateless, uses HMAC for auth and has no UI. It also has no central database but uses a single sqlite db per account.

Outside of the no central database scenario this is a pretty common use case in Slim. While I like all the goodies in Laravel for a UI centric app, I'm hoping to slim down the footprint for an API centric app. So far I've run artisan fresh and removed the following service providers and their aliases:

  • Auth
  • Cookie
  • Redis
  • PasswordReset
  • Session
  • View

After removing the related calls in the HttpKernel and WelcomeController I ran artisan clear-compiled. I am now able to deliver json as expected from a controller action without the system setting any cookies.

I'm wondering if anyone else has been down this path. If so, are their any hidden issues/concerns that come up later with all of this removed from the framework?

0 likes
0 replies

Please or to participate in this conversation.