Creating a user group
|
userGroup
diff --git a/docs/iam/umn/iam_01_0013.html b/docs/iam/umn/iam_01_0013.html
index eab06263..32614938 100644
--- a/docs/iam/umn/iam_01_0013.html
+++ b/docs/iam/umn/iam_01_0013.html
@@ -3,7 +3,7 @@
Viewing Audit Logs
After you enable CTS, it records key operations performed on IAM. You can view the operation records of the last 7 days on the CTS console.
Viewing IAM Audit Logs- Log in to the management console.
- Click Service List in the upper part of the page and choose Cloud Trace Service under Management & Deployment.
- In the navigation pane, choose Trace List.
- Click Filter in the upper right corner of the trace list to set filter conditions.
The following filters are available: - Trace Source, Resource Type, and Search By
- Select a filter criteria from the drop-down list. Specifically, select IAM from the Trace Source drop-down list.
- If you select Trace name for Search By, select a trace name.
- If you select Resource ID for Search By, select or enter a resource ID.
- If you select Resource name for Search By, select or enter a resource name.
- - Operator: Select an operator (a user rather than domain).
- Trace Status: Available options include All trace statuses, normal, incident, and warning.
- Specify the start time and end time for querying traces.
+ - Operator: Select an operator (a user rather than domain).
- Trace Status: Available options include All trace statuses, normal, incident, and warning.
- Specify the start time and end time for querying traces.
- Click Query.
- Expand the details of a trace, as shown in Figure 1.
Figure 1 Expanding trace details
- Click View Trace in the Operation column. In the View Trace dialog box as shown in Figure 2, the trace details are displayed.
Figure 2 Viewing a trace
diff --git a/docs/iam/umn/iam_01_0016.html b/docs/iam/umn/iam_01_0016.html
index 0fba3e0e..5a8f71da 100644
--- a/docs/iam/umn/iam_01_0016.html
+++ b/docs/iam/umn/iam_01_0016.html
@@ -2,32 +2,28 @@
Creating a Custom Policy
You can create custom policies to supplement system-defined policies and implement more refined access control.
- Creating a Custom Policy in the Visual Editor- On the IAM console, choose Policies in the navigation pane, and click Create Custom Policy.
- Enter a policy name.
- Select a scope based on the type of services related to this policy.
- Global services: Select this option if the services to which the policy is related must be deployed in the Global region. When creating custom policies for globally deployed services, specify the scope as Global services. Custom policies of this scope must be attached to user groups for the global service project.
- Project-level services: Select this option if the services to which the policy is related must be deployed in specific regions. When creating custom policies for regionally deployed services, specify the scope as Project-level services. Custom policies of this scope must be attached to user groups for specific projects except the global service project.
-For example, when creating a custom policy containing the action evs:volumes:create for EVS, specify the scope as Project-level services.
- A custom policy can contain actions of multiple services that are globally accessible or accessible through region-specific projects. To define permissions required to access both global and project-level services, create two custom policies and specify the scope as Global services and Project-level services.
- - Select Visual editor.
- Set the policy content.
- Select Allow or Deny.
- Select a cloud service.
Only one cloud service can be selected for each permission block. To configure permissions for multiple cloud services, click Add Permissions or switch to the JSON view.
+ Creating a Custom Policy in the Visual Editor- On the IAM console, choose Policies in the navigation pane, and click Create Custom Policy.
- Enter a policy name.
- Select Visual editor.
- Set the policy content.
- Select Allow or Deny.
- Select a cloud service.
Only one cloud service can be selected for each permission block. To configure permissions for multiple cloud services, click Add Permissions or switch to the JSON view.
- Select actions.
- Select all resources, or select specific resources by specifying their paths.
- (Optional) Add request conditions by specifying condition keys, operators, and values.
-
Table 1 Condition parametersName
+Table 1 Condition parametersName
|
-Description
+ | Description
|
|---|
-Condition Key
+ | Condition Key
|
-A key in the Condition element of a statement. There are global and service-level condition keys. Global condition keys (starting with g:) are available for operations of all services, while service-level condition keys (starting with a service abbreviation name such as obs:) are available only for operations of the corresponding service.
+ | A key in the Condition element of a statement. There are global and service-level condition keys. Global condition keys (starting with g:) are available for operations of all services, while service-level condition keys (starting with a service abbreviation name such as obs:) are available only for operations of the corresponding service.
|
-Operator
+ | Operator
|
-Used together with a condition key to form a complete condition statement.
+ | Used together with a condition key to form a complete condition statement.
|
-Value
+ | Value
|
-Used together with a condition key and an operator that requires a keyword, to form a complete condition statement.
+ | Used together with a condition key and an operator that requires a keyword, to form a complete condition statement.
|
@@ -38,11 +34,7 @@
- (Optional) To add another permission block for the policy, click Add Permissions. Alternatively, click the plus (+) icon on the right of an existing permission block to clone its permissions.
- (Optional) Enter a brief description for the policy.
- Click OK.
- Attach the policy to a user group. Users in the group then inherit the permissions defined in the policy.
-Creating a Custom Policy in JSON View- On the IAM console, choose Policies in the navigation pane, and click Create Custom Policy.
- Enter a policy name.
- Select a scope based on the type of services related to this policy.
- Global services: Select this option if the services to which the policy is related must be deployed in the Global region. When creating custom policies for globally deployed services, specify the scope as Global services. Custom policies of this scope must be attached to user groups for the global service project.
- Project-level services: Select this option if the services to which the policy is related must be deployed in specific regions. When creating custom policies for regionally deployed services, specify the scope as Project-level services. Custom policies of this scope must be attached to user groups for specific projects except the global service project.
-For example, when creating a custom policy containing the action evs:volumes:create for EVS, specify the scope as Project-level services.
- A custom policy can contain actions of multiple services that are globally accessible or accessible through region-specific projects. To define permissions required to access both global and project-level services, create two custom policies and specify the scope as Global services and Project-level services.
-
- - Select JSON.
- (Optional) Click Select Existing Policy, and select a policy to use it as a template, such as VPC Admin.
- Click OK.
- Modify the statement in the template.
- Effect: Set it to Allow or Deny.
- Action: Enter the actions provided in the API actions table of the EVS service, for example, evs:volumes:create.
- The version of each custom policy is fixed at 1.1.
+ Creating a Custom Policy in JSON View- On the IAM console, choose Policies in the navigation pane, and click Create Custom Policy.
- Enter a policy name.
- Select JSON.
- (Optional) Click Select Existing Policy, and select a policy to use it as a template, such as VPC Admin.
- Click OK.
- Modify the statement in the template.
- Effect: Set it to Allow or Deny.
- Action: Enter the actions provided in the API actions table of the EVS service, for example, evs:volumes:create.
- The version of each custom policy is fixed at 1.1.
- (Optional) Enter a brief description for the policy.
- Click OK. If the policy list is displayed, the policy is created successfully.
- Attach the policy to a user group. Users in the group then inherit the permissions defined in the policy.
diff --git a/docs/iam/umn/iam_01_0023.html b/docs/iam/umn/iam_01_0023.html
index 3654093a..45d19512 100644
--- a/docs/iam/umn/iam_01_0023.html
+++ b/docs/iam/umn/iam_01_0023.html
@@ -3,7 +3,7 @@
Identity Management
You can manage users in your account and their security credentials. In addition, you can configure identity federation so that users in other systems can access the cloud platform through SSO.
DomainA domain, also called an "account", is created upon successful registration with the cloud platform. The domain has full access permissions for its cloud services and resources.
- For security purposes, create a security administrator and grant them Security Administrator permissions to manage users and their permissions in your account.
+ For security purposes, create a security administrator and grant them Security Administrator permissions to manage users and their permissions in your account.
Figure 1 Account management model
UserYou or other administrators can create users for employees, systems, or applications in IAM. The users can log in to the console or access APIs using their own identity credentials (passwords and access keys).
diff --git a/docs/iam/umn/iam_01_0029.html b/docs/iam/umn/iam_01_0029.html
index 7dddd88f..dc8309bb 100644
--- a/docs/iam/umn/iam_01_0029.html
+++ b/docs/iam/umn/iam_01_0029.html
@@ -14,7 +14,7 @@
- Go to the Security Settings page.
- Click the Critical Operations tab, and click Bind in the Virtual MFA Device row.
- Set up the MFA application by scanning the QR code or manually entering the secret key.
You can bind a virtual MFA device to your account by scanning the QR code or entering the secret key.
- Scanning the QR code
Open the MFA application on your mobile phone, and use the application to scan the QR code displayed on the Bind Virtual MFA Device page. Your account or IAM user is then added to the application.
- Manually entering the secret key
Open the MFA application on your mobile phone, and enter the secret key.
- Your account is manually added using the time-based algorithm. Ensure that automatic time setting has been enabled on your mobile phone.
+ The user can be manually added only using time-based one-time passwords (TOTP). You are advised to enable automatic time setting on your mobile phone.
- View the verification codes on the MFA application. The code is automatically updated every 30 seconds.
- On the Bind Virtual MFA Device page, enter two consecutive verification codes and click OK.
@@ -22,39 +22,39 @@
Login ProtectionAfter login protection is enabled, you and IAM users created using your account will need to enter a verification code in addition to the username and password during login. Enable this function for account security.
For the account, only the account administrator can enable login protection for it. For IAM users, both the account administrator and other administrators can enable this feature for the users.
- (Administrator) Enabling login protection for an IAM user
To enable login protection for an IAM user, go to the Users page and choose More > Security Settings in the row that contains the IAM user. In the Login Protection area on the displayed Security Settings tab, click  next to Verification Method, and select a verification method from SMS, email, or virtual MFA device.
- - Enabling login protection for your account
To enable login protection, click the Critical Operations tab on the Security Settings page, click Enable next to Login Protection, select a verification method, enter the verification codes, and click OK.
+ - Enabling login protection for your account
To enable login protection, click the Critical Operations tab on the Security Settings page, click Enable next to Login Protection, select a verification method, enter the verification code, and click OK.
Operation Protection- Enabling operation protection
After operation protection is enabled, you and IAM users created using your account need to enter a verification code when performing a critical operation, such as deleting an ECS. This function is enabled by default. To ensure resource security, keep it enabled.
The verification is valid for 15 minutes and you do not need to be verified again when performing critical operations within the validity period.
- Go to the Security Settings page.
- On the Critical Operations tab, locate the Operation Protection row and click Enable.
- Select Enable and then select Self-verification or Verification by another person.
If you select Verification by another person, an identity verification is required to ensure that this verification method is available.
-- Self-verification: You or IAM users themselves perform verification when performing a critical operation.
- Verification by another person: The specified person completes verification when you or IAM users perform a critical operation. Only SMS and email verification are supported.
+ - Self-verification: You or IAM users themselves perform verification when performing a critical operation.
- Verification by another person: The specified person completes verification when you or IAM users perform a critical operation. Only SMS and email verification are supported.
- Click OK.
- Disabling operation protection
If operation protection is disabled, you and IAM users created using your account do not need to enter a verification code when performing a critical operation.
- - Go to the Security Settings page.
- On the Critical Operations tab, locate the Operation Protection row and click Change.
- Select Disable and click OK.
- Enter a verification code.
- Self-verification: The administrator who wants to disable operation protection completes the verification. SMS, email, and virtual MFA verification are supported.
- Verification by another person: The specified person completes the verification. Only SMS and email verification are supported.
+- Go to the Security Settings page.
- On the Critical Operations tab, locate the Operation Protection row and click Change.
- Select Disable and click OK.
- Enter a verification code.
- Self-verification: The administrator who wants to disable operation protection completes the verification. SMS, email, and virtual MFA verification are supported.
- Verification by another person: The specified person completes the verification. Only SMS and email verification are supported.
- Click OK.
- - Each cloud service defines its own critical operations.
- When IAM users created using your account perform a critical operation, they will be prompted to choose a verification method from email, SMS, and virtual MFA device.
- If a user is only associated with a mobile number, only SMS verification is available.
- If a user is only associated with an email address, only email verification is available.
- If a user is not associated with an email address, mobile number, or virtual MFA device, the user will need to associate at least one of them before the user can perform any critical operations.
+ - Each cloud service defines its own critical operations.
- When IAM users created using your account perform a critical operation, they will be prompted to choose a verification method from email, SMS, and virtual MFA device.
- If a user is only associated with a mobile number, only SMS verification is available.
- If a user is only associated with an email address, only email verification is available.
- If a user is not associated with an email address, mobile number, or virtual MFA device, the user will need to associate at least one of them before they can perform any critical operations.
- You may not be able to receive email or SMS verification codes due to communication errors. In this case, you are advised to use a virtual MFA device for verification.
- If operation protection is enabled, IAM users need to enter verification codes when performing a critical operation. The verification codes are sent to the mobile number or email address bound to the IAM users.
Access Key Management- Enabling access key management
After access key management is enabled, only the administrator can create, enable, disable, or delete access keys of IAM users. This function is disabled by default. To ensure resource security, enable this function.
To enable access key management, click the Critical Operations tab on the Security Settings page, and click  in the Access Key Management row.
- Disabling access key management
After access key management is disabled, all IAM users can create, enable, disable, or delete their own access keys.
-To enable access key management, click the Critical Operations tab on the Security Settings page, and click  in the Access Key Management row.
+To enable access key management, click the Critical Operations tab on the Security Settings page, and click in the Access Key Management row.
Information Self-Management- Enabling information self-management
By default, information self-management is enabled, indicating that all IAM users can manage their own basic information (login password, mobile number, and email address). Determine whether to allow IAM users to manage their own information and what information they can modify.
-To enable information self-management, click the Critical Operations tab on the Security Settings page, and click Enable next to Information Self-Management. Select Enable, select the information types that IAM users can modify, and click OK.
+To enable information self-management, click the Critical Operations tab on the Security Settings page, and click Enable in the Information Self-Management row. Select Enable, select the information types that IAM users can modify, and click OK.
- Disabling information self-management
After you disable information self-management, only administrators can manage their own basic information. If IAM users need to modify their login password, mobile number, or email address, they can contact the administrator. For details, see Viewing and Modifying User Group Information.
To disable information self-management, click the Critical Operations tab on the Security Settings page, and click Change in the Information Self-Management row. In the displayed pane, select Disable and click OK.
Critical OperationsThe following tables list the critical operations defined by each cloud service.
- Table 1 Critical operations defined by cloud servicesService Type
+Table 1 Critical operations defined by cloud servicesService Category
|
Service
|
@@ -97,7 +97,7 @@
- Deleting a vault
- Deleting a backup
- Restoring a backup
- Deleting a policy
- Dissociating a resource
- Accepting a backup
|
|---|
-Network
+ | Networking
|
Domain Name Service (DNS)
|
@@ -106,28 +106,27 @@
Virtual Private Cloud (VPC)
|
- |
Elastic Load Balance (ELB)
|
-- Classic load balancers
- Deleting a load balancer
- Deleting a listener
- Deleting a certificate
- Disabling a load balancer
-
- |
Elastic IP (EIP)
|
-- Deleting a shared bandwidth
- Releasing or unbinding an EIP
- Releasing or unbinding EIPs
+ | - Deleting a shared bandwidth
- Releasing or unbinding an EIP
- Batch releasing or unbinding EIPs
|
Management & Deployment
|
Identity and Access Management (IAM)
|
-- Disabling operation protection
- Disabling login protection
- Changing the mobile number
- Changing the email address
- Changing the login password
- Changing the login authentication method
- Deleting an IAM user
- Disabling an IAM user
- Deleting an agency
- Deleting a user group
- Deleting a policy
- Deleting permissions
- Creating an access key
- Deleting an access key
- Disabling an access key
- Deleting the project
- Modifying the status of access key management
+ | - Disabling operation protection
- Disabling login protection
- Changing the mobile number
- Changing the email address
- Changing the login password
- Changing the login authentication method
- Deleting an IAM user
- Disabling an IAM user
- Deleting an agency
- Deleting a user group
- Deleting a policy
- Deleting permissions
- Creating an access key
- Deleting an access key
- Disabling an access key
- Deleting a project
- Modifying the status of access key management
|
Application
@@ -144,7 +143,7 @@
| - Resetting the administrator password
- Deleting a DB instance
- Deleting a database backup
- Switching between primary and standby DB instances
- Changing the database port
- Deleting a database account
- Deleting a database
- Unbinding an EIP
- Downloading a full backup
|
-Databases
+ | Database
|
Document Database Service (DDS)
|
diff --git a/docs/iam/umn/iam_01_0030.html b/docs/iam/umn/iam_01_0030.html
index db9b2f36..c4efa34c 100644
--- a/docs/iam/umn/iam_01_0030.html
+++ b/docs/iam/umn/iam_01_0030.html
@@ -5,8 +5,9 @@
Procedure- Choose .
- In the navigation pane, choose User Groups.
- On the User Groups page, click Create User Group.
- Enter a user group name.
- (Optional) Enter a description for the user group.
To enable users to directly view their permissions, set a description for the user group. For example, if you assign the Security Administrator role to a user group, you can set any description in the Description text box. For example: Security Administrator: Permissions for creating, deleting, and modifying users as well as granting permissions to users. For details about the permissions for all cloud services, see Permission Description.
- Click OK.
The user group is displayed in the user group list.
- - In the row containing the user group, click Manage Permissions.
- On the Permissions tab page, click Assign Permissions above the permission list.
- Specify the authorization scope. If you select Region-specific projects, select one or more projects in the drop-down list.
- Global service project: Services deployed without specifying physical regions are called global services, such as Object Storage Service (OBS), and Tag Management Service (TMS). Permissions for these services must be assigned in the global service project.
- Region-specific projects: Services deployed in specific regions are called project-level services. Permissions for these services need to be assigned in region-specific projects and take effect only for the corresponding regions. If you want the permissions to take effect for all regions, grant them in all these regions.
- - Select policies and click OK.
+ - In the row containing the user group, click Authorize in the Operation column.
- Assign permissions for region-specific projects to the user group.
- Select desired permissions for project-level services and click Next.
- Set Scope to Regional-specific projects, select the regional project, and click OK.
+ - Assign permissions for global services to the user group.
- Select permissions for global services, such as OBS OperateAccess, and click Next.
- Select All resources for Scope and click OK.
+
diff --git a/docs/iam/umn/iam_01_0063.html b/docs/iam/umn/iam_01_0063.html
index 1aa88480..241385a4 100644
--- a/docs/iam/umn/iam_01_0063.html
+++ b/docs/iam/umn/iam_01_0063.html
@@ -1,13 +1,13 @@
(Optional) Assigning Permissions to an IAM User (by a Delegated Party)
- When a trust relationship is established between your account and another account, you become a delegated party. By default, only your account and the members of the admin group can manage resources for the delegating party. To authorize IAM users to manage these resources, assign permissions to the users.
+ When a trust relationship is established between your account and another account, you become a delegated party. By default, only your account and the members of the admin group can manage resources for the delegating party. To authorize IAM users to manage these resources, assign permissions to the users.
You can authorize an IAM user to manage resources for all delegating parties, or authorize the user to manage resources for a specific delegating party.
Prerequisites- A trust relationship has been established between your account and another account.
- You have obtained the name of the delegating account and the name and ID of the created agency.
Procedure- Create a user group and grant permissions to it.
- On the User Groups page, click Create User Group.
- Enter a user group name.
- Click OK.
- In the row containing the user group, click Authorize.
- Create a custom policy.
This step is used to create a policy containing permissions required to manage resources for a specific agency. If you want to authorize an IAM user to manage resources for all agencies, go to 1.f.
-- On the Select Policy/Role page, click Create Policy in the upper right corner of the permission list.
- Enter a policy name.
- Select JSON for Policy View.
- In the Policy Content area, enter the following content:
{
+- On the Select Policy/Role page, click Create Policy in the upper right corner of the permission list.
- Enter a policy name.
- Select JSON for Policy View.
- In the Policy Content area, enter the following content:
{
"Version": "1.1",
"Statement": [
{
@@ -23,12 +23,12 @@
}
]
}
- - Replace b36b1258b5dc41a4aa8255508xxx... with the agency ID obtained from a delegating party. Do not make any other changes.
- For more information about permissions, see Permissions.
+ - Replace b36b1258b5dc41a4aa8255508xxx... with the agency ID obtained from a delegating party. Do not make any other changes.
- For more information about permissions, see Permissions.
- Click Next.
- - Select the policy created in the previous step or the Agent Operator role and click Next.
- Custom policy: Allows a user to manage resources only for a specific agency.
- Agent Operator role: Allows a user to manage resources for all agencies.
+ - Select the policy created in the previous step or the Agent Operator role and click Next.
- Custom policy: Allows a user to manage resources only for an agency identified by a specific ID.
- Agent Operator role: Allows a user to manage resources for all agencies.
- Specify the authorization scope.
- Click OK.
- - Create an IAM user and add the user to the user group.
- On the Users page, click Create User.
- On the Create User page, enter a username.
- For the access type, select Management console access and Set by user.
- Enable login protection and click Next.
- Select the user group created in 1 and click Create.
After the authorization is complete, the IAM user can switch to the account of the delegating party and manage specific resources under the account.
+ - Create an IAM user and add the user to the user group.
- On the Users page, click Create User.
- On the Create User page, enter a username.
- Select Management console access for Access Type and then select Set by user for Credential Type.
- Enable login protection and click Next.
- Select the user group created in 1 and click Create.
After the authorization is complete, the IAM user can switch to the account of the delegating party and manage specific resources under the account.
diff --git a/docs/iam/umn/iam_01_0430.html b/docs/iam/umn/iam_01_0430.html
index 0eb36277..f7a219e8 100644
--- a/docs/iam/umn/iam_01_0430.html
+++ b/docs/iam/umn/iam_01_0430.html
@@ -3,12 +3,12 @@
- Deleting a User Group
+ Deleting User Groups
ProcedureTo delete a user group, do the following:
- - Log in to the IAM console. In the navigation pane, choose User Groups.
- In the user group list, click Delete in the row that contains the user group to be deleted.
- In the displayed dialog box, click Yes.
+ - Log in to the IAM console. In the navigation pane, choose User Groups.
- In the user group list, click Delete in the row that contains the user group to be deleted.
- In the displayed dialog box, click Yes.
Batch Deleting User GroupsTo delete multiple user groups at a time, do the following:
- - Log in to the IAM console. In the navigation pane, choose User Groups.
- In the user group list, select the user groups to be deleted and click Delete above the list.
- In the displayed dialog box, click Yes.
+ - Log in to the IAM console. In the navigation pane, choose User Groups.
- In the user group list, select the user groups to be deleted and click Delete above the list.
- In the displayed dialog box, click Yes.
diff --git a/docs/iam/umn/iam_01_0607.html b/docs/iam/umn/iam_01_0607.html
index aac7208a..90c322a5 100644
--- a/docs/iam/umn/iam_01_0607.html
+++ b/docs/iam/umn/iam_01_0607.html
@@ -8,7 +8,7 @@
Only the administrator can configure the password policy, and IAM users can only view the configurations. If an IAM user needs to modify the configurations, the user can request the administrator to perform the modification or grant the required permissions.
You can configure the password policy to ensure that IAM users create strong passwords and rotate them periodically. In the password policy, you can define password requirements, such as minimum password length, whether to allow consecutive identical characters in a password, and whether to allow previously used passwords.
Password Composition & Reuse- Ensure that the password contains 2 to 4 of the following character types: uppercase letters, lowercase letters, digits, and special characters. By default, the password must contain at least 2 of these character types.
- Set the minimum number of characters that a password must contain. The default value is 6 and the value range is from 6 to 32.
- (Optional) Enable the Restrict consecutive identical characters option and set the maximum number of times that a character is allowed to be consecutively present in a password. For example, value 1 indicates that consecutive identical characters are not allowed in a password.
- (Optional) Enable the Disallow previously used passwords option and set the number of previously used passwords that are not allowed. For example, value 3 indicates that the user cannot set the last three passwords that the user has previously used when setting a new password.
- Changes to the password policy take effect the next time you or your IAM users change passwords. IAM users created later will also adhere to the updated password policy.
+ Changes to the password policy take effect the next time you or your IAM users change passwords. The new password policy will also apply to IAM users created later.
Password ExpirationSet a validity period for passwords so that users need to change their passwords periodically. The users will be prompted to change their passwords 15 days before password expiration. Expired passwords cannot be used to log in to the cloud platform.
This option is disabled by default. The validity period ranges from 1 to 180 days.
@@ -17,7 +17,7 @@
After the password expires, users need to set a new password through the URL sent by email. The new password must be different from the old password.
Minimum Password AgeTo prevent password loss due to frequent password changes, you can set a minimum period after which users are allowed to make a password change.
- This option is disabled by default. If you enable this option, you can set a period from 0 to 1440 minutes.
+ This option is disabled by default. The validity period ranges from 0 to 1,440 minutes.
The changes will take effect immediately for your account and all IAM users under your account.
diff --git a/docs/iam/umn/iam_01_0653.html b/docs/iam/umn/iam_01_0653.html
index ad55d311..d01abaf5 100644
--- a/docs/iam/umn/iam_01_0653.html
+++ b/docs/iam/umn/iam_01_0653.html
@@ -8,7 +8,7 @@
To reset the login password of an IAM user, click Security Settings in the row containing the user, click next to Login Password in the Login Credentials area, and select a password type.
- You can reset the password of an IAM user on the Security Settings page.
- IAM users can change their passwords on the Basic Information tab.
- - Set by user: A one-time login URL will be emailed to the user. The user can then click on the link to set a password.
- Automatically generated: A password will be automatically generated and then sent to the user by email.
- Set now: You set a new password and send the new password to the user.
+ - Set by user: A one-time login URL will be emailed to the user. The user can then click on the link to set a password.
- Automatically generated: A password will be automatically generated and then sent to the user by email.
- Set now: You set a new password and send the new password to the user.
diff --git a/docs/iam/umn/iam_01_0655.html b/docs/iam/umn/iam_01_0655.html
index c416fa86..ed08e97c 100644
--- a/docs/iam/umn/iam_01_0655.html
+++ b/docs/iam/umn/iam_01_0655.html
@@ -1,18 +1,15 @@
-
- User Groups and Authorization
-
-
+ User Groups and Authorization
+
-
|
|---|
|
|---|
|
