Sign-in and identity

Aegis — sign-in and identity

Aegis is where people sign in. Other platforms ask Aegis who someone is before they trust that person.

For your technology team. Aegis is the central sign-in and identity service for every Trudi platform: the user directory, sign-in, multi-factor and one-time codes (MFA/OTP), the shared names for permissions, and the security log. Other platforms check the identity proof (token) it issues. Aegis does not hold the customer record (CIF) or ledger data.

What it does

  • Holds the directory of people and systems that may sign in.
  • Checks a password, a one-time code, or a stronger step-up when a sensitive action needs it.
  • Keeps the session and can end it.
  • Supports single sign-on so one identity can open more than one platform.
  • Issues the proof other platforms use to know who is calling.
  • Keeps the security log of sign-in and access events.
  • Does not store account balances or the customer file.

Who uses it

Everyone who signs in to a Trudi platform, and the security team that reviews the access log.

Detail for your technology team

  • Directory of the people and systems that may sign in
  • Sign-in, multi-factor checks, and a stronger step-up check for sensitive actions
  • Shared names for permissions, and session management
  • A security log that shows who did what, across platforms

How it connects

Aegis CONNECTS TO Atlas Aegis asks Atlas which of its own modules are switched on, where that is controlled All platforms Check the identity proof (token) that Aegis issues or passes through its identity interface Relay Access tickets can hand off into identity workflows (Relay does not keep the official identity record) Customer channels and money platforms Nova, Titan, and others rely on Aegis on controlled paths
Connections named on this page, with the platform marks. The diagram does not show balances or a live screen.
  • AtlasAegis asks Atlas which of its own modules are switched on, where that is controlled
  • All platformsCheck the identity proof (token) that Aegis issues or passes through its identity interface
  • RelayAccess tickets can hand off into identity workflows (Relay does not keep the official identity record)
  • Customer channels and money platformsNova, Titan, and others rely on Aegis on controlled paths

What it is not

The bank’s customer master file (CIF); the ledger; the customer screens; feature permissions and emergency stops (Atlas).