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.
79 # EAP-pwd -- secure password-based authentication
85 server_id = theserver@example.com
87 # This has the same meaning as for TLS.
90 # The virtual server which determines the
91 # "known good" password for the user.
92 # Note that unlike TLS, only the "authorize"
93 # section is processed. EAP-PWD requests can be
94 # distinguished by having a User-Name, but
95 # no User-Password, CHAP-Password, EAP-Message, etc.
96 virtual_server = "inner-tunnel"
101 # We do not recommend using LEAP in new deployments. See:
102 # http://www.securiteam.com/tools/5TP012ACKE.html
104 # Cisco LEAP uses the MS-CHAP algorithm (but not
105 # the MS-CHAP attributes) to perform it's authentication.
107 # As a result, LEAP *requires* access to the plain-text
108 # User-Password, or the NT-Password attributes.
109 # 'System' authentication is impossible with LEAP.
114 # Generic Token Card.
116 # Currently, this is only permitted inside of EAP-TTLS,
117 # or EAP-PEAP. The module "challenges" the user with
118 # text, and the response from the user is taken to be
121 # Proxying the tunneled EAP-GTC session is a bad idea,
122 # the users password will go over the wire in plain-text,
126 # The default challenge, which many clients
128 #challenge = "Password: "
130 # The plain-text response which comes back
131 # is put into a User-Password attribute,
132 # and passed to another module for
133 # authentication. This allows the EAP-GTC
134 # response to be checked against plain-text,
135 # or crypt'd passwords.
137 # If you say "Local" instead of "PAP", then
138 # the module will look for a User-Password
139 # configured for the request, and do the
140 # authentication itself.
145 ## Common TLS configuration for TLS-based EAP types
147 # See raddb/certs/README for additional comments
150 # If OpenSSL was not found at the time the server was
151 # built, the "tls", "ttls", and "peap" sections will
154 # Otherwise, when the server first starts in debugging
155 # mode, test certificates will be created. See the
156 # "make_cert_command" below for details, and the README
157 # file in raddb/certs
159 # These test certificates SHOULD NOT be used in a normal
160 # deployment. They are created only to make it easier
161 # to install the server, and to perform some simple
162 # tests with EAP-TLS, TTLS, or PEAP.
166 # http://www.dslreports.com/forum/remark,9286052~mode=flat
168 # Note that you should NOT use a globally known CA here!
169 # e.g. using a Verisign cert as a "known CA" means that
170 # ANYONE who has a certificate signed by them can
171 # authenticate via EAP-TLS! This is likely not what you want.
172 tls-config tls-common {
173 private_key_password = whatever
174 private_key_file = ${certdir}/server.pem
176 # If Private key & Certificate are located in
177 # the same file, then private_key_file &
178 # certificate_file must contain the same file
181 # If CA_file (below) is not used, then the
182 # certificate_file below MUST include not
183 # only the server certificate, but ALSO all
184 # of the CA certificates used to sign the
185 # server certificate.
186 certificate_file = ${certdir}/server.pem
188 # Trusted Root CA list
190 # ALL of the CA's in this list will be trusted
191 # to issue client certificates for authentication.
193 # In general, you should use self-signed
194 # certificates for 802.1x (EAP) authentication.
195 # In that case, this CA file should contain
196 # *one* CA certificate.
198 # This parameter is used only for EAP-TLS,
199 # when you issue client certificates. If you do
200 # not use client certificates, and you do not want
201 # to permit EAP-TLS authentication, then delete
202 # this configuration item.
203 CA_file = ${cadir}/ca.pem
206 # If OpenSSL supports TLS-PSK, then we can use
207 # a PSK identity and (hex) password. When the
208 # following two configuration items are specified,
209 # then certificate-based configuration items are
212 # private_key_password
218 # For now, the identity is fixed, and must be the
219 # same on the client. The passphrase must be a hex
220 # value, and can be up to 256 hex digits.
222 # Future versions of the server may be able to
223 # look up the shared key (hexphrase) based on the
226 # psk_identity = "test"
227 # psk_hexphrase = "036363823"
230 # For DH cipher suites to work, you have to
231 # run OpenSSL to create the DH file first:
233 # openssl dhparam -out certs/dh 1024
235 dh_file = ${certdir}/dh
236 random_file = ${certdir}/random
239 # This can never exceed the size of a RADIUS
240 # packet (4096 bytes), and is preferably half
241 # that, to accomodate other attributes in
242 # RADIUS packet. On most APs the MAX packet
243 # length is configured between 1500 - 1600
244 # In these cases, fragment size should be
247 # fragment_size = 1024
249 # include_length is a flag which is
250 # by default set to yes If set to
251 # yes, Total Length of the message is
252 # included in EVERY packet we send.
253 # If set to no, Total Length of the
254 # message is included ONLY in the
255 # First packet of a fragment series.
257 # include_length = yes
259 # Check the Certificate Revocation List
261 # 1) Copy CA certificates and CRLs to same directory.
262 # 2) Execute 'c_rehash <CA certs&CRLs Directory>'.
263 # 'c_rehash' is OpenSSL's command.
264 # 3) uncomment the line below.
270 # If check_cert_issuer is set, the value will
271 # be checked against the DN of the issuer in
272 # the client certificate. If the values do not
273 # match, the cerficate verification will fail,
274 # rejecting the user.
276 # In 2.1.10 and later, this check can be done
277 # more generally by checking the value of the
278 # TLS-Client-Cert-Issuer attribute. This check
279 # can be done via any mechanism you choose.
281 # check_cert_issuer = "/C=GB/ST=Berkshire/L=Newbury/O=My Company Ltd"
284 # If check_cert_cn is set, the value will
285 # be xlat'ed and checked against the CN
286 # in the client certificate. If the values
287 # do not match, the certificate verification
288 # will fail rejecting the user.
290 # This check is done only if the previous
291 # "check_cert_issuer" is not set, or if
292 # the check succeeds.
294 # In 2.1.10 and later, this check can be done
295 # more generally by checking the value of the
296 # TLS-Client-Cert-CN attribute. This check
297 # can be done via any mechanism you choose.
299 # check_cert_cn = %{User-Name}
301 # Set this option to specify the allowed
302 # TLS cipher suites. The format is listed
303 # in "man 1 ciphers".
304 cipher_list = "DEFAULT"
308 # This command creates the initial "snake oil"
309 # certificates when the server is run as root,
310 # and via "radiusd -X".
312 # As of 2.1.11, it *also* checks the server
313 # certificate for validity, including expiration.
314 # This means that radiusd will refuse to start
315 # when the certificate has expired. The alternative
316 # is to have the 802.1X clients refuse to connect
317 # when they discover the certificate has expired.
319 # Debugging client issues is hard, so it's better
320 # for the server to print out an error message,
321 # and refuse to start.
323 make_cert_command = "${certdir}/bootstrap"
326 # Elliptical cryptography configuration
328 # Only for OpenSSL >= 0.9.8.f
330 ecdh_curve = "prime256v1"
333 # Session resumption / fast reauthentication
336 # The cache contains the following information:
338 # session Id - unique identifier, managed by SSL
339 # User-Name - from the Access-Accept
340 # Stripped-User-Name - from the Access-Request
341 # Cached-Session-Policy - from the Access-Accept
343 # The "Cached-Session-Policy" is the name of a
344 # policy which should be applied to the cached
345 # session. This policy can be used to assign
346 # VLANs, IP addresses, etc. It serves as a useful
347 # way to re-apply the policy from the original
348 # Access-Accept to the subsequent Access-Accept
349 # for the cached session.
351 # On session resumption, these attributes are
352 # copied from the cache, and placed into the
355 # You probably also want "use_tunneled_reply = yes"
356 # when using fast session resumption.
360 # Enable it. The default is "no".
361 # Deleting the entire "cache" subsection
362 # Also disables caching.
364 # You can disallow resumption for a
365 # particular user by adding the following
366 # attribute to the control item list:
368 # Allow-Session-Resumption = No
370 # If "enable = no" below, you CANNOT
371 # enable resumption for just one user
372 # by setting the above attribute to "yes".
377 # Lifetime of the cached entries, in hours.
378 # The sessions will be deleted after this
381 lifetime = 24 # hours
384 # The maximum number of entries in the
385 # cache. Set to "0" for "infinite".
387 # This could be set to the number of users
388 # who are logged in... which can be a LOT.
394 # As of version 2.1.10, client certificates can be
395 # validated via an external command. This allows
396 # dynamic CRLs or OCSP to be used.
398 # This configuration is commented out in the
399 # default configuration. Uncomment it, and configure
400 # the correct paths below to enable it.
403 # A temporary directory where the client
404 # certificates are stored. This directory
405 # MUST be owned by the UID of the server,
406 # and MUST not be accessible by any other
407 # users. When the server starts, it will do
408 # "chmod go-rwx" on the directory, for
409 # security reasons. The directory MUST
410 # exist when the server starts.
412 # You should also delete all of the files
413 # in the directory when the server starts.
414 # tmpdir = /tmp/radiusd
416 # The command used to verify the client cert.
417 # We recommend using the OpenSSL command-line
420 # The ${..CA_path} text is a reference to
421 # the CA_path variable defined above.
423 # The %{TLS-Client-Cert-Filename} is the name
424 # of the temporary file containing the cert
425 # in PEM format. This file is automatically
426 # deleted by the server when the command
428 # client = "/path/to/openssl verify -CApath ${..CA_path} %{TLS-Client-Cert-Filename}"
433 # Certificates can be verified against an OCSP
434 # Responder. This makes it possible to immediately
435 # revoke certificates without the distribution of
436 # new Certificate Revokation Lists (CRLs).
440 # Enable it. The default is "no".
441 # Deleting the entire "ocsp" subsection
442 # Also disables ocsp checking
447 # The OCSP Responder URL can be automatically
448 # extracted from the certificate in question.
449 # To override the OCSP Responder URL set
450 # "override_cert_url = yes".
452 override_cert_url = yes
455 # If the OCSP Responder address is not
456 # extracted from the certificate, the
457 # URL can be defined here.
460 # Limitation: Currently the HTTP
461 # Request is not sending the "Host: "
462 # information to the web-server. This
463 # can be a problem if the OCSP
464 # Responder is running as a vhost.
466 url = "http://127.0.0.1/ocsp/"
469 # If the OCSP Responder can not cope with nonce
470 # in the request, then it can be disabled here.
472 # For security reasons, disabling this option
473 # is not recommended as nonce protects against
476 # Note that Microsoft AD Certificate Services OCSP
477 # Responder does not enable nonce by default. It is
478 # more secure to enable nonce on the responder than
479 # to disable it in the query here.
480 # See http://technet.microsoft.com/en-us/library/cc770413%28WS.10%29.aspx
485 # Number of seconds before giving up waiting
486 # for OCSP response. 0 uses system default.
491 # Normally an error in querying the OCSP
492 # responder (no response from server, server did
493 # not understand the request, etc) will result in
494 # a validation failure.
496 # To treat these errors as 'soft' failures and
497 # still accept the certificate, enable this
500 # Warning: this may enable clients with revoked
501 # certificates to connect if the OCSP responder
502 # is not available. Use with caution.
510 # As of Version 3.0, the TLS configuration for TLS-based
511 # EAP types is above in the "tls-config" section.
514 # Point to the common TLS configuration
518 # As part of checking a client certificate, the EAP-TLS
519 # sets some attributes such as TLS-Client-Cert-CN. This
520 # virtual server has access to these attributes, and can
521 # be used to accept or reject the request.
523 # virtual_server = check-eap-tls
529 # The TTLS module implements the EAP-TTLS protocol,
530 # which can be described as EAP inside of Diameter,
531 # inside of TLS, inside of EAP, inside of RADIUS...
533 # Surprisingly, it works quite well.
535 # EAP-TTLS does not normally require a client certificate,
536 # but you can make it require one by setting
538 # EAP-TLS-Require-Client-Cert = Yes
540 # in the control items for a request.
543 # Which tls-config section the TLS negotiation parameters
544 # are in - see EAP-TLS above for an explanation.
546 # In the case that an old configuration from FreeRADIUS
547 # v2.x is being used, all the options of the tls-config
548 # section may also appear instead in the 'tls' section
549 # above. If that is done, the tls= option here (and in
550 # tls above) MUST be commented out.
554 # The tunneled EAP session needs a default EAP type
555 # which is separate from the one for the non-tunneled
556 # EAP module. Inside of the TTLS tunnel, we recommend
557 # using EAP-MD5. If the request does not contain an
558 # EAP conversation, then this configuration entry is
561 default_eap_type = md5
563 # The tunneled authentication request does not usually
564 # contain useful attributes like 'Calling-Station-Id',
565 # etc. These attributes are outside of the tunnel,
566 # and normally unavailable to the tunneled
567 # authentication request.
569 # By setting this configuration entry to 'yes',
570 # any attribute which is NOT in the tunneled
571 # authentication request, but which IS available
572 # outside of the tunnel, is copied to the tunneled
575 # allowed values: {no, yes}
577 copy_request_to_tunnel = no
579 # The reply attributes sent to the NAS are usually
580 # based on the name of the user 'outside' of the
581 # tunnel (usually 'anonymous'). If you want to send
582 # the reply attributes based on the user name inside
583 # of the tunnel, then set this configuration entry to
584 # 'yes', and the reply to the NAS will be taken from
585 # the reply to the tunneled request.
587 # allowed values: {no, yes}
589 use_tunneled_reply = no
592 # The inner tunneled request can be sent
593 # through a virtual server constructed
594 # specifically for this purpose.
596 # If this entry is commented out, the inner
597 # tunneled request will be sent through
598 # the virtual server that processed the
601 virtual_server = "inner-tunnel"
603 # This has the same meaning, and overwrites, the
604 # same field in the "tls" configuration, above.
605 # The default value here is "yes".
607 # include_length = yes
614 ##################################################
616 # !!!!! WARNINGS for Windows compatibility !!!!!
618 ##################################################
620 # If you see the server send an Access-Challenge,
621 # and the client never sends another Access-Request,
626 # The server certificate has to have special OID's
627 # in it, or else the Microsoft clients will silently
628 # fail. See the "scripts/xpextensions" file for
629 # details, and the following page:
631 # http://support.microsoft.com/kb/814394/en-us
633 # For additional Windows XP SP2 issues, see:
635 # http://support.microsoft.com/kb/885453/en-us
638 # If is still doesn't work, and you're using Samba,
639 # you may be encountering a Samba bug. See:
641 # https://bugzilla.samba.org/show_bug.cgi?id=6563
643 # Note that we do not necessarily agree with their
644 # explanation... but the fix does appear to work.
646 ##################################################
649 # The tunneled EAP session needs a default EAP type
650 # which is separate from the one for the non-tunneled
651 # EAP module. Inside of the TLS/PEAP tunnel, we
652 # recommend using EAP-MS-CHAPv2.
654 # Unlike EAP-TLS, PEAP does not require a client certificate.
655 # However, you can require one by setting
657 # EAP-TLS-Require-Client-Cert = Yes
659 # in the control items for a request.
662 # Which tls-config section the TLS negotiation parameters
663 # are in - see EAP-TLS above for an explanation.
665 # In the case that an old configuration from FreeRADIUS
666 # v2.x is being used, all the options of the tls-config
667 # section may also appear instead in the 'tls' section
668 # above. If that is done, the tls= option here (and in
669 # tls above) MUST be commented out.
673 # The tunneled EAP session needs a default
674 # EAP type which is separate from the one for
675 # the non-tunneled EAP module. Inside of the
676 # PEAP tunnel, we recommend using MS-CHAPv2,
677 # as that is the default type supported by
680 default_eap_type = mschapv2
682 # The PEAP module also has these configuration
683 # items, which are the same as for TTLS.
685 copy_request_to_tunnel = no
686 use_tunneled_reply = no
688 # When the tunneled session is proxied, the
689 # home server may not understand EAP-MSCHAP-V2.
690 # Set this entry to "no" to proxy the tunneled
691 # EAP-MSCHAP-V2 as normal MSCHAPv2.
693 # proxy_tunneled_request_as_eap = yes
696 # The inner tunneled request can be sent
697 # through a virtual server constructed
698 # specifically for this purpose.
700 # If this entry is commented out, the inner
701 # tunneled request will be sent through
702 # the virtual server that processed the
705 virtual_server = "inner-tunnel"
707 # This option enables support for MS-SoH
708 # see doc/SoH.txt for more info.
709 # It is disabled by default.
714 # The SoH reply will be turned into a request which
715 # can be sent to a specific virtual server:
717 # soh_virtual_server = "soh-server"
721 # This takes no configuration.
723 # Note that it is the EAP MS-CHAPv2 sub-module, not
724 # the main 'mschap' module.
726 # Note also that in order for this sub-module to work,
727 # the main 'mschap' module MUST ALSO be configured.
729 # This module is the *Microsoft* implementation of MS-CHAPv2
730 # in EAP. There is another (incompatible) implementation
731 # of MS-CHAPv2 in EAP by Cisco, which FreeRADIUS does not
735 # Prior to version 2.1.11, the module never
736 # sent the MS-CHAP-Error message to the
737 # client. This worked, but it had issues
738 # when the cached password was wrong. The
739 # server *should* send "E=691 R=0" to the
740 # client, which tells it to prompt the user
741 # for a new password.
743 # The default is to behave as in 2.1.10 and
744 # earlier, which is known to work. If you
745 # set "send_error = yes", then the error
746 # message will be sent back to the client.
747 # This *may* help some clients work better,
748 # but *may* also cause other clients to stop