Permissions
Login
Each person logs in with an account of their own. The login form has two fields: Username and Password. The button below is called Login. If two-factor login is set up for the account, Moliri then asks for the code from the app in a second step, or waits for the confirmation on the phone (see Two-factor login ).
If a single sign-on provider is set up for the instance, the card also shows OR below it and a Login with … button for each provider. Without a provider set up, neither appears.

Login name and password
An administrator sets the login name and the first password in Permissions › Users. With Password reset on next login, the person has to choose their own password the next time they log in. A new password has to pass a strength check before it can be saved.
Everyone can change their own password in their profile (on the right of the main menu, under their own name).
Two-factor login
Moliri supports logging in with a second factor: a one-time password from an authenticator app (TOTP) that changes every few seconds, or the person’s own phone. A phone that was set up confirms a login on the phone itself with its screen lock, and a login on another device with a tap on the matching number (see Confirming with the phone ). App and phone can be set up on their own or together.
| Where | Who | What |
|---|---|---|
| Profile, 2-Factor authentication | The person themselves | Set up: scan the QR code with the app, enter the code shown, save. Remove switches the second factor off |
| Permissions › Users, on the account | An administrator | Switch off only: Remove, for example when the phone with the app is lost |
| Profile, Phone as second factor | The person themselves, on the phone | Set up with a passkey and the phone’s screen lock, also without the app. Remove per device |
| Permissions › Users, on the account, Phone as second factor | An administrator | See the account’s phones and Remove one, for example when it is lost. If confirming on the phone is paused after denied requests, it says until when, and Lift pause lifts the pause. Only the person themselves can set up a phone |
Each person can set up two-factor login only for themselves. An administrator cannot set it up for another account; for an account without a second factor the dialog shows Not set up and points to the profile.
Once an account has a second factor, Moliri does not allow a login without a valid code from the app or the confirmation on the phone. If the app is set up, the account shows Set up under 2-Factor authentication. After Remove the account signs in with the password alone again (or, if a phone is set up, with the phone), until the person sets up the second factor anew in their profile.
Logging in in two steps
The person first enters username and password. If the password is right, Moliri shows a second step: Confirm it’s you with a field for the six-digit code from the app. Confirm logs in. Back to sign-in starts the login again. If a phone is set up, the second step first shows Confirm on your phone; from there Enter a code instead leads to the field for the code (see Confirming with the phone ).

