Manual:Router AAA: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 40: | Line 40: | ||
<li><var>telnet</var> - policy that grants rights to log in remotely via telnet | <li><var>telnet</var> - policy that grants rights to log in remotely via telnet | ||
<li><var>ssh</var> - policy that grants rights to log in remotely via secure shell protocol | <li><var>ssh</var> - policy that grants rights to log in remotely via secure shell protocol | ||
<li><var>ftp</var> - policy that grants | <li><var>ftp</var> - policy that grants full rights to log in remotely via FTP and to transfer files from and to the router. Users with this policy can both read, write and erase files, regardless of "read/write" permission, as that deals only with RouterOS configuration. | ||
<li><var>reboot</var> - policy that allows rebooting the router | <li><var>reboot</var> - policy that allows rebooting the router | ||
<li><var>read</var> - policy that grants read access to the router's configuration. All console commands that do not alter router's configuration are allowed | <li><var>read</var> - policy that grants read access to the router's configuration. All console commands that do not alter router's configuration are allowed. Doesn't affect FTP | ||
<li><var>write</var> - policy that grants write access to the router's configuration, except for user management. This policy does not allow to read the configuration, so make sure to enable read policy as well | <li><var>write</var> - policy that grants write access to the router's configuration, except for user management. This policy does not allow to read the configuration, so make sure to enable read policy as well | ||
<li><var>policy</var> - policy that grants user management rights. Should be used together with write policy | <li><var>policy</var> - policy that grants user management rights. Should be used together with write policy | ||
Revision as of 08:59, 25 February 2010
Applies to RouterOS: 2.9, v3, v4
Summary
Sub-menu: /user
MikroTik RouterOS router user facility manage the users connecting the router from the local console, via serial terminal, telnet, SSH or Winbox. The users are authenticated using either local database or designated RADIUS server.
Each user is assigned to a user group, which denotes the rights of this user. A group policy is a combination of individual policy items.
In case the user authentication is performed using RADIUS, the RADIUS Client should be previously configured.
User Groups
Sub-menu: /user group
The router user groups provide a convenient way to assign different permissions and access rights to different user classes.
Properties
| Property | Description |
|---|---|
| name (string; Default: ) | The name of the user group |
| policy (local | telnet | ssh | ftp | reboot | read | write | policy | test | web; Default: ) | group policy item set
|
Sensitive information
Starting with RouterOS v3.27, the following information is regarded as sensitive, and can be hidden from certain user groups with the 'sensitive' policy unchecked.
Also, since RouterOS v4.3, backup files are considered sensitive, and users without this policy will not be able to download them in any way.
system package
/radius: secret /snmp/community: authentication-password, encryption-password
advanced-tools package
/tool/sms: secret
wireless package
/interface/wireless/security-profiles: wpa-pre-shared-key, wpa2-pre-shared-key, static-key-0, static-key-1, static-key-2, static-key-3, static-sta-private-key /interface/wireless/access-list: private-key, private-pre-shared-key
wireless-test package
/interface/wireless/security-profiles: wpa-pre-shared-key, wpa2-pre-shared-key, static-key-0, static-key-1, static-key-2, static-key-3, static-sta-private-key, management-protection-key /interface/wireless/access-list: private-key, private-pre-shared-key, management-protection-key
user-manager package
/tool/user-manager/user: password /tool/user-manager/customer: password
hotspot package
/ip/hotspot/user: password
ppp package
/ppp/secret: password
security package
/ip/ipsec/installed-sa: auth-key, enc-key /ip/ipsec/manual-sa: ah-key, esp-auth-key, esp-enc-key /ip/ipsec/peer: secret
routing package
/routing/bgp/peer: tcp-md5-key /routing/rip/interface: authentication-key /routing/ospf/interface: authentication-key /routing/ospf/virtual-link: authentication-key
routing-test package
/routing/bgp/peer: tcp-md5-key /routing/rip/interface: authentication-key /routing/ospf/interface: authentication-key /routing/ospf/virtual-link: authentication-key
Notes
There are three system groups which cannot be deleted:
[admin@rb13] > /user group print 0 name="read" policy=local,telnet,ssh,reboot,read,test,winbox,password,web,!ftp,!write,!policy 1 name="write" policy=local,telnet,ssh,reboot,read,write,test,winbox,password,web,!ftp,!policy 2 name="full" policy=local,telnet,ssh,ftp,reboot,read,write,policy,test,winbox,password,web 3 name="test" policy=ssh,read,policy,!local,!telnet,!ftp,!reboot,!write,!test,!winbox,!password,!web [admin@rb13] >
Exclamation sign '!' just before policy item name means NOT.
Example
To add reboot group that is allowed to reboot the router locally or using telnet, as well as read the router's configuration, enter the following command:
[admin@rb13] user group> add name=reboot policy=telnet,reboot,read,local [admin@rb13] user group> print 0 name="read" policy=local,telnet,ssh,reboot,read,test,winbox,password,web,!ftp,!write,!policy 1 name="write" policy=local,telnet,ssh,reboot,read,write,test,winbox,password,web,!ftp,!policy 2 name="full" policy=local,telnet,ssh,ftp,reboot,read,write,policy,test,winbox,password,web 3 name="reboot" policy=local,telnet,reboot,read,!ssh,!ftp,!write,!policy,!test,!winbox,!password,!web [admin@rb13] user group>
Router Users
Sub-menu: /user
Router user database stores the information such as username, password, allowed access addresses and group about router management personnel.
Properties
| Property | Description |
|---|---|
| address (IP/mask; Default: 0.0.0.0/0) | Host or network address from which the user is allowed to log in |
| group (string; Default: ) | name of the group the user belongs to |
| name (string; Default: ) | User name. Although it must start with an alphanumeric character, it may contain "*", "_", "." and "@" symbols |
| password (string; Default: ) | User password. If not specified, it is left blank (hit [Enter] when logging in). It conforms to standard Unix characteristics of passwords and may contain letters, digits, "*" and "_" symbols |
Notes
There is one predefined user with full access rights:
[admin@MikroTik] user> print
Flags: X - disabled
# NAME GROUP ADDRESS
0 ;;; system default user
admin full 0.0.0.0/0
[admin@MikroTik] user>
There always should be at least one user with fulls access rights. If the user with full access rights is the only one, it cannot be removed.
Monitoring Active Users
Sub-menu: /user active
/user active print command shows the currently active users along with respective statisics information.
Properties
| Property | Description |
|---|---|
| address (IP) | Host IP address from which the user is accessing the router. 0.0.0.0 means that user is logged in locally. |
| name (string) | User name |
| via (console | telnet | ssh | winbox) | user's access method |
| when (time) | Log in date and time |
Example
To print currently active users, enter the following command:
[admin@rb13] user> active print Flags: R - radius # WHEN NAME ADDRESS VIA 0 feb/27/2004 00:41:41 admin 1.1.1.200 ssh 1 feb/27/2004 01:22:34 admin 1.1.1.200 winbox [admin@rb13] user>
Remote AAA
Sub-menu: /user aaa
Router user remote AAA enables router user authentication and accounting via RADIUS server. The RADIUS user database is consulted only if the required username is not found in the local user database
Properties
| Property | Description |
|---|---|
| accounting (yes | no; Default: yes) | Enable RADIUS accounting |
| default-group (string; Default: read) | user group used by default for users authenticated via RADIUS server |
| interim-update (time; Default: 0s) | Interim-Update time interval |
| use-radius (yes | no; Default: no) | Enable user authentication via RADIUS |