Customization
Entrust Identity as a Service lets you tailor the authentication experience to match your organization's brand, language, and workflow requirements. You can control visual appearance, login page text, layout structure, legal notices, and sign-in behavior across your tenant.
Topics in this section
Brand login pages
Use custom branding on login pages to match your organization's standards. This is required for white-label deployments where Entrust Identity as a Service branding cannot be shown.
Configure layout and flow
Layout controls let you tailor the visual structure of the login experience, including card style, announcement placement, and sign-in flow order, without changing your brand assets. Use these settings to match your design system, highlight important notices, and streamline the authentication flow for your users.
Customize text and messages
IDaaS displays default text on login, registration, password-reset, and error pages. IDaaS already provides translations for all supported locales, so the default text works out of the box in every language. However, you can override any string with your own wording. For example, you can override the string to use organization-specific terminology ("Employee ID" instead of "User ID"), add your helpdesk contact information to error messages, or meet regulatory requirements for specific wording.
Configure languages
When the login page language selector offers all available locales but your organization only operates in a subset of those languages, users may select a locale that is not relevant to your deployment. Restricting the language selector to only the locales your organization uses keeps the experience clean and focused.
Configure footer and notices
Regulated industries and white-label deployments require control over the legal notices displayed during authentication. By default, IDaaS login pages display Entrust's copyright, Terms of Service link, and Privacy Statement link in the footer. You can replace these with your organization's own legal references, or remove the footer entirely for kiosk or embedded use cases.
Optimize application login flow
By default, IDaaS presents the username on one page and the password on the next. For password-based authentication, this multi-step flow adds an extra page transition and increases friction. Combining username and password on a single page reduces friction and prevents user ID enumeration. When both fields are submitted together, an attacker cannot determine whether an account exists based on the server's response.