Sessions and security
You can sign out a lost device in Preferences. An admin can sign someone out of all their devices at once.
Your sessions
Everyone can see which devices they’re signed in on.
- Click your avatar in the lower left and select Preferences.
- Open Sessions.
- If you see a device you don’t recognize, click Sign out device next to it.
Your current device is labeled This device.
Sign someone out
If someone loses a laptop or phone:
- Click Admin and select Members.
- Open Actions next to their name and select Sign out of all devices.
This ends all of the person’s sessions. They can sign in again.
Change your password
Click your avatar, then Security and Change password. Enter your current password, then type your new password twice. Changing your password signs you out of your other devices.
Password requirements
- Passwords must be at least 12 characters long (
auth.password_min_length). - Gadka rejects passwords found in known data breaches. The server includes the list, so it can check passwords offline.
Protection against password guessing
| Limit | Default | Configuration key |
|---|---|---|
| Failed login attempts per account | 5 per 15 minutes | ratelimit.login_per_account |
| Login attempts from one IP address | 10 per minute | ratelimit.login_per_ip |
If you exceed a limit, the app shows Too many sign-in attempts. Try again in … s.
The api.trusted_proxies setting lets the server distinguish between client IP addresses. The installer adds it in version 0.3.2 and later. If you installed an earlier version, add it to the configuration file.
Session lifetime
| Setting | Default | What it means |
|---|---|---|
auth.refresh_ttl | 30 days | A session expires after this much inactivity. |
auth.session_max_age | 90 days | After this time, you must sign in again. |
Account protection with 2FA
- Anyone can enable 2FA on their account.
- Owners and admins must enable it to use the administration pages.
Server keys
| File | What happens if it is lost |
|---|---|
/etc/gadka/mfa-key | Existing 2FA setups stop working. Users must sign in with recovery codes and set up 2FA again. |
/etc/gadka/jwt-signing-key.pem | Everyone is signed out. |
Keep copies of both files in a password vault.
Include both keys in your server backup. If someone loses access to their account, check what is preventing them from signing in.