After an IDaaS user logs on to the IDaaS application portal, the user can view and edit the basic information of the current account on the My Account page.
The following table describes the fields on the page.
Field | Description |
Account name | The name of the account that is used to log on to the portal. The account name uniquely identifies the account and can be changed later. Note: The initial account name is left empty for an account that is imported from DingTalk. You must specify the account name when you create an account in IDaaS. |
Display name | The alias of the account. |
Mobile number | We recommend that you specify this parameter. This parameter is required in scenarios such as logon, password resetting, and 2FA. Note: If you bind neither a mobile number nor an email address, you cannot perform 2FA. |
Email address | We recommend that you specify this parameter. This parameter is required in scenarios such as logon, password resetting, and 2FA. Note: If you bind neither a mobile number nor an email address, you cannot perform 2FA. |
Password | The administrator can determine the password complexity. |
Bind third-party account | Bind external enterprise identities that users can use to log on to the IDaaS portal. You can bind and unbind accounts. Accounts that are imported from the identity provider are bound to IDaaS by default and cannot be unbound. Note: IDaaS supports DingTalk identities. In the future, IDaaS will support more enterprise identities, such as WeCom, Lark, and AzureAD. |
Bind OTP | After the administrator enables 2FA based on one-time password (OTP), the user can use this field to bind OTP. |