Notifications
Clear all
Topic starter
05/07/2026 10:33 pm
TL;DR: Customising login, consent, email, password validation, and right-to-left language support across the Curity Identity Server is possible, according to Curity. The practical issue is not visual polish, but how identity journeys, accessibility, and client-specific behaviour are governed without weakening control.
NHIMG editorial — based on content published by Curity: Branding and User Experience
By the numbers:
- NHIs outnumber human identities by 25x to 50x in modern enterprises.
- Only 5.7% of organisations have full visibility into their service accounts.
- 91.6% of secrets remain valid five days after the targeted organisation is notified, showing a critical gap in remediation procedures.
Questions worth separating out
Q: How should IAM teams govern branded login experiences without creating policy drift?
A: Treat branding as a presentation layer and policy as a governed control layer.
Q: Why do customised consent screens create governance risk if they are not standardised?
A: Because consent language is part of the trust boundary the user sees.
Q: How do localisation and right-to-left support affect identity security?
A: If identity journeys do not render correctly in the user’s language and layout direction, people can misread prompts, fail to complete secure actions, or bypass the intended flow through support workarounds.
Practitioner guidance
- Separate presentation from policy enforcement Keep branding, layout, and copy in the identity experience layer while preserving a single source of truth for authentication, consent, and password rules.
- Standardise consent language across applications Define approved scope descriptions and user-facing consent text for each application class, then review deviations through IAM, legal, and privacy owners before release.
- Test localisation as part of identity assurance Run login and consent journeys in supported right-to-left and left-to-right formats, with real content and error states, before rollout.
What's in the full article
Curity's full article covers the operational detail this post intentionally leaves for the source:
- Step-by-step examples for building custom login screens and consent experiences in the Curity Identity Server.
- Implementation notes for multi-brand branding patterns and user-facing variations across client applications.
- Guidance on right-to-left language support and email customisation for global identity journeys.
- Password validation and UI kit examples that show how the frontend and backend pieces fit together.
👉 Read Curity's guide to branding and user experience in the Identity Server →
Login and consent customization: what IAM teams should consider?
Explore further
05/07/2026 10:46 pm
Identity user experience is a governance surface, not a cosmetic layer. When organisations customise login, consent, and email flows, they are changing how policy is interpreted by users. The underlying identity controls may remain intact, but inconsistent presentation can still produce inconsistent behaviour, especially across multiple applications and brands. The practitioner conclusion is simple: UX decisions belong in identity governance reviews, not only in design reviews.
A few things that frame the scale:
- 91.6% of secrets remain valid five days after the targeted organisation is notified, showing a critical gap in remediation procedures, according to Ultimate Guide to NHIs.
- Only 5.7% of organisations have full visibility into their service accounts, which is why presentation-layer changes should never be mistaken for governance maturity.
A question worth separating out:
Q: What should teams check before deploying multi-brand login flows?
A: Check that every branded flow uses the same underlying authentication policy, session rules, and account-state messaging. Multi-brand design is acceptable when it changes appearance, not behaviour. If the journey changes materially by app, the programme has likely introduced avoidable identity inconsistency.
👉 Read our full editorial: Curity's branding and UX options reshape login and consent flows
