3 ## eap.conf -- Configuration for EAP types (PEAP, TTLS, etc.)
7 #######################################################################
9 # Whatever you do, do NOT set 'Auth-Type := EAP'. The server
10 # is smart enough to figure this out on its own. The most
11 # common side effect of setting 'Auth-Type := EAP' is that the
12 # users then cannot use ANY other authentication method.
14 # EAP types NOT listed here may be supported via the "eap2" module.
15 # See experimental.conf for documentation.
18 # Invoke the default supported EAP type when
19 # EAP-Identity response is received.
21 # The incoming EAP messages DO NOT specify which EAP
22 # type they will be using, so it MUST be set here.
24 # For now, only one default EAP type may be used at a time.
26 # If the EAP-Type attribute is set by another module,
27 # then that EAP type takes precedence over the
28 # default type configured here.
30 default_eap_type = md5
32 # A list is maintained to correlate EAP-Response
33 # packets with EAP-Request packets. After a
34 # configurable length of time, entries in the list
35 # expire, and are deleted.
39 # There are many EAP types, but the server has support
40 # for only a limited subset. If the server receives
41 # a request for an EAP type it does not support, then
42 # it normally rejects the request. By setting this
43 # configuration to "yes", you can tell the server to
44 # instead keep processing the request. Another module
45 # MUST then be configured to proxy the request to
46 # another RADIUS server which supports that EAP type.
48 # If another module is NOT configured to handle the
49 # request, then the request will still end up being
51 ignore_unknown_eap_types = no
53 # Cisco AP1230B firmware 12.2(13)JA1 has a bug. When given
54 # a User-Name attribute in an Access-Accept, it copies one
55 # more byte than it should.
57 # We can work around it by configurably adding an extra
59 cisco_accounting_username_bug = no
62 # Help prevent DoS attacks by limiting the number of
63 # sessions that the server is tracking. Most systems
64 # can handle ~30 EAP sessions/s, so the default limit
65 # of 4096 should be OK.
71 # We do NOT recommend using EAP-MD5 authentication
72 # for wireless connections. It is insecure, and does
73 # not provide for dynamic WEP keys.
80 # We do not recommend using LEAP in new deployments. See:
81 # http://www.securiteam.com/tools/5TP012ACKE.html
83 # Cisco LEAP uses the MS-CHAP algorithm (but not
84 # the MS-CHAP attributes) to perform it's authentication.
86 # As a result, LEAP *requires* access to the plain-text
87 # User-Password, or the NT-Password attributes.
88 # 'System' authentication is impossible with LEAP.
95 # Currently, this is only permitted inside of EAP-TTLS,
96 # or EAP-PEAP. The module "challenges" the user with
97 # text, and the response from the user is taken to be
100 # Proxying the tunneled EAP-GTC session is a bad idea,
101 # the users password will go over the wire in plain-text,
105 # The default challenge, which many clients
107 #challenge = "Password: "
109 # The plain-text response which comes back
110 # is put into a User-Password attribute,
111 # and passed to another module for
112 # authentication. This allows the EAP-GTC
113 # response to be checked against plain-text,
114 # or crypt'd passwords.
116 # If you say "Local" instead of "PAP", then
117 # the module will look for a User-Password
118 # configured for the request, and do the
119 # authentication itself.
126 # See raddb/certs/README for additional comments
129 # If OpenSSL was not found at the time the server was
130 # built, the "tls", "ttls", and "peap" sections will
133 # Otherwise, when the server first starts in debugging
134 # mode, test certificates will be created. See the
135 # "make_cert_command" below for details, and the README
136 # file in raddb/certs
138 # These test certificates SHOULD NOT be used in a normal
139 # deployment. They are created only to make it easier
140 # to install the server, and to perform some simple
141 # tests with EAP-TLS, TTLS, or PEAP.
145 # http://www.dslreports.com/forum/remark,9286052~mode=flat
147 # Note that you should NOT use a globally known CA here!
148 # e.g. using a Verisign cert as a "known CA" means that
149 # ANYONE who has a certificate signed by them can
150 # authenticate via EAP-TLS! This is likey not what you want.
153 # These is used to simplify later configurations.
155 certdir = ${confdir}/certs
156 cadir = ${confdir}/certs
158 private_key_password = whatever
159 private_key_file = ${certdir}/server.pem
161 # If Private key & Certificate are located in
162 # the same file, then private_key_file &
163 # certificate_file must contain the same file
166 # If CA_file (below) is not used, then the
167 # certificate_file below MUST include not
168 # only the server certificate, but ALSO all
169 # of the CA certificates used to sign the
170 # server certificate.
171 certificate_file = ${certdir}/server.pem
173 # Trusted Root CA list
175 # ALL of the CA's in this list will be trusted
176 # to issue client certificates for authentication.
178 # In general, you should use self-signed
179 # certificates for 802.1x (EAP) authentication.
180 # In that case, this CA file should contain
181 # *one* CA certificate.
183 # This parameter is used only for EAP-TLS,
184 # when you issue client certificates. If you do
185 # not use client certificates, and you do not want
186 # to permit EAP-TLS authentication, then delete
187 # this configuration item.
188 CA_file = ${cadir}/ca.pem
191 # For DH cipher suites to work, you have to
192 # run OpenSSL to create the DH file first:
194 # openssl dhparam -out certs/dh 1024
196 dh_file = ${certdir}/dh
197 random_file = ${certdir}/random
200 # This can never exceed the size of a RADIUS
201 # packet (4096 bytes), and is preferably half
202 # that, to accomodate other attributes in
203 # RADIUS packet. On most APs the MAX packet
204 # length is configured between 1500 - 1600
205 # In these cases, fragment size should be
208 # fragment_size = 1024
210 # include_length is a flag which is
211 # by default set to yes If set to
212 # yes, Total Length of the message is
213 # included in EVERY packet we send.
214 # If set to no, Total Length of the
215 # message is included ONLY in the
216 # First packet of a fragment series.
218 # include_length = yes
220 # Check the Certificate Revocation List
222 # 1) Copy CA certificates and CRLs to same directory.
223 # 2) Execute 'c_rehash <CA certs&CRLs Directory>'.
224 # 'c_rehash' is OpenSSL's command.
225 # 3) uncomment the line below.
228 # CA_path = /path/to/directory/with/ca_certs/and/crls/
231 # If check_cert_issuer is set, the value will
232 # be checked against the DN of the issuer in
233 # the client certificate. If the values do not
234 # match, the cerficate verification will fail,
235 # rejecting the user.
237 # check_cert_issuer = "/C=GB/ST=Berkshire/L=Newbury/O=My Company Ltd"
240 # If check_cert_cn is set, the value will
241 # be xlat'ed and checked against the CN
242 # in the client certificate. If the values
243 # do not match, the certificate verification
244 # will fail rejecting the user.
246 # This check is done only if the previous
247 # "check_cert_issuer" is not set, or if
248 # the check succeeds.
250 # check_cert_cn = %{User-Name}
252 # Set this option to specify the allowed
253 # TLS cipher suites. The format is listed
254 # in "man 1 ciphers".
255 cipher_list = "DEFAULT"
259 # This configuration entry should be deleted
260 # once the server is running in a normal
261 # configuration. It is here ONLY to make
262 # initial deployments easier.
264 make_cert_command = "${certdir}/bootstrap"
267 # Session resumption / fast reauthentication
272 # Enable it. The default is "no".
273 # Deleting the entire "cache" subsection
274 # Also disables caching.
276 # You can disallow resumption for a
277 # particular user by adding the following
278 # attribute to the control item list:
280 # Allow-Session-Resumption = No
282 # If "enable = no" below, you CANNOT
283 # enable resumption for just one user
284 # by setting the above attribute to "yes".
289 # Lifetime of the cached entries, in hours.
290 # The sessions will be deleted after this
293 lifetime = 24 # hours
296 # The maximum number of entries in the
297 # cache. Set to "0" for "infinite".
299 # This could be set to the number of users
300 # who are logged in... which can be a LOT.
306 # The TTLS module implements the EAP-TTLS protocol,
307 # which can be described as EAP inside of Diameter,
308 # inside of TLS, inside of EAP, inside of RADIUS...
310 # Surprisingly, it works quite well.
312 # The TTLS module needs the TLS module to be installed
313 # and configured, in order to use the TLS tunnel
314 # inside of the EAP packet. You will still need to
315 # configure the TLS module, even if you do not want
316 # to deploy EAP-TLS in your network. Users will not
317 # be able to request EAP-TLS, as it requires them to
318 # have a client certificate. EAP-TTLS does not
319 # require a client certificate.
321 # You can make TTLS require a client cert by setting
323 # EAP-TLS-Require-Client-Cert = Yes
325 # in the control items for a request.
328 # The tunneled EAP session needs a default
329 # EAP type which is separate from the one for
330 # the non-tunneled EAP module. Inside of the
331 # TTLS tunnel, we recommend using EAP-MD5.
332 # If the request does not contain an EAP
333 # conversation, then this configuration entry
335 default_eap_type = md5
337 # The tunneled authentication request does
338 # not usually contain useful attributes
339 # like 'Calling-Station-Id', etc. These
340 # attributes are outside of the tunnel,
341 # and normally unavailable to the tunneled
342 # authentication request.
344 # By setting this configuration entry to
345 # 'yes', any attribute which NOT in the
346 # tunneled authentication request, but
347 # which IS available outside of the tunnel,
348 # is copied to the tunneled request.
350 # allowed values: {no, yes}
351 copy_request_to_tunnel = no
353 # The reply attributes sent to the NAS are
354 # usually based on the name of the user
355 # 'outside' of the tunnel (usually
356 # 'anonymous'). If you want to send the
357 # reply attributes based on the user name
358 # inside of the tunnel, then set this
359 # configuration entry to 'yes', and the reply
360 # to the NAS will be taken from the reply to
361 # the tunneled request.
363 # allowed values: {no, yes}
364 use_tunneled_reply = no
367 # The inner tunneled request can be sent
368 # through a virtual server constructed
369 # specifically for this purpose.
371 # If this entry is commented out, the inner
372 # tunneled request will be sent through
373 # the virtual server that processed the
376 virtual_server = "inner-tunnel"
378 # This has the same meaning as the
379 # same field in the "tls" module, above.
380 # The default value here is "yes".
381 # include_length = yes
384 ##################################################
386 # !!!!! WARNINGS for Windows compatibility !!!!!
388 ##################################################
390 # If you see the server send an Access-Challenge,
391 # and the client never sends another Access-Request,
396 # The server certificate has to have special OID's
397 # in it, or else the Microsoft clients will silently
398 # fail. See the "scripts/xpextensions" file for
399 # details, and the following page:
401 # http://support.microsoft.com/kb/814394/en-us
403 # For additional Windows XP SP2 issues, see:
405 # http://support.microsoft.com/kb/885453/en-us
408 # If is still doesn't work, and you're using Samba,
409 # you may be encountering a Samba bug. See:
411 # https://bugzilla.samba.org/show_bug.cgi?id=6563
413 # Note that we do not necessarily agree with their
414 # explanation... but the fix does appear to work.
416 ##################################################
419 # The tunneled EAP session needs a default EAP type
420 # which is separate from the one for the non-tunneled
421 # EAP module. Inside of the TLS/PEAP tunnel, we
422 # recommend using EAP-MS-CHAPv2.
424 # The PEAP module needs the TLS module to be installed
425 # and configured, in order to use the TLS tunnel
426 # inside of the EAP packet. You will still need to
427 # configure the TLS module, even if you do not want
428 # to deploy EAP-TLS in your network. Users will not
429 # be able to request EAP-TLS, as it requires them to
430 # have a client certificate. EAP-PEAP does not
431 # require a client certificate.
434 # You can make PEAP require a client cert by setting
436 # EAP-TLS-Require-Client-Cert = Yes
438 # in the control items for a request.
441 # The tunneled EAP session needs a default
442 # EAP type which is separate from the one for
443 # the non-tunneled EAP module. Inside of the
444 # PEAP tunnel, we recommend using MS-CHAPv2,
445 # as that is the default type supported by
447 default_eap_type = mschapv2
449 # the PEAP module also has these configuration
450 # items, which are the same as for TTLS.
451 copy_request_to_tunnel = no
452 use_tunneled_reply = no
454 # When the tunneled session is proxied, the
455 # home server may not understand EAP-MSCHAP-V2.
456 # Set this entry to "no" to proxy the tunneled
457 # EAP-MSCHAP-V2 as normal MSCHAPv2.
458 # proxy_tunneled_request_as_eap = yes
461 # The inner tunneled request can be sent
462 # through a virtual server constructed
463 # specifically for this purpose.
465 # If this entry is commented out, the inner
466 # tunneled request will be sent through
467 # the virtual server that processed the
470 virtual_server = "inner-tunnel"
474 # This takes no configuration.
476 # Note that it is the EAP MS-CHAPv2 sub-module, not
477 # the main 'mschap' module.
479 # Note also that in order for this sub-module to work,
480 # the main 'mschap' module MUST ALSO be configured.
482 # This module is the *Microsoft* implementation of MS-CHAPv2
483 # in EAP. There is another (incompatible) implementation
484 # of MS-CHAPv2 in EAP by Cisco, which FreeRADIUS does not