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 likely not what you want.
152 private_key_password = whatever
153 private_key_file = ${certdir}/server.pem
155 # If Private key & Certificate are located in
156 # the same file, then private_key_file &
157 # certificate_file must contain the same file
160 # If CA_file (below) is not used, then the
161 # certificate_file below MUST include not
162 # only the server certificate, but ALSO all
163 # of the CA certificates used to sign the
164 # server certificate.
165 certificate_file = ${certdir}/server.pem
167 # Trusted Root CA list
169 # ALL of the CA's in this list will be trusted
170 # to issue client certificates for authentication.
172 # In general, you should use self-signed
173 # certificates for 802.1x (EAP) authentication.
174 # In that case, this CA file should contain
175 # *one* CA certificate.
177 # This parameter is used only for EAP-TLS,
178 # when you issue client certificates. If you do
179 # not use client certificates, and you do not want
180 # to permit EAP-TLS authentication, then delete
181 # this configuration item.
182 CA_file = ${cadir}/ca.pem
185 # For DH cipher suites to work, you have to
186 # run OpenSSL to create the DH file first:
188 # openssl dhparam -out certs/dh 1024
190 dh_file = ${certdir}/dh
191 random_file = ${certdir}/random
194 # This can never exceed the size of a RADIUS
195 # packet (4096 bytes), and is preferably half
196 # that, to accomodate other attributes in
197 # RADIUS packet. On most APs the MAX packet
198 # length is configured between 1500 - 1600
199 # In these cases, fragment size should be
202 # fragment_size = 1024
204 # include_length is a flag which is
205 # by default set to yes If set to
206 # yes, Total Length of the message is
207 # included in EVERY packet we send.
208 # If set to no, Total Length of the
209 # message is included ONLY in the
210 # First packet of a fragment series.
212 # include_length = yes
214 # Check the Certificate Revocation List
216 # 1) Copy CA certificates and CRLs to same directory.
217 # 2) Execute 'c_rehash <CA certs&CRLs Directory>'.
218 # 'c_rehash' is OpenSSL's command.
219 # 3) uncomment the line below.
225 # If check_cert_issuer is set, the value will
226 # be checked against the DN of the issuer in
227 # the client certificate. If the values do not
228 # match, the cerficate verification will fail,
229 # rejecting the user.
231 # In 2.1.10 and later, this check can be done
232 # more generally by checking the value of the
233 # TLS-Client-Cert-Issuer attribute. This check
234 # can be done via any mechanism you choose.
236 # check_cert_issuer = "/C=GB/ST=Berkshire/L=Newbury/O=My Company Ltd"
239 # If check_cert_cn is set, the value will
240 # be xlat'ed and checked against the CN
241 # in the client certificate. If the values
242 # do not match, the certificate verification
243 # will fail rejecting the user.
245 # This check is done only if the previous
246 # "check_cert_issuer" is not set, or if
247 # the check succeeds.
249 # In 2.1.10 and later, this check can be done
250 # more generally by checking the value of the
251 # TLS-Client-Cert-CN attribute. This check
252 # can be done via any mechanism you choose.
254 # check_cert_cn = %{User-Name}
256 # Set this option to specify the allowed
257 # TLS cipher suites. The format is listed
258 # in "man 1 ciphers".
259 cipher_list = "DEFAULT"
263 # This command creates the initial "snake oil"
264 # certificates when the server is run as root,
265 # and via "radiusd -X".
267 # As of 2.1.11, it *also* checks the server
268 # certificate for validity, including expiration.
269 # This means that radiusd will refuse to start
270 # when the certificate has expired. The alternative
271 # is to have the 802.1X clients refuse to connect
272 # when they discover the certificate has expired.
274 # Debugging client issues is hard, so it's better
275 # for the server to print out an error message,
276 # and refuse to start.
278 make_cert_command = "${certdir}/bootstrap"
281 # Elliptical cryptography configuration
283 # Only for OpenSSL >= 0.9.8.f
285 ecdh_curve = "prime256v1"
288 # Session resumption / fast reauthentication
291 # The cache contains the following information:
293 # session Id - unique identifier, managed by SSL
294 # User-Name - from the Access-Accept
295 # Stripped-User-Name - from the Access-Request
296 # Cached-Session-Policy - from the Access-Accept
298 # The "Cached-Session-Policy" is the name of a
299 # policy which should be applied to the cached
300 # session. This policy can be used to assign
301 # VLANs, IP addresses, etc. It serves as a useful
302 # way to re-apply the policy from the original
303 # Access-Accept to the subsequent Access-Accept
304 # for the cached session.
306 # On session resumption, these attributes are
307 # copied from the cache, and placed into the
310 # You probably also want "use_tunneled_reply = yes"
311 # when using fast session resumption.
315 # Enable it. The default is "no".
316 # Deleting the entire "cache" subsection
317 # Also disables caching.
319 # You can disallow resumption for a
320 # particular user by adding the following
321 # attribute to the control item list:
323 # Allow-Session-Resumption = No
325 # If "enable = no" below, you CANNOT
326 # enable resumption for just one user
327 # by setting the above attribute to "yes".
332 # Lifetime of the cached entries, in hours.
333 # The sessions will be deleted after this
336 lifetime = 24 # hours
339 # The maximum number of entries in the
340 # cache. Set to "0" for "infinite".
342 # This could be set to the number of users
343 # who are logged in... which can be a LOT.
349 # As of version 2.1.10, client certificates can be
350 # validated via an external command. This allows
351 # dynamic CRLs or OCSP to be used.
353 # This configuration is commented out in the
354 # default configuration. Uncomment it, and configure
355 # the correct paths below to enable it.
358 # A temporary directory where the client
359 # certificates are stored. This directory
360 # MUST be owned by the UID of the server,
361 # and MUST not be accessible by any other
362 # users. When the server starts, it will do
363 # "chmod go-rwx" on the directory, for
364 # security reasons. The directory MUST
365 # exist when the server starts.
367 # You should also delete all of the files
368 # in the directory when the server starts.
369 # tmpdir = /tmp/radiusd
371 # The command used to verify the client cert.
372 # We recommend using the OpenSSL command-line
375 # The ${..CA_path} text is a reference to
376 # the CA_path variable defined above.
378 # The %{TLS-Client-Cert-Filename} is the name
379 # of the temporary file containing the cert
380 # in PEM format. This file is automatically
381 # deleted by the server when the command
383 # client = "/path/to/openssl verify -CApath ${..CA_path} %{TLS-Client-Cert-Filename}"
388 # Certificates can be verified against an OCSP
389 # Responder. This makes it possible to immediately
390 # revoke certificates without the distribution of
391 # new Certificate Revokation Lists (CRLs).
395 # Enable it. The default is "no".
396 # Deleting the entire "ocsp" subsection
397 # Also disables ocsp checking
402 # The OCSP Responder URL can be automatically
403 # extracted from the certificate in question.
404 # To override the OCSP Responder URL set
405 # "override_cert_url = yes".
407 override_cert_url = yes
410 # If the OCSP Responder address is not
411 # extracted from the certificate, the
412 # URL can be defined here.
415 # Limitation: Currently the HTTP
416 # Request is not sending the "Host: "
417 # information to the web-server. This
418 # can be a problem if the OCSP
419 # Responder is running as a vhost.
421 url = "http://127.0.0.1/ocsp/"
425 # The TTLS module implements the EAP-TTLS protocol,
426 # which can be described as EAP inside of Diameter,
427 # inside of TLS, inside of EAP, inside of RADIUS...
429 # Surprisingly, it works quite well.
431 # The TTLS module needs the TLS module to be installed
432 # and configured, in order to use the TLS tunnel
433 # inside of the EAP packet. You will still need to
434 # configure the TLS module, even if you do not want
435 # to deploy EAP-TLS in your network. Users will not
436 # be able to request EAP-TLS, as it requires them to
437 # have a client certificate. EAP-TTLS does not
438 # require a client certificate.
440 # You can make TTLS require a client cert by setting
442 # EAP-TLS-Require-Client-Cert = Yes
444 # in the control items for a request.
447 # The tunneled EAP session needs a default
448 # EAP type which is separate from the one for
449 # the non-tunneled EAP module. Inside of the
450 # TTLS tunnel, we recommend using EAP-MD5.
451 # If the request does not contain an EAP
452 # conversation, then this configuration entry
454 default_eap_type = md5
456 # The tunneled authentication request does
457 # not usually contain useful attributes
458 # like 'Calling-Station-Id', etc. These
459 # attributes are outside of the tunnel,
460 # and normally unavailable to the tunneled
461 # authentication request.
463 # By setting this configuration entry to
464 # 'yes', any attribute which NOT in the
465 # tunneled authentication request, but
466 # which IS available outside of the tunnel,
467 # is copied to the tunneled request.
469 # allowed values: {no, yes}
470 copy_request_to_tunnel = no
472 # The reply attributes sent to the NAS are
473 # usually based on the name of the user
474 # 'outside' of the tunnel (usually
475 # 'anonymous'). If you want to send the
476 # reply attributes based on the user name
477 # inside of the tunnel, then set this
478 # configuration entry to 'yes', and the reply
479 # to the NAS will be taken from the reply to
480 # the tunneled request.
482 # allowed values: {no, yes}
483 use_tunneled_reply = no
486 # The inner tunneled request can be sent
487 # through a virtual server constructed
488 # specifically for this purpose.
490 # If this entry is commented out, the inner
491 # tunneled request will be sent through
492 # the virtual server that processed the
495 virtual_server = "inner-tunnel"
497 # This has the same meaning as the
498 # same field in the "tls" module, above.
499 # The default value here is "yes".
500 # include_length = yes
503 ##################################################
505 # !!!!! WARNINGS for Windows compatibility !!!!!
507 ##################################################
509 # If you see the server send an Access-Challenge,
510 # and the client never sends another Access-Request,
515 # The server certificate has to have special OID's
516 # in it, or else the Microsoft clients will silently
517 # fail. See the "scripts/xpextensions" file for
518 # details, and the following page:
520 # http://support.microsoft.com/kb/814394/en-us
522 # For additional Windows XP SP2 issues, see:
524 # http://support.microsoft.com/kb/885453/en-us
527 # If is still doesn't work, and you're using Samba,
528 # you may be encountering a Samba bug. See:
530 # https://bugzilla.samba.org/show_bug.cgi?id=6563
532 # Note that we do not necessarily agree with their
533 # explanation... but the fix does appear to work.
535 ##################################################
538 # The tunneled EAP session needs a default EAP type
539 # which is separate from the one for the non-tunneled
540 # EAP module. Inside of the TLS/PEAP tunnel, we
541 # recommend using EAP-MS-CHAPv2.
543 # The PEAP module needs the TLS module to be installed
544 # and configured, in order to use the TLS tunnel
545 # inside of the EAP packet. You will still need to
546 # configure the TLS module, even if you do not want
547 # to deploy EAP-TLS in your network. Users will not
548 # be able to request EAP-TLS, as it requires them to
549 # have a client certificate. EAP-PEAP does not
550 # require a client certificate.
553 # You can make PEAP require a client cert by setting
555 # EAP-TLS-Require-Client-Cert = Yes
557 # in the control items for a request.
560 # The tunneled EAP session needs a default
561 # EAP type which is separate from the one for
562 # the non-tunneled EAP module. Inside of the
563 # PEAP tunnel, we recommend using MS-CHAPv2,
564 # as that is the default type supported by
566 default_eap_type = mschapv2
568 # the PEAP module also has these configuration
569 # items, which are the same as for TTLS.
570 copy_request_to_tunnel = no
571 use_tunneled_reply = no
573 # When the tunneled session is proxied, the
574 # home server may not understand EAP-MSCHAP-V2.
575 # Set this entry to "no" to proxy the tunneled
576 # EAP-MSCHAP-V2 as normal MSCHAPv2.
577 # proxy_tunneled_request_as_eap = yes
580 # The inner tunneled request can be sent
581 # through a virtual server constructed
582 # specifically for this purpose.
584 # If this entry is commented out, the inner
585 # tunneled request will be sent through
586 # the virtual server that processed the
589 virtual_server = "inner-tunnel"
591 # This option enables support for MS-SoH
592 # see doc/SoH.txt for more info.
593 # It is disabled by default.
598 # The SoH reply will be turned into a request which
599 # can be sent to a specific virtual server:
601 # soh_virtual_server = "soh-server"
605 # This takes no configuration.
607 # Note that it is the EAP MS-CHAPv2 sub-module, not
608 # the main 'mschap' module.
610 # Note also that in order for this sub-module to work,
611 # the main 'mschap' module MUST ALSO be configured.
613 # This module is the *Microsoft* implementation of MS-CHAPv2
614 # in EAP. There is another (incompatible) implementation
615 # of MS-CHAPv2 in EAP by Cisco, which FreeRADIUS does not
619 # Prior to version 2.1.11, the module never
620 # sent the MS-CHAP-Error message to the
621 # client. This worked, but it had issues
622 # when the cached password was wrong. The
623 # server *should* send "E=691 R=0" to the
624 # client, which tells it to prompt the user
625 # for a new password.
627 # The default is to behave as in 2.1.10 and
628 # earlier, which is known to work. If you
629 # set "send_error = yes", then the error
630 # message will be sent back to the client.
631 # This *may* help some clients work better,
632 # but *may* also cause other clients to stop