Complete real-name verification¶
Where enabled, verification checks your real name against the account’s currently verified phone number. Complete it when requested by access-credential management or a console call entry, then return to that entry.
Check before you begin¶
Check the phone number in Account settings and verify it first if needed. The real-name dialog uses that current number rather than a different number entered in the dialog. Phone verification and real-name verification are distinct states.
Availability can vary by deployment. If the account page does not expose this feature, ask the deployment administrator. A bound phone number does not establish successful identity verification.
Submit authentication¶
Open Account settings from the account menu.
Open real-name verification and check its current status.
Confirm the displayed phone number.
Enter the matching real name and confirm verification.
Wait for Verified, then return to the original operation.
Check state and processing failures¶
State or prompt |
Next step |
|---|---|
Identity unverified |
Follow page instructions to submit your real name and currently verified phone number. |
Authentication is in progress or verification is not confirmed |
Use the page’s refresh or authentication-state retry entry to check the original request result first. |
Name or phone number mismatch |
Check the current phone number and name, correct the profile, then submit again. |
Service temporarily unavailable or rate-limited |
Follow the specific prompt, retain operation time/error information, and avoid repeated submissions. |
Availability varies by deployment. Do not assume a verified phone means real-name verification passed. API, SDK, and CLI calls still need valid credentials and resource permissions. Keep names, full numbers, codes, and keys out of screenshots.