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. For simplicity,
64 # this is taken from the "max_requests" directive in
66 max_sessions = ${max_requests}
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.
88 # fragment_size = 1020
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 # If you do not currently have certificates signed by
155 # a trusted CA you may use the 'snakeoil' certificates.
156 # Included with the server in raddb/certs.
158 # If these certificates have not been auto-generated:
162 # These test certificates SHOULD NOT be used in a normal
163 # deployment. They are created only to make it easier
164 # to install the server, and to perform some simple
165 # tests with EAP-TLS, TTLS, or PEAP.
169 # http://www.dslreports.com/forum/remark,9286052~mode=flat
171 # Note that you should NOT use a globally known CA here!
172 # e.g. using a Verisign cert as a "known CA" means that
173 # ANYONE who has a certificate signed by them can
174 # authenticate via EAP-TLS! This is likely not what you want.
175 tls-config tls-common {
176 private_key_password = whatever
177 private_key_file = ${certdir}/server.pem
179 # If Private key & Certificate are located in
180 # the same file, then private_key_file &
181 # certificate_file must contain the same file
184 # If ca_file (below) is not used, then the
185 # certificate_file below MUST include not
186 # only the server certificate, but ALSO all
187 # of the CA certificates used to sign the
188 # server certificate.
189 certificate_file = ${certdir}/server.pem
191 # Trusted Root CA list
193 # ALL of the CA's in this list will be trusted
194 # to issue client certificates for authentication.
196 # In general, you should use self-signed
197 # certificates for 802.1x (EAP) authentication.
198 # In that case, this CA file should contain
199 # *one* CA certificate.
201 ca_file = ${cadir}/ca.pem
203 # OpenSSL will automatically create certificate chains,
204 # unless we tell it to not do that. The problem is that
205 # it sometimes gets the chains right from a certificate
206 # signature view, but wrong from the clients view.
208 # When setting "auto_chain = no", the server certificate
209 # file MUST include the full certificate chain.
213 # If OpenSSL supports TLS-PSK, then we can use
214 # a PSK identity and (hex) password. When the
215 # following two configuration items are specified,
216 # then certificate-based configuration items are
219 # private_key_password
225 # For now, the identity is fixed, and must be the
226 # same on the client. The passphrase must be a hex
227 # value, and can be up to 256 hex digits.
229 # Future versions of the server may be able to
230 # look up the shared key (hexphrase) based on the
233 # psk_identity = "test"
234 # psk_hexphrase = "036363823"
237 # For DH cipher suites to work, you have to
238 # run OpenSSL to create the DH file first:
240 # openssl dhparam -out certs/dh 2048
242 dh_file = ${certdir}/dh
245 # If your system doesn't have /dev/urandom,
246 # you will need to create this file, and
247 # periodically change its contents.
249 # For security reasons, FreeRADIUS doesn't
250 # write to files in its configuration
253 # random_file = /dev/urandom
256 # This can never exceed the size of a RADIUS
257 # packet (4096 bytes), and is preferably half
258 # that, to accommodate other attributes in
259 # RADIUS packet. On most APs the MAX packet
260 # length is configured between 1500 - 1600
261 # In these cases, fragment size should be
264 # fragment_size = 1024
266 # include_length is a flag which is
267 # by default set to yes If set to
268 # yes, Total Length of the message is
269 # included in EVERY packet we send.
270 # If set to no, Total Length of the
271 # message is included ONLY in the
272 # First packet of a fragment series.
274 # include_length = yes
277 # Check the Certificate Revocation List
279 # 1) Copy CA certificates and CRLs to same directory.
280 # 2) Execute 'c_rehash <CA certs&CRLs Directory>'.
281 # 'c_rehash' is OpenSSL's command.
282 # 3) uncomment the lines below.
286 # Check if intermediate CAs have been revoked.
287 # check_all_crl = yes
292 # If check_cert_issuer is set, the value will
293 # be checked against the DN of the issuer in
294 # the client certificate. If the values do not
295 # match, the certificate verification will fail,
296 # rejecting the user.
298 # In 2.1.10 and later, this check can be done
299 # more generally by checking the value of the
300 # TLS-Client-Cert-Issuer attribute. This check
301 # can be done via any mechanism you choose.
303 # check_cert_issuer = "/C=GB/ST=Berkshire/L=Newbury/O=My Company Ltd"
306 # If check_cert_cn is set, the value will
307 # be xlat'ed and checked against the CN
308 # in the client certificate. If the values
309 # do not match, the certificate verification
310 # will fail rejecting the user.
312 # This check is done only if the previous
313 # "check_cert_issuer" is not set, or if
314 # the check succeeds.
316 # In 2.1.10 and later, this check can be done
317 # more generally by checking the value of the
318 # TLS-Client-Cert-CN attribute. This check
319 # can be done via any mechanism you choose.
321 # check_cert_cn = %{User-Name}
323 # Set this option to specify the allowed
324 # TLS cipher suites. The format is listed
325 # in "man 1 ciphers".
326 cipher_list = "DEFAULT"
331 # Elliptical cryptography configuration
333 # Only for OpenSSL >= 0.9.8.f
335 ecdh_curve = "prime256v1"
338 # Session resumption / fast reauthentication
341 # The cache contains the following information:
343 # session Id - unique identifier, managed by SSL
344 # User-Name - from the Access-Accept
345 # Stripped-User-Name - from the Access-Request
346 # Cached-Session-Policy - from the Access-Accept
348 # The "Cached-Session-Policy" is the name of a
349 # policy which should be applied to the cached
350 # session. This policy can be used to assign
351 # VLANs, IP addresses, etc. It serves as a useful
352 # way to re-apply the policy from the original
353 # Access-Accept to the subsequent Access-Accept
354 # for the cached session.
356 # On session resumption, these attributes are
357 # copied from the cache, and placed into the
360 # You probably also want "use_tunneled_reply = yes"
361 # when using fast session resumption.
365 # Enable it. The default is "no". Deleting the entire "cache"
366 # subsection also disables caching.
368 # You can disallow resumption for a particular user by adding the
369 # following attribute to the control item list:
371 # Allow-Session-Resumption = No
373 # If "enable = no" below, you CANNOT enable resumption for just one
374 # user by setting the above attribute to "yes".
379 # Lifetime of the cached entries, in hours. The sessions will be
380 # deleted/invalidated after this time.
382 lifetime = 24 # hours
385 # The maximum number of entries in the
386 # cache. Set to "0" for "infinite".
388 # This could be set to the number of users
389 # who are logged in... which can be a LOT.
394 # Internal "name" of the session cache. Used to
395 # distinguish which TLS context sessions belong to.
397 # The server will generate a random value if unset.
398 # This will change across server restart so you MUST
399 # set the "name" if you want to persist sessions (see
405 # Simple directory-based storage of sessions.
406 # Two files per session will be written, the SSL
407 # state and the cached VPs. This will persist session
408 # across server restarts.
410 # The server will need write perms, and the directory
411 # should be secured from anyone else. You might want
412 # a script to remove old files from here periodically:
414 # find ${logdir}/tlscache -mtime +2 -exec rm -f {} \;
416 # This feature REQUIRES "name" option be set above.
418 #persist_dir = "${logdir}/tlscache"
422 # As of version 2.1.10, client certificates can be
423 # validated via an external command. This allows
424 # dynamic CRLs or OCSP to be used.
426 # This configuration is commented out in the
427 # default configuration. Uncomment it, and configure
428 # the correct paths below to enable it.
431 # A temporary directory where the client
432 # certificates are stored. This directory
433 # MUST be owned by the UID of the server,
434 # and MUST not be accessible by any other
435 # users. When the server starts, it will do
436 # "chmod go-rwx" on the directory, for
437 # security reasons. The directory MUST
438 # exist when the server starts.
440 # You should also delete all of the files
441 # in the directory when the server starts.
442 # tmpdir = /tmp/radiusd
444 # The command used to verify the client cert.
445 # We recommend using the OpenSSL command-line
448 # The ${..ca_path} text is a reference to
449 # the ca_path variable defined above.
451 # The %{TLS-Client-Cert-Filename} is the name
452 # of the temporary file containing the cert
453 # in PEM format. This file is automatically
454 # deleted by the server when the command
456 # client = "/path/to/openssl verify -CApath ${..ca_path} %{TLS-Client-Cert-Filename}"
461 # Certificates can be verified against an OCSP
462 # Responder. This makes it possible to immediately
463 # revoke certificates without the distribution of
464 # new Certificate Revocation Lists (CRLs).
468 # Enable it. The default is "no".
469 # Deleting the entire "ocsp" subsection
470 # also disables ocsp checking
475 # The OCSP Responder URL can be automatically
476 # extracted from the certificate in question.
477 # To override the OCSP Responder URL set
478 # "override_cert_url = yes".
480 override_cert_url = yes
483 # If the OCSP Responder address is not extracted from
484 # the certificate, the URL can be defined here.
486 url = "http://127.0.0.1/ocsp/"
489 # If the OCSP Responder can not cope with nonce
490 # in the request, then it can be disabled here.
492 # For security reasons, disabling this option
493 # is not recommended as nonce protects against
496 # Note that Microsoft AD Certificate Services OCSP
497 # Responder does not enable nonce by default. It is
498 # more secure to enable nonce on the responder than
499 # to disable it in the query here.
500 # See http://technet.microsoft.com/en-us/library/cc770413%28WS.10%29.aspx
505 # Number of seconds before giving up waiting
506 # for OCSP response. 0 uses system default.
511 # Normally an error in querying the OCSP
512 # responder (no response from server, server did
513 # not understand the request, etc) will result in
514 # a validation failure.
516 # To treat these errors as 'soft' failures and
517 # still accept the certificate, enable this
520 # Warning: this may enable clients with revoked
521 # certificates to connect if the OCSP responder
522 # is not available. Use with caution.
530 # As of Version 3.0, the TLS configuration for TLS-based
531 # EAP types is above in the "tls-config" section.
534 # Point to the common TLS configuration
538 # As part of checking a client certificate, the EAP-TLS
539 # sets some attributes such as TLS-Client-Cert-CN. This
540 # virtual server has access to these attributes, and can
541 # be used to accept or reject the request.
543 # virtual_server = check-eap-tls
549 # The TTLS module implements the EAP-TTLS protocol,
550 # which can be described as EAP inside of Diameter,
551 # inside of TLS, inside of EAP, inside of RADIUS...
553 # Surprisingly, it works quite well.
556 # Which tls-config section the TLS negotiation parameters
557 # are in - see EAP-TLS above for an explanation.
559 # In the case that an old configuration from FreeRADIUS
560 # v2.x is being used, all the options of the tls-config
561 # section may also appear instead in the 'tls' section
562 # above. If that is done, the tls= option here (and in
563 # tls above) MUST be commented out.
567 # The tunneled EAP session needs a default EAP type
568 # which is separate from the one for the non-tunneled
569 # EAP module. Inside of the TTLS tunnel, we recommend
570 # using EAP-MD5. If the request does not contain an
571 # EAP conversation, then this configuration entry is
574 default_eap_type = md5
576 # The tunneled authentication request does not usually
577 # contain useful attributes like 'Calling-Station-Id',
578 # etc. These attributes are outside of the tunnel,
579 # and normally unavailable to the tunneled
580 # authentication request.
582 # By setting this configuration entry to 'yes',
583 # any attribute which is NOT in the tunneled
584 # authentication request, but which IS available
585 # outside of the tunnel, is copied to the tunneled
588 # allowed values: {no, yes}
590 copy_request_to_tunnel = no
593 # As of version 3.0.5, this configuration item
594 # is deprecated. Instead, you should use
596 # update outer.session-state {
601 # This will cache attributes for the final Access-Accept.
603 # The reply attributes sent to the NAS are usually
604 # based on the name of the user 'outside' of the
605 # tunnel (usually 'anonymous'). If you want to send
606 # the reply attributes based on the user name inside
607 # of the tunnel, then set this configuration entry to
608 # 'yes', and the reply to the NAS will be taken from
609 # the reply to the tunneled request.
611 # allowed values: {no, yes}
613 use_tunneled_reply = no
616 # The inner tunneled request can be sent
617 # through a virtual server constructed
618 # specifically for this purpose.
620 # If this entry is commented out, the inner
621 # tunneled request will be sent through
622 # the virtual server that processed the
625 virtual_server = "inner-tunnel"
627 # This has the same meaning, and overwrites, the
628 # same field in the "tls" configuration, above.
629 # The default value here is "yes".
631 # include_length = yes
634 # Unlike EAP-TLS, EAP-TTLS does not require a client
635 # certificate. However, you can require one by setting the
636 # following option. You can also override this option by
639 # EAP-TLS-Require-Client-Cert = Yes
641 # in the control items for a request.
643 # require_client_cert = yes
650 ##################################################
652 # !!!!! WARNINGS for Windows compatibility !!!!!
654 ##################################################
656 # If you see the server send an Access-Challenge,
657 # and the client never sends another Access-Request,
662 # The server certificate has to have special OID's
663 # in it, or else the Microsoft clients will silently
664 # fail. See the "scripts/xpextensions" file for
665 # details, and the following page:
667 # http://support.microsoft.com/kb/814394/en-us
669 # For additional Windows XP SP2 issues, see:
671 # http://support.microsoft.com/kb/885453/en-us
674 # If is still doesn't work, and you're using Samba,
675 # you may be encountering a Samba bug. See:
677 # https://bugzilla.samba.org/show_bug.cgi?id=6563
679 # Note that we do not necessarily agree with their
680 # explanation... but the fix does appear to work.
682 ##################################################
685 # The tunneled EAP session needs a default EAP type
686 # which is separate from the one for the non-tunneled
687 # EAP module. Inside of the TLS/PEAP tunnel, we
688 # recommend using EAP-MS-CHAPv2.
691 # Which tls-config section the TLS negotiation parameters
692 # are in - see EAP-TLS above for an explanation.
694 # In the case that an old configuration from FreeRADIUS
695 # v2.x is being used, all the options of the tls-config
696 # section may also appear instead in the 'tls' section
697 # above. If that is done, the tls= option here (and in
698 # tls above) MUST be commented out.
702 # The tunneled EAP session needs a default
703 # EAP type which is separate from the one for
704 # the non-tunneled EAP module. Inside of the
705 # PEAP tunnel, we recommend using MS-CHAPv2,
706 # as that is the default type supported by
709 default_eap_type = mschapv2
711 # The PEAP module also has these configuration
712 # items, which are the same as for TTLS.
714 copy_request_to_tunnel = no
717 # As of version 3.0.5, this configuration item
718 # is deprecated. Instead, you should use
720 # update outer.session-state {
725 # This will cache attributes for the final Access-Accept.
727 use_tunneled_reply = no
729 # When the tunneled session is proxied, the
730 # home server may not understand EAP-MSCHAP-V2.
731 # Set this entry to "no" to proxy the tunneled
732 # EAP-MSCHAP-V2 as normal MSCHAPv2.
734 # proxy_tunneled_request_as_eap = yes
737 # The inner tunneled request can be sent
738 # through a virtual server constructed
739 # specifically for this purpose.
741 # If this entry is commented out, the inner
742 # tunneled request will be sent through
743 # the virtual server that processed the
746 virtual_server = "inner-tunnel"
748 # This option enables support for MS-SoH
749 # see doc/SoH.txt for more info.
750 # It is disabled by default.
755 # The SoH reply will be turned into a request which
756 # can be sent to a specific virtual server:
758 # soh_virtual_server = "soh-server"
761 # Unlike EAP-TLS, PEAP does not require a client certificate.
762 # However, you can require one by setting the following
763 # option. You can also override this option by setting
765 # EAP-TLS-Require-Client-Cert = Yes
767 # in the control items for a request.
769 # require_client_cert = yes
773 # This takes no configuration.
775 # Note that it is the EAP MS-CHAPv2 sub-module, not
776 # the main 'mschap' module.
778 # Note also that in order for this sub-module to work,
779 # the main 'mschap' module MUST ALSO be configured.
781 # This module is the *Microsoft* implementation of MS-CHAPv2
782 # in EAP. There is another (incompatible) implementation
783 # of MS-CHAPv2 in EAP by Cisco, which FreeRADIUS does not
787 # Prior to version 2.1.11, the module never
788 # sent the MS-CHAP-Error message to the
789 # client. This worked, but it had issues
790 # when the cached password was wrong. The
791 # server *should* send "E=691 R=0" to the
792 # client, which tells it to prompt the user
793 # for a new password.
795 # The default is to behave as in 2.1.10 and
796 # earlier, which is known to work. If you
797 # set "send_error = yes", then the error
798 # message will be sent back to the client.
799 # This *may* help some clients work better,
800 # but *may* also cause other clients to stop
805 # Server identifier to send back in the challenge.
806 # This should generally be the host name of the
807 # RADIUS server. Or, some information to uniquely
809 # identity = "FreeRADIUS"