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
Even after several iterations, current approach to handling third party storage providers, especially the authentication part, is pretty clumsy. oslo/oauth2 can relieve a lot of pressure associated auth and token management.
Proposed solution
We’ll use Deno for runtime and oak for API routes. The business logic largely can be taken from current InterCloud with little to no changes. The main difference will be in auth management: instead of custom implementation we’ll rely on Oslo, sessions will be managed server-side, client will only receive an http-only cookie with session ID only. Access and refresh tokens will be stored server-side, probably in Redis.
Acceptance criteria
No functionality regression
The auth flow and interaction with the cloud provider works correctly on both web and Android platforms
The text was updated successfully, but these errors were encountered:
Description
Even after several iterations, current approach to handling third party storage providers, especially the authentication part, is pretty clumsy. oslo/oauth2 can relieve a lot of pressure associated auth and token management.
Proposed solution
We’ll use Deno for runtime and oak for API routes. The business logic largely can be taken from current InterCloud with little to no changes. The main difference will be in auth management: instead of custom implementation we’ll rely on Oslo, sessions will be managed server-side, client will only receive an http-only cookie with session ID only. Access and refresh tokens will be stored server-side, probably in Redis.
Acceptance criteria
The text was updated successfully, but these errors were encountered: