You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I see in the documentation for custom strategies that can only check features if we have the user's session. The problem with that is that the current user is not always obtain the same way in different parts of a application (API token, sso, session) and I would like to have an option to pass the current_user object directly like:
I imagine you have a request object in all cases? So the solution would be to unify whatever differences you have by inspecting the request and retrieve the user information in different ways depending on the request parameters/hostname/session/path, etc.
Hello,
I see in the documentation for custom strategies that can only check features if we have the user's session. The problem with that is that the current user is not always obtain the same way in different parts of a application (API token, sso, session) and I would like to have an option to pass the current_user object directly like:
How could do it do something like this possible?
The text was updated successfully, but these errors were encountered: