Seperate Guards for Authentication/Authorization

[evansims]

At the moment, the SDK currently provides a single Gaurd interface, which handles all of the state management for both stateful (authentication/session-based) and stateless (authorization/access token-based) requests.

Improvements

While this offers a simplified integration experience, it can introduce complications for Laravel applications that need to handle traffic for both of these use types simultaneously. Without distinct Guards, you must work around the limitations of having one SDK configuration and a single, multipurpose guard by using event hooks.

Our goal for the next major release will be to offer distinct and independent guards for each type of request scenario, which can be used side by side, to handle different types of requests within a host application simultaneously.

Blockers

This will not be possible until the next major of the new underlying PHP SDK is released, as there are technical limitations imposed on our Laravel implementation that must be resolved upstream before we can properly implement that feature here.