What is the reason why the data can still be obtained by calling the interface when EasyCVR enables interface authentication?

The EasyCVR video fusion platform is based on the cloud-edge-end integrated architecture, which can centrally access the front-end equipment in a complex network environment, and realize the aggregation and management of video resources, live broadcast authentication, transcoding processing, multi-terminal distribution, intelligent alarm, data Sharing and other capabilities and services. The platform supports multi-protocol and multi-type device access, including national standard GB28181, RTMP, RTSP/Onvif, Hikvision Ehome, Hikvision SDK, Dahua SDK, Uniview SDK, etc., and can distribute RTMP, RTSP, HTTP-FLV, WS-FLV, HLS, WebRTC, etc.

According to user feedback, the EasyCVR 3.1 version is deployed on site. After the interface authentication is enabled, the interface /api/v1/getbaseconfig is called, and the data can still be obtained, as shown in the following figure:

The same happens when verifying that version locally. After investigation, it is found that this version /api/v1/getbaseconfig does not add authentication check. Redeploy the new version, enable interface authentication, call the interface again, and return data as shown below:

Interface authentication has taken effect, meeting user requirements.

Combining EasyCVR with the intelligent analysis gateway can realize AI intelligent detection and analysis based on the cloud, edge, and terminal architecture and the fine scheduling of computing power. The application scenarios of this solution are also very wide, including: general security, smart security monitoring , bright kitchen and bright stove, smart scenic spots, regional safety monitoring, etc. Interested users can go to the demonstration platform for experience or deployment testing.

Guess you like

Origin blog.csdn.net/EasyNVS/article/details/131309041