3 # Whatever you do, do NOT set 'Auth-Type := EAP'. The server
4 # is smart enough to figure this out on its own. The most
5 # common side effect of setting 'Auth-Type := EAP' is that the
6 # users then cannot use ANY other authentication method.
11 # Invoke the default supported EAP type when
12 # EAP-Identity response is received.
14 # The incoming EAP messages DO NOT specify which EAP
15 # type they will be using, so it MUST be set here.
17 # For now, only one default EAP type may be used at a time.
19 # If the EAP-Type attribute is set by another module,
20 # then that EAP type takes precedence over the
21 # default type configured here.
23 default_eap_type = md5
25 # A list is maintained to correlate EAP-Response
26 # packets with EAP-Request packets. After a
27 # configurable length of time, entries in the list
28 # expire, and are deleted.
32 # There are many EAP types, but the server has support
33 # for only a limited subset. If the server receives
34 # a request for an EAP type it does not support, then
35 # it normally rejects the request. By setting this
36 # configuration to "yes", you can tell the server to
37 # instead keep processing the request. Another module
38 # MUST then be configured to proxy the request to
39 # another RADIUS server which supports that EAP type.
41 # If another module is NOT configured to handle the
42 # request, then the request will still end up being
44 ignore_unknown_eap_types = no
46 # Cisco AP1230B firmware 12.2(13)JA1 has a bug. When given
47 # a User-Name attribute in an Access-Accept, it copies one
48 # more byte than it should.
50 # We can work around it by configurably adding an extra
52 cisco_accounting_username_bug = no
57 # We do NOT recommend using EAP-MD5 authentication
58 # for wireless connections. It is insecure, and does
59 # not provide for dynamic WEP keys.
66 # We do not recommend using LEAP in new deployments. See:
67 # http://www.securiteam.com/tools/5TP012ACKE.html
69 # Cisco LEAP uses the MS-CHAP algorithm (but not
70 # the MS-CHAP attributes) to perform it's authentication.
72 # As a result, LEAP *requires* access to the plain-text
73 # User-Password, or the NT-Password attributes.
74 # 'System' authentication is impossible with LEAP.
81 # Currently, this is only permitted inside of EAP-TTLS,
82 # or EAP-PEAP. The module "challenges" the user with
83 # text, and the response from the user is taken to be
86 # Proxying the tunneled EAP-GTC session is a bad idea,
87 # the users password will go over the wire in plain-text,
91 # The default challenge, which many clients
93 #challenge = "Password: "
95 # The plain-text response which comes back
96 # is put into a User-Password attribute,
97 # and passed to another module for
98 # authentication. This allows the EAP-GTC
99 # response to be checked against plain-text,
100 # or crypt'd passwords.
102 # If you say "Local" instead of "PAP", then
103 # the module will look for a User-Password
104 # configured for the request, and do the
105 # authentication itself.
112 # If OpenSSL was not found at the time the server was
113 # built, the "tls", "ttls", and "peap" sections will
116 # Otherwise, when the server first starts in debugging
117 # mode, test certificates will be created. See the
118 # "make_cert_command" below for details, and the README
119 # file in raddb/certs
121 # These test certificates SHOULD NOT be used in a normal
122 # deployment. They are created only to make it easier
123 # to install the server, and to perform some simple
124 # tests with EAP-TLS, TTLS, or PEAP.
128 # http://www.dslreports.com/forum/remark,9286052~mode=flat
132 # These is used to simplify later configurations.
134 certdir = ${confdir}/certs
135 cadir = ${confdir}/certs
137 private_key_password = whatever
138 private_key_file = ${certdir}/server.pem
140 # If Private key & Certificate are located in
141 # the same file, then private_key_file &
142 # certificate_file must contain the same file
144 certificate_file = ${certdir}/server.pem
146 # Trusted Root CA list
147 CA_file = ${cadir}/ca.pem
150 # For DH cipher suites to work, you have to
151 # run OpenSSL to create the DH file first:
153 # openssl dhparam -out certs/dh 1024
155 dh_file = ${certdir}/dh
156 random_file = ${certdir}/random
159 # This can never exceed the size of a RADIUS
160 # packet (4096 bytes), and is preferably half
161 # that, to accomodate other attributes in
162 # RADIUS packet. On most APs the MAX packet
163 # length is configured between 1500 - 1600
164 # In these cases, fragment size should be
167 # fragment_size = 1024
169 # include_length is a flag which is
170 # by default set to yes If set to
171 # yes, Total Length of the message is
172 # included in EVERY packet we send.
173 # If set to no, Total Length of the
174 # message is included ONLY in the
175 # First packet of a fragment series.
177 # include_length = yes
179 # Check the Certificate Revocation List
181 # 1) Copy CA certificates and CRLs to same directory.
182 # 2) Execute 'c_rehash <CA certs&CRLs Directory>'.
183 # 'c_rehash' is OpenSSL's command.
184 # 3) Add 'CA_path=<CA certs&CRLs directory>'
185 # to radiusd.conf's tls section.
186 # 4) uncomment the line below.
191 # If check_cert_issuer is set, the value will
192 # be checked against the DN of the issuer in
193 # the client certificate. If the values do not
194 # match, the cerficate verification will fail,
195 # rejecting the user.
197 # check_cert_issuer = "/C=GB/ST=Berkshire/L=Newbury/O=My Company Ltd"
200 # If check_cert_cn is set, the value will
201 # be xlat'ed and checked against the CN
202 # in the client certificate. If the values
203 # do not match, the certificate verification
204 # will fail rejecting the user.
206 # This check is done only if the previous
207 # "check_cert_issuer" is not set, or if
208 # the check succeeds.
210 # check_cert_cn = %{User-Name}
212 # Set this option to specify the allowed
213 # TLS cipher suites. The format is listed
214 # in "man 1 ciphers".
215 cipher_list = "DEFAULT"
219 # This configuration entry should be deleted
220 # once the server is running in a normal
221 # configuration. It is here ONLY to make
222 # initial deployments easier.
224 make_cert_command = "${certdir}/bootstrap"
227 # The TTLS module implements the EAP-TTLS protocol,
228 # which can be described as EAP inside of Diameter,
229 # inside of TLS, inside of EAP, inside of RADIUS...
231 # Surprisingly, it works quite well.
233 # The TTLS module needs the TLS module to be installed
234 # and configured, in order to use the TLS tunnel
235 # inside of the EAP packet. You will still need to
236 # configure the TLS module, even if you do not want
237 # to deploy EAP-TLS in your network. Users will not
238 # be able to request EAP-TLS, as it requires them to
239 # have a client certificate. EAP-TTLS does not
240 # require a client certificate.
242 # You can make TTLS require a client cert by setting
244 # EAP-TLS-Require-Client-Cert = Yes
246 # in the control items for a request.
249 # The tunneled EAP session needs a default
250 # EAP type which is separate from the one for
251 # the non-tunneled EAP module. Inside of the
252 # TTLS tunnel, we recommend using EAP-MD5.
253 # If the request does not contain an EAP
254 # conversation, then this configuration entry
256 default_eap_type = md5
258 # The tunneled authentication request does
259 # not usually contain useful attributes
260 # like 'Calling-Station-Id', etc. These
261 # attributes are outside of the tunnel,
262 # and normally unavailable to the tunneled
263 # authentication request.
265 # By setting this configuration entry to
266 # 'yes', any attribute which NOT in the
267 # tunneled authentication request, but
268 # which IS available outside of the tunnel,
269 # is copied to the tunneled request.
271 # allowed values: {no, yes}
272 copy_request_to_tunnel = no
274 # The reply attributes sent to the NAS are
275 # usually based on the name of the user
276 # 'outside' of the tunnel (usually
277 # 'anonymous'). If you want to send the
278 # reply attributes based on the user name
279 # inside of the tunnel, then set this
280 # configuration entry to 'yes', and the reply
281 # to the NAS will be taken from the reply to
282 # the tunneled request.
284 # allowed values: {no, yes}
285 use_tunneled_reply = no
288 # The inner tunneled request can be sent
289 # through a virtual server constructed
290 # specifically for this purpose.
292 # If this entry is commented out, the inner
293 # tunneled request will be sent through
294 # the virtual server that processed the
297 #virtual_server = "inner-tunnel"
300 ##################################################
302 # !!!!! WARNINGS for Windows compatibility !!!!!
304 ##################################################
306 # If you see the server send an Access-Challenge,
307 # and the client never sends another Access-Request,
312 # The server certificate has to have special OID's
313 # in it, or else the Microsoft clients will silently
314 # fail. See the "scripts/xpextensions" file for
315 # details, and the following page:
317 # http://support.microsoft.com/kb/814394/en-us
319 # For additional Windows XP SP2 issues, see:
321 # http://support.microsoft.com/kb/885453/en-us
323 # Note that we do not necessarily agree with their
324 # explanation... but the fix does appear to work.
326 ##################################################
329 # The tunneled EAP session needs a default EAP type
330 # which is separate from the one for the non-tunneled
331 # EAP module. Inside of the TLS/PEAP tunnel, we
332 # recommend using EAP-MS-CHAPv2.
334 # The PEAP module needs the TLS module to be installed
335 # and configured, in order to use the TLS tunnel
336 # inside of the EAP packet. You will still need to
337 # configure the TLS module, even if you do not want
338 # to deploy EAP-TLS in your network. Users will not
339 # be able to request EAP-TLS, as it requires them to
340 # have a client certificate. EAP-PEAP does not
341 # require a client certificate.
344 # You can make TTLS require a client cert by setting
346 # EAP-TLS-Require-Client-Cert = Yes
348 # in the control items for a request.
351 # The tunneled EAP session needs a default
352 # EAP type which is separate from the one for
353 # the non-tunneled EAP module. Inside of the
354 # PEAP tunnel, we recommend using MS-CHAPv2,
355 # as that is the default type supported by
357 default_eap_type = mschapv2
359 # the PEAP module also has these configuration
360 # items, which are the same as for TTLS.
361 copy_request_to_tunnel = no
362 use_tunneled_reply = no
364 # When the tunneled session is proxied, the
365 # home server may not understand EAP-MSCHAP-V2.
366 # Set this entry to "no" to proxy the tunneled
367 # EAP-MSCHAP-V2 as normal MSCHAPv2.
368 # proxy_tunneled_request_as_eap = yes
371 # The inner tunneled request can be sent
372 # through a virtual server constructed
373 # specifically for this purpose.
375 # If this entry is commented out, the inner
376 # tunneled request will be sent through
377 # the virtual server that processed the
380 #virtual_server = "inner-tunnel"
384 # This takes no configuration.
386 # Note that it is the EAP MS-CHAPv2 sub-module, not
387 # the main 'mschap' module.
389 # Note also that in order for this sub-module to work,
390 # the main 'mschap' module MUST ALSO be configured.
392 # This module is the *Microsoft* implementation of MS-CHAPv2
393 # in EAP. There is another (incompatible) implementation
394 # of MS-CHAPv2 in EAP by Cisco, which FreeRADIUS does not