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.
15 # Invoke the default supported EAP type when
16 # EAP-Identity response is received.
18 # The incoming EAP messages DO NOT specify which EAP
19 # type they will be using, so it MUST be set here.
21 # For now, only one default EAP type may be used at a time.
23 # If the EAP-Type attribute is set by another module,
24 # then that EAP type takes precedence over the
25 # default type configured here.
27 default_eap_type = md5
29 # A list is maintained to correlate EAP-Response
30 # packets with EAP-Request packets. After a
31 # configurable length of time, entries in the list
32 # expire, and are deleted.
36 # There are many EAP types, but the server has support
37 # for only a limited subset. If the server receives
38 # a request for an EAP type it does not support, then
39 # it normally rejects the request. By setting this
40 # configuration to "yes", you can tell the server to
41 # instead keep processing the request. Another module
42 # MUST then be configured to proxy the request to
43 # another RADIUS server which supports that EAP type.
45 # If another module is NOT configured to handle the
46 # request, then the request will still end up being
48 ignore_unknown_eap_types = no
50 # Cisco AP1230B firmware 12.2(13)JA1 has a bug. When given
51 # a User-Name attribute in an Access-Accept, it copies one
52 # more byte than it should.
54 # We can work around it by configurably adding an extra
56 cisco_accounting_username_bug = no
59 # Help prevent DoS attacks by limiting the number of
60 # sessions that the server is tracking. For simplicity,
61 # this is taken from the "max_requests" directive in
63 max_sessions = ${max_requests}
68 # We do NOT recommend using EAP-MD5 authentication
69 # for wireless connections. It is insecure, and does
70 # not provide for dynamic WEP keys.
76 # EAP-pwd -- secure password-based authentication
82 # server_id = theserver@example.com
84 # This has the same meaning as for TLS.
85 # fragment_size = 1020
87 # The virtual server which determines the
88 # "known good" password for the user.
89 # Note that unlike TLS, only the "authorize"
90 # section is processed. EAP-PWD requests can be
91 # distinguished by having a User-Name, but
92 # no User-Password, CHAP-Password, EAP-Message, etc.
93 # virtual_server = "inner-tunnel"
98 # We do not recommend using LEAP in new deployments. See:
99 # http://www.securiteam.com/tools/5TP012ACKE.html
101 # Cisco LEAP uses the MS-CHAP algorithm (but not
102 # the MS-CHAP attributes) to perform it's authentication.
104 # As a result, LEAP *requires* access to the plain-text
105 # User-Password, or the NT-Password attributes.
106 # 'System' authentication is impossible with LEAP.
111 # Generic Token Card.
113 # Currently, this is only permitted inside of EAP-TTLS,
114 # or EAP-PEAP. The module "challenges" the user with
115 # text, and the response from the user is taken to be
118 # Proxying the tunneled EAP-GTC session is a bad idea,
119 # the users password will go over the wire in plain-text,
123 # The default challenge, which many clients
125 #challenge = "Password: "
127 # The plain-text response which comes back
128 # is put into a User-Password attribute,
129 # and passed to another module for
130 # authentication. This allows the EAP-GTC
131 # response to be checked against plain-text,
132 # or crypt'd passwords.
134 # If you say "Local" instead of "PAP", then
135 # the module will look for a User-Password
136 # configured for the request, and do the
137 # authentication itself.
142 ## Common TLS configuration for TLS-based EAP types
144 # See raddb/certs/README for additional comments
147 # If OpenSSL was not found at the time the server was
148 # built, the "tls", "ttls", and "peap" sections will
151 # If you do not currently have certificates signed by
152 # a trusted CA you may use the 'snakeoil' certificates.
153 # Included with the server in raddb/certs.
155 # If these certificates have not been auto-generated:
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 ca_file = ${cadir}/ca.pem
200 # OpenSSL will automatically create certificate chains,
201 # unless we tell it to not do that. The problem is that
202 # it sometimes gets the chains right from a certificate
203 # signature view, but wrong from the clients view.
205 # When setting "auto_chain = no", the server certificate
206 # file MUST include the full certificate chain.
210 # If OpenSSL supports TLS-PSK, then we can use
211 # a PSK identity and (hex) password. When the
212 # following two configuration items are specified,
213 # then certificate-based configuration items are
216 # private_key_password
222 # For now, the identity is fixed, and must be the
223 # same on the client. The passphrase must be a hex
224 # value, and can be up to 256 hex digits.
226 # Future versions of the server may be able to
227 # look up the shared key (hexphrase) based on the
230 # psk_identity = "test"
231 # psk_hexphrase = "036363823"
234 # For DH cipher suites to work, you have to
235 # run OpenSSL to create the DH file first:
237 # openssl dhparam -out certs/dh 2048
239 dh_file = ${certdir}/dh
242 # If your system doesn't have /dev/urandom,
243 # you will need to create this file, and
244 # periodically change its contents.
246 # For security reasons, FreeRADIUS doesn't
247 # write to files in its configuration
250 # random_file = /dev/urandom
253 # This can never exceed the size of a RADIUS
254 # packet (4096 bytes), and is preferably half
255 # that, to accommodate other attributes in
256 # RADIUS packet. On most APs the MAX packet
257 # length is configured between 1500 - 1600
258 # In these cases, fragment size should be
261 # fragment_size = 1024
263 # include_length is a flag which is
264 # by default set to yes If set to
265 # yes, Total Length of the message is
266 # included in EVERY packet we send.
267 # If set to no, Total Length of the
268 # message is included ONLY in the
269 # First packet of a fragment series.
271 # include_length = yes
274 # Check the Certificate Revocation List
276 # 1) Copy CA certificates and CRLs to same directory.
277 # 2) Execute 'c_rehash <CA certs&CRLs Directory>'.
278 # 'c_rehash' is OpenSSL's command.
279 # 3) uncomment the lines below.
283 # Check if intermediate CAs have been revoked.
284 # check_all_crl = yes
289 # If check_cert_issuer is set, the value will
290 # be checked against the DN of the issuer in
291 # the client certificate. If the values do not
292 # match, the certificate verification will fail,
293 # rejecting the user.
295 # In 2.1.10 and later, this check can be done
296 # more generally by checking the value of the
297 # TLS-Client-Cert-Issuer attribute. This check
298 # can be done via any mechanism you choose.
300 # check_cert_issuer = "/C=GB/ST=Berkshire/L=Newbury/O=My Company Ltd"
303 # If check_cert_cn is set, the value will
304 # be xlat'ed and checked against the CN
305 # in the client certificate. If the values
306 # do not match, the certificate verification
307 # will fail rejecting the user.
309 # This check is done only if the previous
310 # "check_cert_issuer" is not set, or if
311 # the check succeeds.
313 # In 2.1.10 and later, this check can be done
314 # more generally by checking the value of the
315 # TLS-Client-Cert-CN attribute. This check
316 # can be done via any mechanism you choose.
318 # check_cert_cn = %{User-Name}
320 # Set this option to specify the allowed
321 # TLS cipher suites. The format is listed
322 # in "man 1 ciphers".
324 # For EAP-FAST, use "ALL:!EXPORT:!eNULL:!SSLv2"
326 cipher_list = "DEFAULT"
328 # Work-arounds for OpenSSL nonsense
329 # OpenSSL 1.0.1f and 1.0.1g do not calculate
330 # the EAP keys correctly. The fix is to upgrade
331 # OpenSSL, or disable TLS 1.2 here.
333 # For EAP-FAST, this MUST be set to "yes".
335 # disable_tlsv1_2 = no
340 # Elliptical cryptography configuration
342 # Only for OpenSSL >= 0.9.8.f
344 ecdh_curve = "prime256v1"
347 # Session resumption / fast reauthentication
350 # The cache contains the following information:
352 # session Id - unique identifier, managed by SSL
353 # User-Name - from the Access-Accept
354 # Stripped-User-Name - from the Access-Request
355 # Cached-Session-Policy - from the Access-Accept
357 # The "Cached-Session-Policy" is the name of a
358 # policy which should be applied to the cached
359 # session. This policy can be used to assign
360 # VLANs, IP addresses, etc. It serves as a useful
361 # way to re-apply the policy from the original
362 # Access-Accept to the subsequent Access-Accept
363 # for the cached session.
365 # On session resumption, these attributes are
366 # copied from the cache, and placed into the
369 # You probably also want "use_tunneled_reply = yes"
370 # when using fast session resumption.
374 # Enable it. The default is "no". Deleting the entire "cache"
375 # subsection also disables caching.
377 # You can disallow resumption for a particular user by adding the
378 # following attribute to the control item list:
380 # Allow-Session-Resumption = No
382 # If "enable = no" below, you CANNOT enable resumption for just one
383 # user by setting the above attribute to "yes".
388 # Lifetime of the cached entries, in hours. The sessions will be
389 # deleted/invalidated after this time.
391 lifetime = 24 # hours
394 # The maximum number of entries in the
395 # cache. Set to "0" for "infinite".
397 # This could be set to the number of users
398 # who are logged in... which can be a LOT.
403 # Internal "name" of the session cache. Used to
404 # distinguish which TLS context sessions belong to.
406 # The server will generate a random value if unset.
407 # This will change across server restart so you MUST
408 # set the "name" if you want to persist sessions (see
414 # Simple directory-based storage of sessions.
415 # Two files per session will be written, the SSL
416 # state and the cached VPs. This will persist session
417 # across server restarts.
419 # The server will need write perms, and the directory
420 # should be secured from anyone else. You might want
421 # a script to remove old files from here periodically:
423 # find ${logdir}/tlscache -mtime +2 -exec rm -f {} \;
425 # This feature REQUIRES "name" option be set above.
427 #persist_dir = "${logdir}/tlscache"
431 # As of version 2.1.10, client certificates can be
432 # validated via an external command. This allows
433 # dynamic CRLs or OCSP to be used.
435 # This configuration is commented out in the
436 # default configuration. Uncomment it, and configure
437 # the correct paths below to enable it.
439 # If OCSP checking is enabled, and the OCSP checks fail,
440 # the verify section is not run.
442 # If OCSP checking is disabled, the verify section is
443 # run on successful certificate validation.
446 # If the OCSP checks succeed, the verify section
447 # is run to allow additional checks.
449 # If you want to skip verify on OCSP success,
450 # uncomment this configuration item, and set it
452 # skip_if_ocsp_ok = no
454 # A temporary directory where the client
455 # certificates are stored. This directory
456 # MUST be owned by the UID of the server,
457 # and MUST not be accessible by any other
458 # users. When the server starts, it will do
459 # "chmod go-rwx" on the directory, for
460 # security reasons. The directory MUST
461 # exist when the server starts.
463 # You should also delete all of the files
464 # in the directory when the server starts.
465 # tmpdir = /tmp/radiusd
467 # The command used to verify the client cert.
468 # We recommend using the OpenSSL command-line
471 # The ${..ca_path} text is a reference to
472 # the ca_path variable defined above.
474 # The %{TLS-Client-Cert-Filename} is the name
475 # of the temporary file containing the cert
476 # in PEM format. This file is automatically
477 # deleted by the server when the command
479 # client = "/path/to/openssl verify -CApath ${..ca_path} %{TLS-Client-Cert-Filename}"
484 # Certificates can be verified against an OCSP
485 # Responder. This makes it possible to immediately
486 # revoke certificates without the distribution of
487 # new Certificate Revocation Lists (CRLs).
491 # Enable it. The default is "no".
492 # Deleting the entire "ocsp" subsection
493 # also disables ocsp checking
498 # The OCSP Responder URL can be automatically
499 # extracted from the certificate in question.
500 # To override the OCSP Responder URL set
501 # "override_cert_url = yes".
503 override_cert_url = yes
506 # If the OCSP Responder address is not extracted from
507 # the certificate, the URL can be defined here.
509 url = "http://127.0.0.1/ocsp/"
512 # If the OCSP Responder can not cope with nonce
513 # in the request, then it can be disabled here.
515 # For security reasons, disabling this option
516 # is not recommended as nonce protects against
519 # Note that Microsoft AD Certificate Services OCSP
520 # Responder does not enable nonce by default. It is
521 # more secure to enable nonce on the responder than
522 # to disable it in the query here.
523 # See http://technet.microsoft.com/en-us/library/cc770413%28WS.10%29.aspx
528 # Number of seconds before giving up waiting
529 # for OCSP response. 0 uses system default.
534 # Normally an error in querying the OCSP
535 # responder (no response from server, server did
536 # not understand the request, etc) will result in
537 # a validation failure.
539 # To treat these errors as 'soft' failures and
540 # still accept the certificate, enable this
543 # Warning: this may enable clients with revoked
544 # certificates to connect if the OCSP responder
545 # is not available. Use with caution.
553 # As of Version 3.0, the TLS configuration for TLS-based
554 # EAP types is above in the "tls-config" section.
557 # Point to the common TLS configuration
561 # As part of checking a client certificate, the EAP-TLS
562 # sets some attributes such as TLS-Client-Cert-CN. This
563 # virtual server has access to these attributes, and can
564 # be used to accept or reject the request.
566 # virtual_server = check-eap-tls
572 # The TTLS module implements the EAP-TTLS protocol,
573 # which can be described as EAP inside of Diameter,
574 # inside of TLS, inside of EAP, inside of RADIUS...
576 # Surprisingly, it works quite well.
579 # Which tls-config section the TLS negotiation parameters
580 # are in - see EAP-TLS above for an explanation.
582 # In the case that an old configuration from FreeRADIUS
583 # v2.x is being used, all the options of the tls-config
584 # section may also appear instead in the 'tls' section
585 # above. If that is done, the tls= option here (and in
586 # tls above) MUST be commented out.
590 # The tunneled EAP session needs a default EAP type
591 # which is separate from the one for the non-tunneled
592 # EAP module. Inside of the TTLS tunnel, we recommend
593 # using EAP-MD5. If the request does not contain an
594 # EAP conversation, then this configuration entry is
597 default_eap_type = md5
599 # The tunneled authentication request does not usually
600 # contain useful attributes like 'Calling-Station-Id',
601 # etc. These attributes are outside of the tunnel,
602 # and normally unavailable to the tunneled
603 # authentication request.
605 # By setting this configuration entry to 'yes',
606 # any attribute which is NOT in the tunneled
607 # authentication request, but which IS available
608 # outside of the tunnel, is copied to the tunneled
611 # allowed values: {no, yes}
613 copy_request_to_tunnel = no
616 # As of version 3.0.5, this configuration item
617 # is deprecated. Instead, you should use
619 # update outer.session-state {
624 # This will cache attributes for the final Access-Accept.
626 # The reply attributes sent to the NAS are usually
627 # based on the name of the user 'outside' of the
628 # tunnel (usually 'anonymous'). If you want to send
629 # the reply attributes based on the user name inside
630 # of the tunnel, then set this configuration entry to
631 # 'yes', and the reply to the NAS will be taken from
632 # the reply to the tunneled request.
634 # allowed values: {no, yes}
636 use_tunneled_reply = no
639 # The inner tunneled request can be sent
640 # through a virtual server constructed
641 # specifically for this purpose.
643 # If this entry is commented out, the inner
644 # tunneled request will be sent through
645 # the virtual server that processed the
648 virtual_server = "inner-tunnel"
650 # This has the same meaning, and overwrites, the
651 # same field in the "tls" configuration, above.
652 # The default value here is "yes".
654 # include_length = yes
657 # Unlike EAP-TLS, EAP-TTLS does not require a client
658 # certificate. However, you can require one by setting the
659 # following option. You can also override this option by
662 # EAP-TLS-Require-Client-Cert = Yes
664 # in the control items for a request.
666 # require_client_cert = yes
673 ##################################################
675 # !!!!! WARNINGS for Windows compatibility !!!!!
677 ##################################################
679 # If you see the server send an Access-Challenge,
680 # and the client never sends another Access-Request,
685 # The server certificate has to have special OID's
686 # in it, or else the Microsoft clients will silently
687 # fail. See the "scripts/xpextensions" file for
688 # details, and the following page:
690 # http://support.microsoft.com/kb/814394/en-us
692 # For additional Windows XP SP2 issues, see:
694 # http://support.microsoft.com/kb/885453/en-us
697 # If is still doesn't work, and you're using Samba,
698 # you may be encountering a Samba bug. See:
700 # https://bugzilla.samba.org/show_bug.cgi?id=6563
702 # Note that we do not necessarily agree with their
703 # explanation... but the fix does appear to work.
705 ##################################################
708 # The tunneled EAP session needs a default EAP type
709 # which is separate from the one for the non-tunneled
710 # EAP module. Inside of the TLS/PEAP tunnel, we
711 # recommend using EAP-MS-CHAPv2.
714 # Which tls-config section the TLS negotiation parameters
715 # are in - see EAP-TLS above for an explanation.
717 # In the case that an old configuration from FreeRADIUS
718 # v2.x is being used, all the options of the tls-config
719 # section may also appear instead in the 'tls' section
720 # above. If that is done, the tls= option here (and in
721 # tls above) MUST be commented out.
725 # The tunneled EAP session needs a default
726 # EAP type which is separate from the one for
727 # the non-tunneled EAP module. Inside of the
728 # PEAP tunnel, we recommend using MS-CHAPv2,
729 # as that is the default type supported by
732 default_eap_type = mschapv2
734 # The PEAP module also has these configuration
735 # items, which are the same as for TTLS.
737 copy_request_to_tunnel = no
740 # As of version 3.0.5, this configuration item
741 # is deprecated. Instead, you should use
743 # update outer.session-state {
748 # This will cache attributes for the final Access-Accept.
750 use_tunneled_reply = no
752 # When the tunneled session is proxied, the
753 # home server may not understand EAP-MSCHAP-V2.
754 # Set this entry to "no" to proxy the tunneled
755 # EAP-MSCHAP-V2 as normal MSCHAPv2.
757 # proxy_tunneled_request_as_eap = yes
760 # The inner tunneled request can be sent
761 # through a virtual server constructed
762 # specifically for this purpose.
764 # If this entry is commented out, the inner
765 # tunneled request will be sent through
766 # the virtual server that processed the
769 virtual_server = "inner-tunnel"
771 # This option enables support for MS-SoH
772 # see doc/SoH.txt for more info.
773 # It is disabled by default.
778 # The SoH reply will be turned into a request which
779 # can be sent to a specific virtual server:
781 # soh_virtual_server = "soh-server"
784 # Unlike EAP-TLS, PEAP does not require a client certificate.
785 # However, you can require one by setting the following
786 # option. You can also override this option by setting
788 # EAP-TLS-Require-Client-Cert = Yes
790 # in the control items for a request.
792 # require_client_cert = yes
796 # This takes no configuration.
798 # Note that it is the EAP MS-CHAPv2 sub-module, not
799 # the main 'mschap' module.
801 # Note also that in order for this sub-module to work,
802 # the main 'mschap' module MUST ALSO be configured.
804 # This module is the *Microsoft* implementation of MS-CHAPv2
805 # in EAP. There is another (incompatible) implementation
806 # of MS-CHAPv2 in EAP by Cisco, which FreeRADIUS does not
810 # Prior to version 2.1.11, the module never
811 # sent the MS-CHAP-Error message to the
812 # client. This worked, but it had issues
813 # when the cached password was wrong. The
814 # server *should* send "E=691 R=0" to the
815 # client, which tells it to prompt the user
816 # for a new password.
818 # The default is to behave as in 2.1.10 and
819 # earlier, which is known to work. If you
820 # set "send_error = yes", then the error
821 # message will be sent back to the client.
822 # This *may* help some clients work better,
823 # but *may* also cause other clients to stop
828 # Server identifier to send back in the challenge.
829 # This should generally be the host name of the
830 # RADIUS server. Or, some information to uniquely
832 # identity = "FreeRADIUS"
837 # The FAST module implements the EAP-FAST protocol
840 # Point to the common TLS configuration
842 # cipher_list though must include "ADH" for anonymous provisioning.
843 # This is not as straight forward as appending "ADH" alongside
844 # "DEFAULT" as "DEFAULT" contains "!aNULL" so instead it is
845 # recommended "ALL:!EXPORT:!eNULL:!SSLv2" is used
849 # PAC lifetime in seconds (default: seven days)
851 # pac_lifetime = 604800
853 # Authority ID of the server
855 # if you are running a cluster of RADIUS servers, you should make
856 # the value chosen here (and for "pac_opaque_key") the same on all
857 # your RADIUS servers. This value should be unique to your
858 # installation. We suggest using a domain name.
860 # authority_identity = "1234"
862 # PAC Opaque encryption key (must be exactly 32 bytes in size)
864 # This value MUST be secret, and MUST be generated using
865 # a secure method, such as via 'openssl rand -hex 32'
867 # pac_opaque_key = "0123456789abcdef0123456789ABCDEF"
869 # Same as for TTLS, PEAP, etc.
871 # virtual_server = inner-tunnel