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
Currently all togo settings are stored in the local storage of the browser. The Metadata API provides one means of persistence, but does not isolate access from other applications or togo instances attempting to use the same namespace. The client, group, and profile settings APIs allow a client application to store data within a namespace unique to the client and user or group. Leveraging these services allows custom configurations to be stored securely by applications without fear of leakage or over exposure.
Push the ToGo config into the client settings service on startup and sync user settings with the profile settings service on auth success.
In theory, this would allow ToGo to enforce a whitelist/blacklist, autoconfig, etc without a backend. It wouldn't be the more secure thing in the world, but it would be enough for quite a few user groups.
The text was updated successfully, but these errors were encountered:
Currently all togo settings are stored in the local storage of the browser. The Metadata API provides one means of persistence, but does not isolate access from other applications or togo instances attempting to use the same namespace. The client, group, and profile settings APIs allow a client application to store data within a namespace unique to the client and user or group. Leveraging these services allows custom configurations to be stored securely by applications without fear of leakage or over exposure.
Push the ToGo config into the client settings service on startup and sync user settings with the profile settings service on auth success.
The text was updated successfully, but these errors were encountered: