Technical Plugin Vdatait

Technical: Vdatait plugin

Provides installation-specific frontend/integration behavior.

Audience: developers, advanced administrators and AI-assisted diagnosis. Plugin catalog.

Source baseline

• Review date: 2026-10-29. Method: static source analysis; runtime/provider behavior was not exercised.
• Code ownership: installation-specific local extension; no canonical repository identified.
• Reported version: 1.0.
• Entry class file: Vdatait.php.

Confirm the installed plugin version independently of the Streamer version. Configuration defaults below are not a dump of this installation's saved settings.

Dependencies

No literal dependency declaration was extracted. This does not prove the plugin is standalone.

Hook integration

Override	Implementation
updateScript()	Vdatait.php:33
getStart()	Vdatait.php:145
decodeAToken()	Vdatait.php:369
videoHLSProtectionByPass($videos_id)	Vdatait.php:445

Configuration assignments

These are direct assignments inside getEmptyDataObject(), not evaluated effective defaults. Stored plugins.object_data, globals, structured values and conditional branches may alter runtime behavior. Private/default credential values are omitted.

Field	Literal default or expression type	Literal source label/help	Evidence
baseURL	Computed/structured; inspect source	—	source
privateKeyPassword	Private setting; value omitted	—	source
privateKey	Private setting; value omitted	—	source
publicKey	Private setting; value omitted	—	source
checkClientIP	false	—	source
atokenTimeoutInSeconds	Private setting; value omitted	—	source
testVideos_id	0	—	source
testFilename	''	—	source
testBaseURLVideos_id	0	—	source
testBaseURLFilename	''	—	source
testBaseURL	Computed/structured; inspect source	—	source

Files and request surface

This inventory distinguishes implementation files from an API specification. Includes, templates, callbacks and CLI workers are not interchangeable HTTP endpoints. Request-field names below are direct source references, not a complete schema or permission declaration.

File	Source role	Direct request fields observed
Vdatait.php	plugin entry class	GUID, byPassAdmin, comebackhere, debug, filename, globalToken, key
decrypt.json.php	JSON entry point; inspect caller and guard	encryptedMessage, encryptedUA
encrypt.json.php	JSON entry point; inspect caller and guard	videos_id
functionsKeys.php	PHP page/include/worker; inspect caller	—
generateKeys.json.php	JSON entry point; inspect caller and guard	—
guid.json.php	JSON entry point; inspect caller and guard	GUID
guid.php	PHP page/include/worker; inspect caller	—
messages.php	PHP page/include/worker; inspect caller	—
securityCheck.php	PHP page/include/worker; inspect caller	videos_id

Data and migrations

No CREATE TABLE names were extracted from available plugin SQL. The plugin can still use core tables, PHP-created schema or another component's data. Apply installation/update behavior through the owning plugin; this reference is not a script for running historical migrations manually.

Main-file named symbols

Visibility and implementation semantics must be checked in source. Nonempty string defaults are represented as . This is a symbol reference, not a stable public API promise.

Function or method	Source
getDescription()	10
getName()	18
getUUID()	23
getPluginVersion()	28
updateScript()	33
getEmptyDataObject()	45
isValidToAuthorize()	108
getStart()	145
authorizeVideoPage()	158
ignore()	173
authorizeEncryptionKey()	192
isAuthorized($videos_id)	219
authorizeGUID()	231
requestPostman($videos_id, $guid)	282
decodeAToken()	369
checkAToken()	403
shouldByPass()	431
videoHLSProtectionByPass($videos_id)	445

Supporting PHP declarations

These symbols are grouped by source file; inspect the class declaration and visibility before calling them.

functionsKeys.php

Named symbol	Source
createKeysVdatait($UserIDPacket = '<string>', $password = '')	8
encryptMessageVdatait($message, $publicKey)	60
decryptMessageVdatait($encryptedMessage, $privatekey, $password = '')	71

securityCheck.php

Named symbol	Source
getMainDomain()	5

Diagnostics and validation

1. Check the installed/enabled version and the dependencies/settings above.
2. Identify the actual failing page, request, callback or worker and correlate its timestamp with the AVideo log.
3. Follow the linked method and caller. Check business-state changes and output artifacts as well as HTTP status.
4. Reproduce the relevant workflow in a test environment. External provider, Encoder, live-server, storage, payment and authenticated flows require their real integrations.

Shared diagnostic workflow. This page is not a security audit or a claim of end-to-end validation.