Skip to content

User Manager

← Documentation index

User Manager is RouterOS's RADIUS server. Many networks run it on a CHR or router so that switches, firewalls and access points (MikroTik or not) authenticate logins against one place. The User Manager page, under Services, shows it for the whole network (#251). It's in the sidebar only once a device in the selected site is found running it.

Which devices are shown

Every device is checked once a day for User Manager: the user-manager package installed and switched on. Devices without it cost one call a day. A device found running it gets a User Manager badge on its page, linking here. If you've just switched it on, press Sync on that device's page: Sync always checks, and the badge and the sidebar link appear when it's done.

With more than one server (two for redundancy, or one per site), a picker at the top switches between them. The list follows the site selected at the top of the sidebar.

What it shows

Read live from the server when the page opens, and every minute while it's open. Nothing it holds is copied into the manager's database.

  • Logged in now: active sessions: user, the device they logged in through (linked when it's a device the manager manages), where from, when, and traffic.
  • Users: name, group, how many sessions each may have at once, and any attributes set on the user itself.
  • Groups: the RADIUS attributes each group sends, shown as name value pairs. These are what firewalls and switches authorise on, for example Cisco-AVPair shell:priv-lvl=15 or PaloAlto-Admin-Role superuser.
  • Devices that authenticate against it: each RADIUS client, its address, and whether it's a device in the manager (linked) or not.
  • Recent sessions: the latest 100 that have ended, with why (user-request, a session limit, a timeout).

Passwords and secrets never leave the server. User passwords, OTP secrets and the shared secrets of the devices are left out of every read, on the backend, whatever RouterOS returns. Edits write them and never read them back.

Clearing a stuck session

A session stays open in User Manager when the device never reports the logout (it rebooted, or lost contact). For a user allowed only one session, that blocks the next login. Clear on the session removes the record from User Manager. It doesn't log anyone off the device itself. It needs operator access or above.

Users

Admins (of the server's site) can add, edit, disable and remove users (#360): username, password, group, how many sessions at once, a comment, and RADIUS attributes. Passwords are written to the server and never read back; leave the field empty when editing to keep it.

VLAN for 802.1X puts the user in a VLAN when they log in on an 802.1X port: it sets the three attributes RouterOS's 802.1X reads (Tunnel-Type:13, Tunnel-Medium-Type:6, Tunnel-Private-Group-ID:<vlan>) alongside any others you give.

802.1X with User Manager

Use for a switch's 802.1X, under the devices that authenticate against it, links a managed switch or router in one step. A new random shared secret is set on both ends:

  • User Manager accepts the switch, at its management address unless you give another. A switch already listed at that address gets the new secret.
  • The switch gets a RADIUS server for 802.1X at User Manager's management address (or the one you give), or its existing entry there takes the new secret. This runs under Change Guard.

Then turn 802.1X on for the switch's ports on its 802.1X tab. Give each address as the other end sees it: when the switch reaches User Manager through NAT or another interface, enter that address.

Limits

  • Groups and their attributes are read-only here; edit them in RouterOS.
  • Failed logins aren't shown here: User Manager doesn't keep them as session records, only in the server's log.