Sign-in and MFA
On the Sign-in page of the Admin App you choose how the users of your Tenant sign in. You need the Right to manage sign-in for it. Admins hold it.
Each setting is saved as soon as you change it. It applies from each user’s next sign-in, and at the latest after 15 minutes, when the apps renew their sign-in.
The settings
Section titled “The settings”| Setting | What it does |
|---|---|
| Allow sign-in with a password | Users sign in with their email and a password. It stays on until your Tenant signs in with SSO, so that nobody is locked out. |
| Require two-step verification for password users | Everyone who signs in with a password also enters a code from an authenticator app. See below. |
| Allow passwords for users of other domains | Users whose email isn’t in one of your Verified Domains, such as guests and contractors, may keep signing in with a password. It takes effect once your Tenant signs in with SSO. |
Require two-step verification
Section titled “Require two-step verification”- In the Admin App, select Sign-in.
- Select Require two-step verification for password users.
Users who have already set up two-step verification notice nothing. Everyone else is asked to set it up at their next sign-in, before they can do anything else in your Tenant. If they belong to another Tenant that doesn’t require it, they land there instead and are asked to set it up when they switch to yours. That includes you: set it up for your own account first.
To stop requiring it, clear the same checkbox. Users keep two-step verification once they set it up, until they turn it off themselves.
The look of the login pages
Section titled “The look of the login pages”The pages where users enter their password, reset it, sign up from an invitation or enter their two-step code use the apps’ colors, shapes and focus rings, in light or dark to match the browser. The look is code, not a setting: it is the same for every Tenant, and nobody changes it in Cognito’s own web interface. The runbook The login page’s look in the repository has the steps in detail.
Change it in code
Section titled “Change it in code”- Change a design token of the apps, or the layout in the generator for the login style (
build_settingsininfra/src/infra/login_branding/generate.py). - Run
npx nx run infra:generate-login-brandingand commit the settings and assets it writes. - Run
npx nx run infra:test. It fails when the committed files are stale, and when any text, button, border, focus ring, icon or error color is below WCAG 2.2 AA, in light and dark.
The change goes out with the next deploy, and a PR Environment shows it. To use a real logo, put the file in the assets folder under the name of an existing entry. Until then the pages show a placeholder wordmark made from the tokens.
What the login pages can’t match
Section titled “What the login pages can’t match”- Fonts: the pages use Cognito’s font. There is no setting for another.
- Shadows, transitions and any other CSS: not possible.
- Radii: one value each for buttons, inputs, drop-downs, forms and alerts.
- Dark mode follows the browser, not the theme a user picked in the apps.
- A few colors are raised to meet WCAG 2.2 AA where an app’s token falls short: the hairline input border, muted text, the focus ring, errors and link hover.
- There is no success color: success indicators are neutral.
- There is no header and no footer, and none of Cognito’s stock illustrations.
Which clients show a page
Section titled “Which clients show a page”- The browser client, which the apps sign in through, shows every page and has the style.
- Each Tenant’s SSO skips the password form, but its sign-in page and the error pages still exist, and they have the style too. It is made with the SSO setup and deleted with it.
- Signing up from an invitation and stopping a Turn never show a login page.
Language
Section titled “Language”The pages come in English and German like the apps. Cognito serves the text itself and picks the language from the app’s sign-in link, or from the browser’s language without it. The style can’t change a word of the text.
If someone edits the style in Cognito’s web interface
Section titled “If someone edits the style in Cognito’s web interface”Every deploy applies the committed style again, so an edit of any value the style sets is gone after the next deploy. A style made by hand for a client that the platform styles blocks the deploy: delete it first.
What the Audit Log shows
Section titled “What the Audit Log shows”Every change of a setting leaves an entry in the Audit Log with the setting’s name, who changed it and when. It doesn’t record the value.