Default Hosted Pages
The default hosted pages provided by cidaas allow you to instantly use cidaas and customise the login, registration, and many more pages at the push of a button.
Of course, you can also build your own Login and Registration Pages if you want.
In this section, we are introducing the default hosted pages.
The Definition of a Hosted Page
Hosted Pages in Cidaas refer to customizable and pre-built web pages that serve as an integral part of the authentication and user management processes. They are also pages in Cidaas where users are automatically redirected.
Let's understand this with an example:
If you call the authz Endpoint cidaas does decide whether the user is still logged in (has an active session) or needs authentication. In case authentication is required, cidaas will automatically direct the user to the login page, so here the login page is hosted.
All redirection done on frontend are not hosted page.
Customize the Default Hosted Pages
Having the User Interfaces branded in your design is essential. Thereby, the user can immediately recognise you.
Setup of Hosted Pages
The hosted pages setup is explained in more detailed under Hosted Pages
| Field | Description |
|---|---|
| App Name | defines the internal app name that is displayed in the Admin Dashboard and App Developer Portal. |
| App Display Name | defines the name presented on the Login Page. |
| App Logo URL | defines the logo that is presented on the default hosted pages (e.g., login page, registration page). |
| Logo Position | defines the alignment of the logo. Possible values are center, right, and left. |
| Login Form Position | defines the alignment of the login form. Possible values are center, right, and left. |
| Media Type | defines the type of the background image. |
| App Background URL | defines the image presented in the background of the hosted pages. |
| App Primary Color | defines the primary color to render e.g texts and borders. |
| App Accent Color | defines the accent color used e.g. to display the verification methods. |
Client Management
To find out how to setup the complete client configuration, please go to Client Management
Overview of Hosted Pages
| hosted page Id | Description |
|---|---|
| Login | Those pages might result from calling the authz-srv or login-srv endpoints and are related to login. |
| login | This page is redirected if the user needs to login. |
| login_success | This page is displayed after a user logs in successfully and login_success is enabled in this app (App Settings). |
| register_additional_info | The user will be redirected to this page in case further information is required by this app (Progressive profiling). |
| consent_preview | the consent_preview is displayed when the user needs to provide a consent that is mandatory for this application |
| consent_scopes | The consent_preview is displayed when the user needs to provide a scope consent that is mandatory due to scope being required as user consent or when it is a THIRD_PARTY client |
| Register | The registration pages are presented when the users-srv is called during registration. |
| register | This is presented if view_type is register for an authz call. |
| register_success | No automatic redirection will happen here, but it will be returned as redirect_uri in the response body of the register Call |
| account_deduplication | No automatic redirection will happen here, but it will be returned as redirect_uri in the response body of the register call |
| Password | |
| password_forgot_init | No automatic redirection will happen here, this is a hosted page included in our default hosted page webapp |
| password_set_success | We introduced an automatic redirection to password_set_success, so after completing, you can set a new password (using the forgot password flow). |
| password_set | In case of using /validatecode, we introduced an automatic redirection to password_set page |
| Verification | The verification pages are related to passwordless authentication |
| verification_init | The redirection to verification_int page will take place in case of calling the initiate verification api but no userId was provided that matches the reset medium or in case of "email_not_verified" or "mobile_not_verified" |
| verification_complete | After initiating a authentication using CODE-Flow the user will be prompted to verification_complete page. |
| mfa_required | No automatic redirection will happen here, this is a hosted page included in our default hosted page webapp |
| Logout | |
| logout_success | No automatic redirection will happen here, this is a hosted page included in our default hosted page webapp |
| Error | |
| error | The error page can be client specific, and might show in case of invalid or expired parameters are overhanded to cidaas. Thereby we ensure a proper styling. in case of no client can be determined the error page of the default hosted page group is used. |
| Device Code Flow | Those pages are related to the device code flow, so login on a users device like a smart TV |
| device_init_code | The init page is presented during the initiation of the device code flow |
| device_success_page | If the user logs in successfully using the device code flow, this device success page is displayed |
Help and support
Please contact us directly on our support page.