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.
171 certificate_file = ${certdir}/server.pem
173 # Trusted Root CA list
175 # ALL of the CA's in this list will be trusted
176 # to issue client certificates for authentication.
178 # In general, you should use self-signed
179 # certificates for 802.1x (EAP) authentication.
180 # In that case, this CA file should contain
181 # *one* CA certificate.
183 # This parameter is used only for EAP-TLS,
184 # when you issue client certificates. If you do
185 # not use client certificates, and you do not want
186 # to permit EAP-TLS authentication, then delete
187 # this configuration item.
188 CA_file = ${cadir}/ca.pem
191 # For DH cipher suites to work, you have to
192 # run OpenSSL to create the DH file first:
194 # openssl dhparam -out certs/dh 1024
196 dh_file = ${certdir}/dh
197 random_file = ${certdir}/random
200 # This can never exceed the size of a RADIUS
201 # packet (4096 bytes), and is preferably half
202 # that, to accomodate other attributes in
203 # RADIUS packet. On most APs the MAX packet
204 # length is configured between 1500 - 1600
205 # In these cases, fragment size should be
208 # fragment_size = 1024
210 # include_length is a flag which is
211 # by default set to yes If set to
212 # yes, Total Length of the message is
213 # included in EVERY packet we send.
214 # If set to no, Total Length of the
215 # message is included ONLY in the
216 # First packet of a fragment series.
218 # include_length = yes
220 # Check the Certificate Revocation List
222 # 1) Copy CA certificates and CRLs to same directory.
223 # 2) Execute 'c_rehash <CA certs&CRLs Directory>'.
224 # 'c_rehash' is OpenSSL's command.
225 # 3) uncomment the line below.
228 # CA_path = /path/to/directory/with/ca_certs/and/crls/
231 # If check_cert_issuer is set, the value will
232 # be checked against the DN of the issuer in
233 # the client certificate. If the values do not
234 # match, the cerficate verification will fail,
235 # rejecting the user.
237 # check_cert_issuer = "/C=GB/ST=Berkshire/L=Newbury/O=My Company Ltd"
240 # If check_cert_cn is set, the value will
241 # be xlat'ed and checked against the CN
242 # in the client certificate. If the values
243 # do not match, the certificate verification
244 # will fail rejecting the user.
246 # This check is done only if the previous
247 # "check_cert_issuer" is not set, or if
248 # the check succeeds.
250 # check_cert_cn = %{User-Name}
252 # Set this option to specify the allowed
253 # TLS cipher suites. The format is listed
254 # in "man 1 ciphers".
255 cipher_list = "DEFAULT"
259 # This configuration entry should be deleted
260 # once the server is running in a normal
261 # configuration. It is here ONLY to make
262 # initial deployments easier.
264 make_cert_command = "${certdir}/bootstrap"
267 # Session resumption / fast reauthentication
270 # The cache contains the following information:
272 # session Id - unique identifier, managed by SSL
273 # User-Name - from the Access-Accept
274 # Stripped-User-Name - from the Access-Request
275 # Cached-Session-Policy - from the Access-Accept
277 # The "Cached-Session-Policy" is the name of a
278 # policy which should be applied to the cached
279 # session. This policy can be used to assign
280 # VLANs, IP addresses, etc. It serves as a useful
281 # way to re-apply the policy from the original
282 # Access-Accept to the subsequent Access-Accept
283 # for the cached session.
285 # On session resumption, these attributes are
286 # copied from the cache, and placed into the
291 # Enable it. The default is "no".
292 # Deleting the entire "cache" subsection
293 # Also disables caching.
295 # You can disallow resumption for a
296 # particular user by adding the following
297 # attribute to the control item list:
299 # Allow-Session-Resumption = No
301 # If "enable = no" below, you CANNOT
302 # enable resumption for just one user
303 # by setting the above attribute to "yes".
308 # Lifetime of the cached entries, in hours.
309 # The sessions will be deleted after this
312 lifetime = 24 # hours
315 # The maximum number of entries in the
316 # cache. Set to "0" for "infinite".
318 # This could be set to the number of users
319 # who are logged in... which can be a LOT.
325 # The TTLS module implements the EAP-TTLS protocol,
326 # which can be described as EAP inside of Diameter,
327 # inside of TLS, inside of EAP, inside of RADIUS...
329 # Surprisingly, it works quite well.
331 # The TTLS module needs the TLS module to be installed
332 # and configured, in order to use the TLS tunnel
333 # inside of the EAP packet. You will still need to
334 # configure the TLS module, even if you do not want
335 # to deploy EAP-TLS in your network. Users will not
336 # be able to request EAP-TLS, as it requires them to
337 # have a client certificate. EAP-TTLS does not
338 # require a client certificate.
340 # You can make TTLS require a client cert by setting
342 # EAP-TLS-Require-Client-Cert = Yes
344 # in the control items for a request.
347 # The tunneled EAP session needs a default
348 # EAP type which is separate from the one for
349 # the non-tunneled EAP module. Inside of the
350 # TTLS tunnel, we recommend using EAP-MD5.
351 # If the request does not contain an EAP
352 # conversation, then this configuration entry
354 default_eap_type = md5
356 # The tunneled authentication request does
357 # not usually contain useful attributes
358 # like 'Calling-Station-Id', etc. These
359 # attributes are outside of the tunnel,
360 # and normally unavailable to the tunneled
361 # authentication request.
363 # By setting this configuration entry to
364 # 'yes', any attribute which NOT in the
365 # tunneled authentication request, but
366 # which IS available outside of the tunnel,
367 # is copied to the tunneled request.
369 # allowed values: {no, yes}
370 copy_request_to_tunnel = no
372 # The reply attributes sent to the NAS are
373 # usually based on the name of the user
374 # 'outside' of the tunnel (usually
375 # 'anonymous'). If you want to send the
376 # reply attributes based on the user name
377 # inside of the tunnel, then set this
378 # configuration entry to 'yes', and the reply
379 # to the NAS will be taken from the reply to
380 # the tunneled request.
382 # allowed values: {no, yes}
383 use_tunneled_reply = no
386 # The inner tunneled request can be sent
387 # through a virtual server constructed
388 # specifically for this purpose.
390 # If this entry is commented out, the inner
391 # tunneled request will be sent through
392 # the virtual server that processed the
395 virtual_server = "inner-tunnel"
397 # This has the same meaning as the
398 # same field in the "tls" module, above.
399 # The default value here is "yes".
400 # include_length = yes
403 ##################################################
405 # !!!!! WARNINGS for Windows compatibility !!!!!
407 ##################################################
409 # If you see the server send an Access-Challenge,
410 # and the client never sends another Access-Request,
415 # The server certificate has to have special OID's
416 # in it, or else the Microsoft clients will silently
417 # fail. See the "scripts/xpextensions" file for
418 # details, and the following page:
420 # http://support.microsoft.com/kb/814394/en-us
422 # For additional Windows XP SP2 issues, see:
424 # http://support.microsoft.com/kb/885453/en-us
427 # If is still doesn't work, and you're using Samba,
428 # you may be encountering a Samba bug. See:
430 # https://bugzilla.samba.org/show_bug.cgi?id=6563
432 # Note that we do not necessarily agree with their
433 # explanation... but the fix does appear to work.
435 ##################################################
438 # The tunneled EAP session needs a default EAP type
439 # which is separate from the one for the non-tunneled
440 # EAP module. Inside of the TLS/PEAP tunnel, we
441 # recommend using EAP-MS-CHAPv2.
443 # The PEAP module needs the TLS module to be installed
444 # and configured, in order to use the TLS tunnel
445 # inside of the EAP packet. You will still need to
446 # configure the TLS module, even if you do not want
447 # to deploy EAP-TLS in your network. Users will not
448 # be able to request EAP-TLS, as it requires them to
449 # have a client certificate. EAP-PEAP does not
450 # require a client certificate.
453 # You can make PEAP require a client cert by setting
455 # EAP-TLS-Require-Client-Cert = Yes
457 # in the control items for a request.
460 # The tunneled EAP session needs a default
461 # EAP type which is separate from the one for
462 # the non-tunneled EAP module. Inside of the
463 # PEAP tunnel, we recommend using MS-CHAPv2,
464 # as that is the default type supported by
466 default_eap_type = mschapv2
468 # the PEAP module also has these configuration
469 # items, which are the same as for TTLS.
470 copy_request_to_tunnel = no
471 use_tunneled_reply = no
473 # When the tunneled session is proxied, the
474 # home server may not understand EAP-MSCHAP-V2.
475 # Set this entry to "no" to proxy the tunneled
476 # EAP-MSCHAP-V2 as normal MSCHAPv2.
477 # proxy_tunneled_request_as_eap = yes
480 # The inner tunneled request can be sent
481 # through a virtual server constructed
482 # specifically for this purpose.
484 # If this entry is commented out, the inner
485 # tunneled request will be sent through
486 # the virtual server that processed the
489 virtual_server = "inner-tunnel"
493 # This takes no configuration.
495 # Note that it is the EAP MS-CHAPv2 sub-module, not
496 # the main 'mschap' module.
498 # Note also that in order for this sub-module to work,
499 # the main 'mschap' module MUST ALSO be configured.
501 # This module is the *Microsoft* implementation of MS-CHAPv2
502 # in EAP. There is another (incompatible) implementation
503 # of MS-CHAPv2 in EAP by Cisco, which FreeRADIUS does not