blob: 3528563e45aa676662dc262cec850d47ddfb0cbb [file] [log] [blame]
Chetan Gaonker7f4bf742016-05-04 15:56:08 -07001#
2# Configuration file for the rlm_files module.
3# Please see rlm_files(5) manpage for more information.
4#
5# This file contains authentication security and configuration
6# information for each user. Accounting requests are NOT processed
7# through this file. Instead, see 'accounting', in this directory.
8#
9# The first field is the user's name and can be up to
10# 253 characters in length. This is followed (on the same line) with
11# the list of authentication requirements for that user. This can
12# include password, comm server name, comm server port number, protocol
13# type (perhaps set by the "hints" file), and huntgroup name (set by
14# the "huntgroups" file).
15#
16# If you are not sure why a particular reply is being sent by the
17# server, then run the server in debugging mode (radiusd -X), and
18# you will see which entries in this file are matched.
19#
20# When an authentication request is received from the comm server,
21# these values are tested. Only the first match is used unless the
22# "Fall-Through" variable is set to "Yes".
23#
24# A special user named "DEFAULT" matches on all usernames.
25# You can have several DEFAULT entries. All entries are processed
26# in the order they appear in this file. The first entry that
27# matches the login-request will stop processing unless you use
28# the Fall-Through variable.
29#
30# Indented (with the tab character) lines following the first
31# line indicate the configuration values to be passed back to
32# the comm server to allow the initiation of a user session.
33# This can include things like the PPP configuration values
34# or the host to log the user onto.
35#
36# You can include another `users' file with `$INCLUDE users.other'
37
38#
39# For a list of RADIUS attributes, and links to their definitions,
40# see: http://www.freeradius.org/rfc/attributes.html
41#
42# Entries below this point are examples included in the server for
43# educational purposes. They may be deleted from the deployed
44# configuration without impacting the operation of the server.
45#
46
47#
48# Deny access for a specific user. Note that this entry MUST
49# be before any other 'Auth-Type' attribute which results in the user
50# being authenticated.
51#
52# Note that there is NO 'Fall-Through' attribute, so the user will not
53# be given any additional resources.
54#
55#lameuser Auth-Type := Reject
56# Reply-Message = "Your account has been disabled."
57
58#
59# Deny access for a group of users.
60#
61# Note that there is NO 'Fall-Through' attribute, so the user will not
62# be given any additional resources.
63#
64#DEFAULT Group == "disabled", Auth-Type := Reject
65# Reply-Message = "Your account has been disabled."
66#
67
68#
69# This is a complete entry for "steve". Note that there is no Fall-Through
70# entry so that no DEFAULT entry will be used, and the user will NOT
71# get any attributes in addition to the ones listed here.
72#
73#steve Cleartext-Password := "testing"
74# Service-Type = Framed-User,
75# Framed-Protocol = PPP,
76# Framed-IP-Address = 172.16.3.33,
77# Framed-IP-Netmask = 255.255.255.0,
78# Framed-Routing = Broadcast-Listen,
79# Framed-Filter-Id = "std.ppp",
80# Framed-MTU = 1500,
81# Framed-Compression = Van-Jacobsen-TCP-IP
82
83#
84# The canonical testing user which is in most of the
85# examples.
86#
87#bob Cleartext-Password := "hello"
88# Reply-Message := "Hello, %{User-Name}"
89#
90
91test Cleartext-Password := "test"
92 Reply-Message := "Hello, %{User-Name}"
93
94raduser Cleartext-Password := "radpass"
95 Reply-Message := "Hello, %{User-Name}"
96
97#
98# This is an entry for a user with a space in their name.
99# Note the double quotes surrounding the name. If you have
100# users with spaces in their names, you must also change
101# the "filter_username" policy to allow spaces.
102#
103# See raddb/policy.d/filter, filter_username {} section.
104#
105#"John Doe" Cleartext-Password := "hello"
106# Reply-Message = "Hello, %{User-Name}"
107
108#
109# Dial user back and telnet to the default host for that port
110#
111#Deg Cleartext-Password := "ge55ged"
112# Service-Type = Callback-Login-User,
113# Login-IP-Host = 0.0.0.0,
114# Callback-Number = "9,5551212",
115# Login-Service = Telnet,
116# Login-TCP-Port = Telnet
117
118#
119# Another complete entry. After the user "dialbk" has logged in, the
120# connection will be broken and the user will be dialed back after which
121# he will get a connection to the host "timeshare1".
122#
123#dialbk Cleartext-Password := "callme"
124# Service-Type = Callback-Login-User,
125# Login-IP-Host = timeshare1,
126# Login-Service = PortMaster,
127# Callback-Number = "9,1-800-555-1212"
128
129#
130# user "swilson" will only get a static IP number if he logs in with
131# a framed protocol on a terminal server in Alphen (see the huntgroups file).
132#
133# Note that by setting "Fall-Through", other attributes will be added from
134# the following DEFAULT entries
135#
136#swilson Service-Type == Framed-User, Huntgroup-Name == "alphen"
137# Framed-IP-Address = 192.0.2.65,
138# Fall-Through = Yes
139
140#
141# If the user logs in as 'username.shell', then authenticate them
142# using the default method, give them shell access, and stop processing
143# the rest of the file.
144#
145#DEFAULT Suffix == ".shell"
146# Service-Type = Login-User,
147# Login-Service = Telnet,
148# Login-IP-Host = your.shell.machine
149
150
151#
152# The rest of this file contains the several DEFAULT entries.
153# DEFAULT entries match with all login names.
154# Note that DEFAULT entries can also Fall-Through (see first entry).
155# A name-value pair from a DEFAULT entry will _NEVER_ override
156# an already existing name-value pair.
157#
158
159#
160# Set up different IP address pools for the terminal servers.
161# Note that the "+" behind the IP address means that this is the "base"
162# IP address. The Port-Id (S0, S1 etc) will be added to it.
163#
164#DEFAULT Service-Type == Framed-User, Huntgroup-Name == "alphen"
165# Framed-IP-Address = 192.0.2.32+,
166# Fall-Through = Yes
167
168#DEFAULT Service-Type == Framed-User, Huntgroup-Name == "delft"
169# Framed-IP-Address = 198.51.100.32+,
170# Fall-Through = Yes
171
172#
173# Sample defaults for all framed connections.
174#
175#DEFAULT Service-Type == Framed-User
176# Framed-IP-Address = 255.255.255.254,
177# Framed-MTU = 576,
178# Service-Type = Framed-User,
179# Fall-Through = Yes
180
181#
182# Default for PPP: dynamic IP address, PPP mode, VJ-compression.
183# NOTE: we do not use Hint = "PPP", since PPP might also be auto-detected
184# by the terminal server in which case there may not be a "P" suffix.
185# The terminal server sends "Framed-Protocol = PPP" for auto PPP.
186#
187DEFAULT Framed-Protocol == PPP
188 Framed-Protocol = PPP,
189 Framed-Compression = Van-Jacobson-TCP-IP
190
191#
192# Default for CSLIP: dynamic IP address, SLIP mode, VJ-compression.
193#
194DEFAULT Hint == "CSLIP"
195 Framed-Protocol = SLIP,
196 Framed-Compression = Van-Jacobson-TCP-IP
197
198#
199# Default for SLIP: dynamic IP address, SLIP mode.
200#
201DEFAULT Hint == "SLIP"
202 Framed-Protocol = SLIP
203
204#
205# Last default: rlogin to our main server.
206#
207#DEFAULT
208# Service-Type = Login-User,
209# Login-Service = Rlogin,
210# Login-IP-Host = shellbox.ispdomain.com
211
212# #
213# # Last default: shell on the local terminal server.
214# #
215# DEFAULT
216# Service-Type = Administrative-User
217
218# On no match, the user is denied access.