All Products
Search
Document Center

Security Center:ModifyWebLockStart

Last Updated:Nov 25, 2024

Configures and enables web tamper proofing for a specified server.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • The required resource types are displayed in bold characters.
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
yundun-sas:ModifyWebLockStartupdate
*All Resources
*
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
ModestringYes

The protection mode of web tamper proofing. Valid values:

  • whitelist: In this mode, web tamper proofing is enabled for the specified directories and file types.
  • blacklist: In this mode, web tamper proofing is enabled for the unspecified subdirectories, file types, and files in the protected directory.
whitelist
LocalBackupDirstringYes

The local path to the backup files of the protected directory.
The directory format of a Linux server is different from that of a Windows server. You must enter the directory in the required format based on your operating system. Examples:

  • Linux server: /usr/local/aegis/bak
  • Windows server: C:\Program Files (x86)\Alibaba\Aegis\bak
/usr/local/backup
ExclusiveFilestringNo

The file for which you want to disable web tamper proofing.

Note If you set Mode to blacklist, you must specify this parameter.
/home/admin/tomcat/localhost.log
DirstringYes

The directory for which you want to enable web tamper proofing. Separate multiple directories with commas (,).

/home/admin/tomcat
InclusiveFileTypestringNo

The type of the file for which you want to enable web tamper proofing. Separate multiple types with semicolons (;). Valid values:

  • php
  • jsp
  • asp
  • aspx
  • js
  • cgi
  • html
  • htm
  • xml
  • shtml
  • shtm
  • jpg
  • gif
  • png
Note If you set Mode to whitelist, you must specify this parameter.
php
UuidstringYes

The UUID of the server for which you want to enable web tamper proofing.

80d2f7d6-31a9-4d7f-8ff4-7ecc42f89ca****
ExclusiveFileTypestringNo

The type of the file for which you want to disable web tamper proofing. Separate multiple types with semicolons (;). Valid values:

  • php
  • jsp
  • asp
  • aspx
  • js
  • cgi
  • html
  • htm
  • xml
  • shtml
  • shtm
  • jpg
  • gif
  • png
Note If you set Mode to blacklist, you must specify this parameter.
jpg
ExclusiveDirstringNo

The directory for which you want to disable web tamper proofing.

Note If you set Mode to blacklist, you must specify this parameter.
/home/admin/java
DefenceModestringYes

The prevention mode. Valid values:

  • block: Interception Mode
  • audit: Alert Mode
block

Response parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The ID of the request, which is used to locate and troubleshoot issues.

D9354C1A-D709-4873-9AAE-41513327B247

Examples

Sample success responses

JSONformat

{
  "RequestId": "D9354C1A-D709-4873-9AAE-41513327B247"
}

Error codes

HTTP status codeError codeError messageDescription
400IllegalParamIllegal param-
400DuplicatedDirectoryDuplicated directory-
400NeedBuyThis service shoule be purchased first.-
400DefenceEmptyConfigAt least one protection directory is needed.-
400DefenceAuthLimitThe number of machines has reached the upper limit.-
400BindDataExistThe binding data already exists.-
403NoPermissioncaller has no permissionYou are not authorized to do this operation.
500InternalErrorThe request processing has failed due to some unknown error.-
500ServerErrorServerError-

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2024-09-24The Error code has changedView Change Details
2022-08-01The Error code has changedView Change Details