In the current wunderDB access-token system, we are using only one access token for all access - Admin Access, Service Access and App/Third-Party Client Access. This poses a serious fault that doesn't allow different levels of separation of access for different actions. The goal is to prepare a Multi-Token Multi-Level Access Token Framework for accessing different sections and actions in wPlat.
In the current wunderDB access-token system, we are using only one access token for all access - Admin Access, Service Access and App/Third-Party Client Access. This poses a serious fault that doesn't allow different levels of separation of access for different actions. The goal is to prepare a Multi-Token Multi-Level Access Token Framework for accessing different sections and actions in wPlat.
Refer to Notes and Observations in The Curious case of Login and the various Tokens.