ModifyLoginBaseConfig - Security Center - Alibaba Cloud Documentation Center

Modifies the logon configuration for a specified asset.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Debug

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.

Operation	Access level	Resource type	Condition key	Associated operation
yundun-sas:ModifyLoginBaseConfig	Write	All Resources *	none	none

Request parameters

Parameter	Type	Required	Description	Example
Type	string	Yes	The logon type of the configuration to modify. Valid values: login_common_location: common logon location login_common_ip: common logon IP address login_common_time: common logon time range login_common_account: common logon account	login_common_location
Config	string	Yes	The details of the configuration that is used to detect unusual logons to your servers. The value of this parameter is in the JSON format and contains the following fields: totalCount: the total number of servers. uuidCount: the number of servers to which the configuration is applied. id: the ID of the configuration. location: the common logon location. Note You must specify this field if the Type parameter is set to login_common_location. ip: the common logon IP address. Note You must specify this field if the Type parameter is set to login_common_ip. endTime: the end time of the common logon time range. Note You must specify this field if the Type parameter is set to login_common_time. startTime: the start time of the common logon time range. Note You must specify this field if the Type parameter is set to login_common_time. account: the common logon account. Note You must specify this field if the Type parameter is set to login_common_account.	{"totalCount":174,"uuidCount":4,"location":"Montenegro","id":0}
Target	string	Yes	The details of the server to which the configuration is applied. The value of this parameter is in the JSON format and contains the following fields: Target: the UUID of the server. targetType: the type of the server to which the configuration is applied. Valid values: uuid: a server groupId: a server group flag: the operation that you want to perform on the server. Valid values: del: removes the server from the configuration. add: adds the server to the configuration.	[{"target":"inet-7c676676-06fa-442e-90fb-b802e5d6****","targetType":"uuid","flag":"add"}]

Response parameters

Parameter	Type	Description	Example
	object	The data returned.
RequestId	string	The ID of the request, which is used to locate and troubleshoot issues.	AB96FDDF-ED29-52B1-9FAE-8203F2808F24
Code	string	The status code returned. The status code 200 indicates that the request was successful. Other status codes indicate that the request failed. You can identify the cause of the failure based on the status code.	200
Message	string	The message returned.	successful
Success	boolean	Indicates whether the request was successful. Valid values: true: The request was successful. false: The request failed.	true

Examples

Sample success responses

JSONformat

{
  "RequestId": "AB96FDDF-ED29-52B1-9FAE-8203F2808F24",
  "Code": "200",
  "Message": "successful",
  "Success": true
}

Error codes

HTTP status code	Error code	Error message	Description
400	DataNotExists	%s data not exist	-
403	NoPermission	caller has no permission	You are not authorized to do this operation.
500	ServerError	ServerError	-

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

Change history

Change time	Summary of changes	Operation

No change history