Skip to Content
Browse documentation

App Authentication and Security

Enforce authentication, panel-specific ownership, safe privileged operations and trusted deployment boundaries for Eenos extensions.

An installed extension executes code inside the server's control-panel environment. App metadata and menu visibility are not a permission system or isolation boundary.

Authenticate every entry point

For Django views, use the current panel's authenticated request and protect views with login_required or an equivalent verified policy. Protect background/AJAX endpoints as well as the visible page. For PHP, establish a reviewed authentication and session mechanism; the My Apps link does not pass a trusted Django identity automatically.

Do not reuse the old shell-based shadow-password example, expose password files to web workers, or accept an asserted username from the browser as identity.

Enforce ownership and operation permissions

WAP, RAPP and UAPP have different authority. Derive the actor from trusted server-side context, validate its current status and permitted scope, and check ownership of each requested resource. A valid login does not permit access to every account, domain or file.

For mutations, use appropriate request methods, validated forms/payloads and CSRF protection. Escape output and validate filesystem paths, identifiers and uploaded content. Do not use a hidden menu or a disabled button as the enforcement check.

Keep privileged work in a narrow backend

Unprivileged RAPP/UAPP code must not run arbitrary root shell commands. Follow the panel's taskmanager/backend separation, passing only validated operations and data. Do not offer a generic command executor or accept executable paths from a request. A PHP root-FPM socket is not a substitute for a permission model.

Treat installation as trusted administrative execution

App archives can install dependencies, scripts, hooks, web routes and pre/post code. Review their contents and provenance before installation. The reviewed app manager does not provide package-signature verification, dependency isolation or transaction rollback.

Keep secrets outside public assets and distribute only app-owned files. Use unique paths and names so updates and removal cannot unintentionally target another extension's resources. Maintain logs with useful correlation identifiers without storing passwords, private keys or temporary login tokens.

Verify disable and uninstall behavior

Per-panel disable changes availability and applicable vhosts but does not remove installed scripts/hooks. Global disable is not guaranteed to stop app-owned workers or every external entry point. Test the actual protected endpoints and background activity when planning suspension or removal.

Use packaging acceptance checks and document any app-specific cleanup or recovery steps for administrators.