| Situation | Behaviour |
|---|---|
| Wrong code | Moliri says that the code did not work, and the second step stays open. A wrong code counts as a failed attempt, like a wrong password |
| Three wrong codes | The second step ends. The login starts again at username and password, with the note Please sign in again |
| No code within five minutes | As above: the login starts again |
| A code that was used before | Refused. Each code can be used only once, even while it is still valid |
| Wrong password | The second step does not appear. The login fails as for an account without a second factor |
Until the second step is passed, nobody is logged in. The second step only works in the browser in which the password was entered.
If the app cannot read the QR code, Moliri shows the key as text to type in.
Confirming with the phone
A phone that was set up keeps a passkey for Moliri in its own password manager. How the person sets up the phone is described under Profile .
When the person logs in on the phone itself, the second step shows Confirm with this device. The screen lock (fingerprint, face or PIN) confirms, and the person is logged in.
When they log in on another device, for example on the computer, the second step shows Confirm on your phone with the phone’s name (for example “iPhone · Safari”), a large two-digit number and the time left: the request is valid for two minutes. Below it are No notification? Open Moliri on your phone: the request shows there., Enter a code instead (if the app is set up) and Use the passkey of this device.
If the person switched notifications on on the phone, it speaks up at once with Confirm sign-in?, even when Moliri is closed there or the phone is locked (see Notifications to the phone ); a tap opens Moliri with the request. Otherwise the phone shows the request when Moliri is opened there, when it comes back to the foreground, and every ten seconds while Moliri is visible. For this, Moliri has to be signed in on the phone with this device: in the browser in which the phone was set up, or after a login with Confirm with this device. The request asks Are you signing in? and names the instance, the browser and system of the asking device (for example “Windows · Chrome”), its IP address (with local network added for addresses in your own network) and the time with the time left. Below are three numbers and That wasn’t me. The person taps the number the computer shows and confirms with the screen lock. The phone shows Confirmed, and the computer is logged in within two seconds.
When an account is taken over for single sign-on, the phone asks Link a single sign-on to your account?, and when confirming again before a change in the profile Confirm a change to your sign-in? (see Single sign-on ).
| Situation | Behaviour |
|---|---|
| Wrong number tapped | The phone shows Wrong number: sign-in stopped. The computer returns to the password and reports Sign-in denied on your phone: “Another number was tapped on the phone …” |
| That wasn’t me | The phone shows Sign-in denied and says that whoever tried to sign in knows the password; Change password leads to the profile. The computer returns to the password and reports Sign-in denied on your phone |
| Two minutes without an answer | The computer says that the request ran out and offers Send a new request. The code from the app keeps working until the second step ends after five minutes |
| A second login while a request is waiting | One request waits per account: the new login replaces the older request. On the other device the code from the app still works |
| Three denials or wrong numbers within an hour | Confirming on the phone is paused for an hour. Logging in then works with the code from the app, or on the phone itself with Confirm with this device. The profile gives the time until which the pause lasts. An administrator lifts it in Permissions › Users on the account under Phone as second factor with Lift pause |
| Phone lost | The person removes it in their profile, or an administrator removes it under Permissions › Users. Without the app and without a second phone, only an administrator can let the person in again: they remove the phone, and the account signs in with the password alone until a second factor is set up again |
| Passkey refused (another account, no screen lock, expired) | Counts as a failed attempt, like a wrong code. After three failed attempts the login starts again |
| Phone removed (by the person or under Permissions › Users) | The logins on that phone end at once, and so do logins waiting for their second step. The app stays set up |
| 2-Factor authentication removed while a phone is still set up | The phone stays the second factor: every login on another device waits for the confirmation on the phone |
| New password, app removed, account expired or status changed | Logins waiting for their second step end and start again |
| Account that must use single sign-on | No phone as second factor: the provider checks the second factor |
A phone can also be set up without the app. The app or a second phone keeps a way in open if the phone is lost, without the administration having to help. The passkey works only for the address of the instance where it was created.
Under System › History (Approval devices), setting up and removing are listed with the device’s name, browser and address; for a removal also whether the person or an administrator did it. Every approval, denial and wrong number is listed there too, with the phone’s name and the browser and address of the asking device, as is every pause and every lifted pause.
Notifications to the phone
Each person switches notifications on on their set-up phone in the profile (see Profile ). When a login, the takeover of an account for single sign-on or the renewed confirmation before a change then waits for the phone, Moliri sends a notification to every phone of the account that has notifications on. It goes through the push service of the phone’s maker (Google, Apple, Mozilla, Microsoft), carries a number only and is valid for two minutes, as long as the request. On iPhone and iPad it only reaches Moliri on the home screen, iOS 16.4 or later.
| Situation | Behaviour |
|---|---|
| Switching notifications off for the whole instance | System › Settings, section Security, Sign-in: switch off Notifications to the phone. Then no notification leaves the server; the phone shows the request only when Moliri is opened there. The profiles say so. Switched on again, notifications reach everyone who had them on |
| Push service slow or unreachable | The login does not wait for it: Moliri sends the notification after the computer has its answer. The phone then shows the request when it is opened |
| Push service reports the phone as no longer reachable | Moliri forgets that phone’s notifications; the person switches them on there again |
Single sign-on
Moliri can leave login to a provider of your institution, through OpenID Connect (OIDC). Moliri sets up the provider for the instance; there is no setting for it in the interface. Part of this is a pattern for login names, for example all addresses of one domain.
| Situation | Behaviour |
|---|---|
| The username entered matches the pattern | Password, one-time password and Login disappear, and the Login with … button takes their place |
| New account whose login name matches the pattern | Needs no password. The dialog says No password needed, sign-in via … |
| An account without a password logs in through the provider for the first time | The account is linked to the provider. From then on single sign-on is mandatory for this account, and password login is blocked |
| New account matching the pattern but with a password set anyway | The person enters the password once to take the account over for login through the provider. The dialog warns about this. If the account has a second factor, a second step with the code from the app or the confirmation on the phone follows, as at login |
| Existing account with a password | In the profile, under Single Sign-On (SSO), you can add a login through the provider |
Anyone who adds or removes a login through a provider in their profile confirms this first with their password and, if applicable, a one-time password. With a phone set up, the field for the one-time password stays empty: the dialog then shows the number and waits for the confirmation on the phone, and Enter the code instead leads back to the field. The only login of an account for which single sign-on is mandatory cannot be removed.
Whether single sign-on is set up for an instance, and with which provider, is something your institution arranges with Moliri at [email protected] .
Lockout and validity
| Setting | Effect |
|---|---|
| Failed login attempts | Wrong passwords and wrong codes count together. After each failed attempt the next login waits a little longer. After too many failed attempts the account is locked. An administrator unlocks it with Reset |
| Pause of the confirmation on the phone | Separate from the lockout: after three denials or wrong numbers within an hour, only confirming on the phone is paused for an hour; the account stays open. Denials do not count as failed attempts. Lift pause under Phone as second factor lifts the pause, not Reset |
| Valid until | From this day on, logging in is no longer possible. For internships, freelance contracts and external staff |
| Last login | Shows when the account was last used |
There is no automatic logout after a period of inactivity.
Further reading
- Creating a user : setting up the account
- Roles and status : what an account may do
- Operation : instance, backup, hosting