VXG Cloud VMS does not contain user authentication and authorization services. It is fully detached from user management and thus it is easy to integrate it with any existing or new authentication and authorization service. On the VXG Cloud VMS level, all data is fully anonymous and cameras are represented as a flat list of unique camera ids.
Channel ID | Access Token, … |
23454 | eyJhY2Nlc3324dwfdsf2F0Y2giLCAidG9r34… |
23455 | eyJhYfsdfdslc3MiOiAid2F0Y2giLCAidG9rrW… |
23456 | eyJghjY2Nlc3MiOiAid2F0Y2giLCAidG9rZe… |
23457 | eyJhY2Nlc3MiOiAid2F0Y2giLCAidG9rZ5… |
23458 | eyJhY2Nlc3MiOiAid2F0Y2giLCAidG9rZ1… |
It is easy to integrate the Cloud VMS with any existing or new authentication and authorization service. As an example, Web front-end and Mobile apps use the VSaaS template that comes as a part of the Cloud VMS uses Google Firebase for authentication.
...
The authorization and permissions are managed by a simple backend DB that associates Firebase user ids with camera ids and corresponding access levels.
...
The Access Tokens are all you need for playback live or recorded video using Web or Mobile SDK, as well as for calling REST API functions of the VXG Cloud VMS platform.
...
The same copy of the CLoud VMS can work with multiple authentication services and back-ends. This is often called multi-tenancy:
...