Login control is used to configure the behavior of the end-user login and Register pages, including page layout, account identifier, and authentication methods. Through flexible settings, you can customize the user login experience to meet different business scenario requirements.
Path: Log in to the RootAuth console → Navigate to the target application → Click Configuration in the top navigation bar → Select Application – Application Management → Login Control
1. General Login Settings
The table below lists the core configuration items in Login Control and their current status:
| Configuration Item | Description | Current Status |
|---|---|---|
| Register/Login Pagination | Login and Register are on two separate pages; users must register first before logging in. | Fixed, cannot be modified |
| Account Field | The account identifier type used for user login/Register. | Fixed to Email |
| Authentication Methods | The login verification methods available to users. | Optional: Password, Verification Code |
1.1 Authentication Method Selection Rules
-
At least one authentication method must be selected; otherwise, the configuration cannot be saved.
-
If both Password and Verification Code are selected, the login page will provide tab switching, allowing users to freely choose their login method.
-
If only one of them is selected, the login page will display only that login method (e.g., password‑only login or verification‑code‑only login).
2. Try Register/Login
After completing the application configuration, you can click the Try Register/Login button in the upper‑right corner of the page to preview the effect of the current login and Register pages.
The preview page strictly follows the following configurations:
-
Authentication methods selected in Login Control
-
Logo and application name configured in Application Configuration
-
Register security settings configured in Security Settings (such as CAPTCHA, Register restrictions, etc.)
-
Grant types configured in Protocol Configuration (affects only the OIDC flow; the preview page does not involve authorization interactions)
This feature allows you to quickly verify whether the configuration meets expectations, ensuring a smooth experience before going live.
Note: After changing the application configuration, it may take up to 2 minutes for the changes to take effect on both the preview page and the end‑user page.
