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, e.g.:
172 # cat server.pem sub-ca.pem ca.pem > bundle.pem
174 certificate_file = ${certdir}/server.pem
176 # Trusted Root CA list
178 # ALL of the CA's in this list will be trusted
179 # to issue client certificates for authentication.
181 # In general, you should use self-signed
182 # certificates for 802.1x (EAP) authentication.
183 # In that case, this CA file should contain
184 # *one* CA certificate.
186 # This parameter is used only for EAP-TLS,
187 # when you issue client certificates. If you do
188 # not use client certificates, and you do not want
189 # to permit EAP-TLS authentication, then delete
190 # this configuration item.
191 CA_file = ${cadir}/ca.pem
194 # For DH cipher suites to work, you have to
195 # run OpenSSL to create the DH file first:
197 # openssl dhparam -out certs/dh 1024
199 dh_file = ${certdir}/dh
200 random_file = ${certdir}/random
203 # This can never exceed the size of a RADIUS
204 # packet (4096 bytes), and is preferably half
205 # that, to accomodate other attributes in
206 # RADIUS packet. On most APs the MAX packet
207 # length is configured between 1500 - 1600
208 # In these cases, fragment size should be
211 # fragment_size = 1024
213 # include_length is a flag which is
214 # by default set to yes If set to
215 # yes, Total Length of the message is
216 # included in EVERY packet we send.
217 # If set to no, Total Length of the
218 # message is included ONLY in the
219 # First packet of a fragment series.
221 # include_length = yes
223 # Check the Certificate Revocation List
225 # 1) Copy CA certificates and CRLs to same directory.
226 # 2) Execute 'c_rehash <CA certs&CRLs Directory>'.
227 # 'c_rehash' is OpenSSL's command.
228 # 3) uncomment the line below.
231 # CA_path = /path/to/directory/with/ca_certs/and/crls/
234 # If check_cert_issuer is set, the value will
235 # be checked against the DN of the issuer in
236 # the client certificate. If the values do not
237 # match, the cerficate verification will fail,
238 # rejecting the user.
240 # check_cert_issuer = "/C=GB/ST=Berkshire/L=Newbury/O=My Company Ltd"
243 # If check_cert_cn is set, the value will
244 # be xlat'ed and checked against the CN
245 # in the client certificate. If the values
246 # do not match, the certificate verification
247 # will fail rejecting the user.
249 # This check is done only if the previous
250 # "check_cert_issuer" is not set, or if
251 # the check succeeds.
253 # check_cert_cn = %{User-Name}
255 # Set this option to specify the allowed
256 # TLS cipher suites. The format is listed
257 # in "man 1 ciphers".
258 cipher_list = "DEFAULT"
262 # This configuration entry should be deleted
263 # once the server is running in a normal
264 # configuration. It is here ONLY to make
265 # initial deployments easier.
267 make_cert_command = "${certdir}/bootstrap"
270 # Session resumption / fast reauthentication
275 # Enable it. The default is "no".
276 # Deleting the entire "cache" subsection
277 # Also disables caching.
279 # You can disallow resumption for a
280 # particular user by adding the following
281 # attribute to the control item list:
283 # Allow-Session-Resumption = No
285 # If "enable = no" below, you CANNOT
286 # enable resumption for just one user
287 # by setting the above attribute to "yes".
292 # Lifetime of the cached entries, in hours.
293 # The sessions will be deleted after this
296 lifetime = 24 # hours
299 # The maximum number of entries in the
300 # cache. Set to "0" for "infinite".
302 # This could be set to the number of users
303 # who are logged in... which can be a LOT.
309 # The TTLS module implements the EAP-TTLS protocol,
310 # which can be described as EAP inside of Diameter,
311 # inside of TLS, inside of EAP, inside of RADIUS...
313 # Surprisingly, it works quite well.
315 # The TTLS module needs the TLS module to be installed
316 # and configured, in order to use the TLS tunnel
317 # inside of the EAP packet. You will still need to
318 # configure the TLS module, even if you do not want
319 # to deploy EAP-TLS in your network. Users will not
320 # be able to request EAP-TLS, as it requires them to
321 # have a client certificate. EAP-TTLS does not
322 # require a client certificate.
324 # You can make TTLS require a client cert by setting
326 # EAP-TLS-Require-Client-Cert = Yes
328 # in the control items for a request.
331 # The tunneled EAP session needs a default
332 # EAP type which is separate from the one for
333 # the non-tunneled EAP module. Inside of the
334 # TTLS tunnel, we recommend using EAP-MD5.
335 # If the request does not contain an EAP
336 # conversation, then this configuration entry
338 default_eap_type = md5
340 # The tunneled authentication request does
341 # not usually contain useful attributes
342 # like 'Calling-Station-Id', etc. These
343 # attributes are outside of the tunnel,
344 # and normally unavailable to the tunneled
345 # authentication request.
347 # By setting this configuration entry to
348 # 'yes', any attribute which NOT in the
349 # tunneled authentication request, but
350 # which IS available outside of the tunnel,
351 # is copied to the tunneled request.
353 # allowed values: {no, yes}
354 copy_request_to_tunnel = no
356 # The reply attributes sent to the NAS are
357 # usually based on the name of the user
358 # 'outside' of the tunnel (usually
359 # 'anonymous'). If you want to send the
360 # reply attributes based on the user name
361 # inside of the tunnel, then set this
362 # configuration entry to 'yes', and the reply
363 # to the NAS will be taken from the reply to
364 # the tunneled request.
366 # allowed values: {no, yes}
367 use_tunneled_reply = no
370 # The inner tunneled request can be sent
371 # through a virtual server constructed
372 # specifically for this purpose.
374 # If this entry is commented out, the inner
375 # tunneled request will be sent through
376 # the virtual server that processed the
379 virtual_server = "inner-tunnel"
381 # This has the same meaning as the
382 # same field in the "tls" module, above.
383 # The default value here is "yes".
384 # include_length = yes
387 ##################################################
389 # !!!!! WARNINGS for Windows compatibility !!!!!
391 ##################################################
393 # If you see the server send an Access-Challenge,
394 # and the client never sends another Access-Request,
399 # The server certificate has to have special OID's
400 # in it, or else the Microsoft clients will silently
401 # fail. See the "scripts/xpextensions" file for
402 # details, and the following page:
404 # http://support.microsoft.com/kb/814394/en-us
406 # For additional Windows XP SP2 issues, see:
408 # http://support.microsoft.com/kb/885453/en-us
410 # Note that we do not necessarily agree with their
411 # explanation... but the fix does appear to work.
413 ##################################################
416 # The tunneled EAP session needs a default EAP type
417 # which is separate from the one for the non-tunneled
418 # EAP module. Inside of the TLS/PEAP tunnel, we
419 # recommend using EAP-MS-CHAPv2.
421 # The PEAP module needs the TLS module to be installed
422 # and configured, in order to use the TLS tunnel
423 # inside of the EAP packet. You will still need to
424 # configure the TLS module, even if you do not want
425 # to deploy EAP-TLS in your network. Users will not
426 # be able to request EAP-TLS, as it requires them to
427 # have a client certificate. EAP-PEAP does not
428 # require a client certificate.
431 # You can make PEAP require a client cert by setting
433 # EAP-TLS-Require-Client-Cert = Yes
435 # in the control items for a request.
438 # The tunneled EAP session needs a default
439 # EAP type which is separate from the one for
440 # the non-tunneled EAP module. Inside of the
441 # PEAP tunnel, we recommend using MS-CHAPv2,
442 # as that is the default type supported by
444 default_eap_type = mschapv2
446 # the PEAP module also has these configuration
447 # items, which are the same as for TTLS.
448 copy_request_to_tunnel = no
449 use_tunneled_reply = no
451 # When the tunneled session is proxied, the
452 # home server may not understand EAP-MSCHAP-V2.
453 # Set this entry to "no" to proxy the tunneled
454 # EAP-MSCHAP-V2 as normal MSCHAPv2.
455 # proxy_tunneled_request_as_eap = yes
458 # The inner tunneled request can be sent
459 # through a virtual server constructed
460 # specifically for this purpose.
462 # If this entry is commented out, the inner
463 # tunneled request will be sent through
464 # the virtual server that processed the
467 virtual_server = "inner-tunnel"
471 # This takes no configuration.
473 # Note that it is the EAP MS-CHAPv2 sub-module, not
474 # the main 'mschap' module.
476 # Note also that in order for this sub-module to work,
477 # the main 'mschap' module MUST ALSO be configured.
479 # This module is the *Microsoft* implementation of MS-CHAPv2
480 # in EAP. There is another (incompatible) implementation
481 # of MS-CHAPv2 in EAP by Cisco, which FreeRADIUS does not