Authorized operations

Same name in other branches
  1. 7.x modules/system/system.module \authorize
  2. 9 core/modules/system/system.module \authorize
  3. 8.9.x core/modules/system/system.module \authorize
  4. 10 core/modules/system/system.module \authorize

Functions to run operations with elevated privileges via authorize.php.

Because of the Update manager functionality included in Drupal core, there is a mechanism for running operations with elevated file system privileges, the top-level authorize.php script. This script runs at a reduced Drupal bootstrap level so that it is not reliant on the entire site being functional. The operations use a FileTransfer class to manipulate code installed on the system as the user that owns the files, not the user that the httpd is running as.

The first setup is to define a callback function that should be authorized to run with the elevated privileges. This callback should take a FileTransfer as its first argument, although you can define an array of other arguments it should be invoked with. The callback should be placed in a separate .inc file that will be included by authorize.php.

To run the operation, certain data must be saved into the SESSION, and then the flow of control should be redirected to the authorize.php script. There are two ways to do this, either to call system_authorized_run() directly, or to call system_authorized_init() and then redirect to authorize.php, using the URL from system_authorized_get_url(). Redirecting yourself is necessary when your authorized operation is being triggered by a form submit handler, since calling redirecting in a submit handler is a bad idea, and you should instead use $form_state->setRedirect().

Once the SESSION is setup for the operation and the user is redirected to authorize.php, they will be prompted for their connection credentials (core provides FTP and SSH by default, although other connection classes can be added via contributed modules). With valid credentials, authorize.php will instantiate the appropriate FileTransfer object, and then invoke the desired operation passing in that object. The authorize.php script can act as a Batch API processing page, if the operation requires a batch.

See also

authorize.php

\Drupal\Core\FileTransfer\FileTransfer

hook_filetransfer_info()

File

core/modules/system/system.module, line 379

Functions

Title File name Summary
system_authorized_batch_process core/modules/system/system.module Use authorize.php to run batch_process().
system_authorized_batch_processing_url core/modules/system/system.module Returns the URL for the authorize.php script when it is processing a batch.
system_authorized_get_url core/modules/system/system.module Return the URL for the authorize.php script.
system_authorized_init core/modules/system/system.module Setup a given callback to run via authorize.php with elevated privileges.
system_authorized_run core/modules/system/system.module Setup and invoke an operation using authorize.php.

Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.