1 ######################################################################
3 # As of 2.0.0, FreeRADIUS supports virtual hosts using the
4 # "server" section, and configuration directives.
6 # Virtual hosts should be put into the "sites-available"
7 # directory. Soft links should be created in the "sites-enabled"
8 # directory to these files. This is done in a normal installation.
13 ######################################################################
16 # In 1.x, the "authorize", etc. sections were global in
17 # radiusd.conf. As of 2.0, they MUST be in a server section.
19 # The server section with no virtual server name is the "default"
20 # section. It is used when no server name is specified.
22 # We don't indent the rest of this file, because doing so
23 # would make it harder to read.
27 # Authorization. First preprocess (hints and huntgroups files),
28 # then realms, and finally look in the "users" file.
30 # The order of the realm modules will determine the order that
31 # we try to find a matching realm.
33 # Make *sure* that 'preprocess' comes before any realm if you
34 # need to setup hints for the remote radius server
37 # The preprocess module takes care of sanitizing some bizarre
38 # attributes in the request, and turning them into attributes
39 # which are more standard.
41 # It takes care of processing the 'raddb/hints' and the
42 # 'raddb/huntgroups' files.
44 # It also adds the %{Client-IP-Address} attribute to the request.
48 # If you want to have a log of authentication requests,
49 # un-comment the following line, and the 'detail auth_log'
54 # The chap module will set 'Auth-Type := CHAP' if we are
55 # handling a CHAP request and Auth-Type has not already been set
59 # If the users are logging in with an MS-CHAP-Challenge
60 # attribute for authentication, the mschap module will find
61 # the MS-CHAP-Challenge attribute, and add 'Auth-Type := MS-CHAP'
62 # to the request, which will cause the server to then use
63 # the mschap module for authentication.
67 # Pull crypt'd passwords from /etc/passwd or /etc/shadow,
68 # using the system API's to get the password. If you want
69 # to read /etc/passwd or /etc/shadow directly, see the
70 # passwd module, above.
75 # If you have a Cisco SIP server authenticating against
76 # FreeRADIUS, uncomment the following line, and the 'digest'
77 # line in the 'authenticate' section.
81 # Look for IPASS style 'realm/', and if not found, look for
82 # '@realm', and decide whether or not to proxy, based on
87 # If you are using multiple kinds of realms, you probably
88 # want to set "ignore_null = yes" for all of them.
89 # Otherwise, when the first style of realm doesn't match,
90 # the other styles won't be checked.
96 # This module takes care of EAP-MD5, EAP-TLS, and EAP-LEAP
99 # It also sets the EAP-Type attribute in the request
100 # attribute list to the EAP type from the packet.
102 # As of 2.0, the EAP module returns "ok" in the authorize stage
103 # for TTLS and PEAP. In 1.x, it never returned "ok" here, so
104 # this change is compatible with older configurations.
106 # The example below uses module failover to avoid querying all
107 # of the following modules if the EAP module returns "ok".
108 # Therefore, your LDAP and/or SQL servers will not be queried
109 # for the many packets that go back and forth to set up TTLS
110 # or PEAP. The load on those servers will therefore be reduced.
117 # Read the 'users' file
121 # Look in an SQL database. The schema of the database
122 # is meant to mirror the "users" file.
124 # See "Authorization Queries" in sql.conf
128 # If you are using /etc/smbpasswd, and are also doing
129 # mschap authentication, the un-comment this line, and
130 # configure the 'etc_smbpasswd' module, above.
134 # The ldap module will set Auth-Type to LDAP if it has not
139 # Enforce daily limits on time spent logged in.
143 # Use the checkval module
150 # If no other module has claimed responsibility for
151 # authentication, then try to use PAP. This allows the
152 # other modules listed above to add a "known good" password
153 # to the request, and to do nothing else. The PAP module
154 # will then see that password, and use it to do PAP
157 # This module should be listed last, so that the other modules
158 # get a chance to set Auth-Type for themselves.
163 # If "status_server = yes", then Status-Server messages are passed
164 # through the following section, and ONLY the following section.
165 # This permits you to do DB queries, for example. If the modules
166 # listed here return "fail", then NO response is sent.
168 # Autz-Type Status-Server {
177 # This section lists which modules are available for authentication.
178 # Note that it does NOT mean 'try each module in order'. It means
179 # that a module from the 'authorize' section adds a configuration
180 # attribute 'Auth-Type := FOO'. That authentication type is then
181 # used to pick the apropriate module from the list below.
184 # In general, you SHOULD NOT set the Auth-Type attribute. The server
185 # will figure it out on its own, and will do the right thing. The
186 # most common side effect of erroneously setting the Auth-Type
187 # attribute is that one authentication method will work, but the
190 # The common reasons to set the Auth-Type attribute by hand
191 # is to either forcibly reject the user (Auth-Type := Reject),
192 # or to or forcibly accept the user (Auth-Type := Accept).
194 # Note that Auth-Type := Accept will NOT work with EAP.
196 # Please do not put "unlang" configurations into the "authenticate"
197 # section. Put them in the "post-auth" section instead. That's what
198 # the post-auth section is for.
202 # PAP authentication, when a back-end database listed
203 # in the 'authorize' section supplies a password. The
204 # password can be clear-text, or encrypted.
210 # Most people want CHAP authentication
211 # A back-end database listed in the 'authorize' section
212 # MUST supply a CLEAR TEXT password. Encrypted passwords
219 # MSCHAP authentication.
225 # If you have a Cisco SIP server authenticating against
226 # FreeRADIUS, uncomment the following line, and the 'digest'
227 # line in the 'authorize' section.
231 # Pluggable Authentication Modules.
235 # See 'man getpwent' for information on how the 'unix'
236 # module checks the users password. Note that packets
237 # containing CHAP-Password attributes CANNOT be authenticated
238 # against /etc/passwd! See the FAQ for details.
242 # Uncomment it if you want to use ldap for authentication
244 # Note that this means "check plain-text password against
245 # the ldap database", which means that EAP won't work,
246 # as it does not supply a plain-text password.
252 # Allow EAP authentication.
258 # Pre-accounting. Decide which accounting type to use.
264 # Ensure that we have a semi-unique identifier for every
265 # request, and many NAS boxes are broken.
269 # Look for IPASS-style 'realm/', and if not found, look for
270 # '@realm', and decide whether or not to proxy, based on
273 # Accounting requests are generally proxied to the same
274 # home server as authentication requests.
280 # Read the 'acct_users' file
285 # Accounting. Log the accounting data.
289 # Create a 'detail'ed log of the packets.
290 # Note that accounting requests which are proxied
291 # are also logged in the detail file.
295 # Update the wtmp file
297 # If you don't use "radlast", you can delete this line.
301 # For Simultaneous-Use tracking.
303 # Due to packet losses in the network, the data here
304 # may be incorrect. There is little we can do about it.
308 # Return an address to the IP Pool when we see a stop record.
312 # Log traffic to an SQL database.
314 # See "Accounting queries" in sql.conf
318 # Instead of sending the query to the SQL server,
319 # write it into a log file.
323 # Cisco VoIP specific bulk accounting
326 # Filter attributes from the accounting response.
327 attr_filter.accounting_response
330 # See "Autz-Type Status-Server" for how this works.
332 # Acct-Type Status-Server {
338 # Session database, used for checking Simultaneous-Use. Either the radutmp
339 # or rlm_sql module can handle this.
340 # The rlm_sql module is *much* faster
345 # See "Simultaneous Use Checking Queries" in sql.conf
350 # Post-Authentication
351 # Once we KNOW that the user has been authenticated, there are
352 # additional steps we can take.
354 # Get an address from the IP Pool.
358 # If you want to have a log of authentication replies,
359 # un-comment the following line, and the 'detail reply_log'
364 # After authenticating the user, do another SQL query.
366 # See "Authentication Logging Queries" in sql.conf
370 # Instead of sending the query to the SQL server,
371 # write it into a log file.
376 # Un-comment the following if you have set
377 # 'edir_account_policy_check = yes' in the ldap module sub-section of
378 # the 'modules' section.
383 # Access-Reject packets are sent through the REJECT sub-section of the
386 # Add the ldap module name (or instance) if you have set
387 # 'edir_account_policy_check = yes' in the ldap module configuration
389 Post-Auth-Type REJECT {
390 attr_filter.access_reject
395 # When the server decides to proxy a request to a home server,
396 # the proxied request is first passed through the pre-proxy
397 # stage. This stage can re-write the request, or decide to
400 # Only a few modules currently have this method.
405 # Uncomment the following line if you want to change attributes
406 # as defined in the preproxy_users file.
409 # Uncomment the following line if you want to filter requests
410 # sent to remote servers based on the rules defined in the
411 # 'attrs.pre-proxy' file.
412 # attr_filter.pre-proxy
414 # If you want to have a log of packets proxied to a home
415 # server, un-comment the following line, and the
416 # 'detail pre_proxy_log' section, above.
421 # When the server receives a reply to a request it proxied
422 # to a home server, the request may be massaged here, in the
427 # If you want to have a log of replies from a home server,
428 # un-comment the following line, and the 'detail post_proxy_log'
434 # Uncomment the following line if you want to filter replies from
435 # remote proxies based on the rules defined in the 'attrs' file.
436 # attr_filter.post-proxy
439 # If you are proxying LEAP, you MUST configure the EAP
440 # module, and you MUST list it here, in the post-proxy
443 # You MUST also use the 'nostrip' option in the 'realm'
444 # configuration. Otherwise, the User-Name attribute
445 # in the proxied request will not match the user name
446 # hidden inside of the EAP packet, and the end server will
447 # reject the EAP request.
452 # If the server tries to proxy a request and fails, then the
453 # request is processed through the modules in this section.
455 # The main use of this section is to permit robust proxying
456 # of accounting packets. The server can be configured to
457 # proxy accounting packets as part of normal processing.
458 # Then, if the home server goes down, accounting packets can
459 # be logged to a local "detail" file, for processing with
460 # radrelay. When the home server comes back up, radrelay
461 # will read the detail file, and send the packets to the
464 # With this configuration, the server always responds to
465 # Accounting-Requests from the NAS, but only writes
466 # accounting packets to disk if the home server is down.
468 # Post-Proxy-Type Fail {
474 } # default server block