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
64 # We do NOT recommend using EAP-MD5 authentication
65 # for wireless connections. It is insecure, and does
66 # not provide for dynamic WEP keys.
73 # We do not recommend using LEAP in new deployments. See:
74 # http://www.securiteam.com/tools/5TP012ACKE.html
76 # Cisco LEAP uses the MS-CHAP algorithm (but not
77 # the MS-CHAP attributes) to perform it's authentication.
79 # As a result, LEAP *requires* access to the plain-text
80 # User-Password, or the NT-Password attributes.
81 # 'System' authentication is impossible with LEAP.
88 # Currently, this is only permitted inside of EAP-TTLS,
89 # or EAP-PEAP. The module "challenges" the user with
90 # text, and the response from the user is taken to be
93 # Proxying the tunneled EAP-GTC session is a bad idea,
94 # the users password will go over the wire in plain-text,
98 # The default challenge, which many clients
100 #challenge = "Password: "
102 # The plain-text response which comes back
103 # is put into a User-Password attribute,
104 # and passed to another module for
105 # authentication. This allows the EAP-GTC
106 # response to be checked against plain-text,
107 # or crypt'd passwords.
109 # If you say "Local" instead of "PAP", then
110 # the module will look for a User-Password
111 # configured for the request, and do the
112 # authentication itself.
119 # If OpenSSL was not found at the time the server was
120 # built, the "tls", "ttls", and "peap" sections will
123 # Otherwise, when the server first starts in debugging
124 # mode, test certificates will be created. See the
125 # "make_cert_command" below for details, and the README
126 # file in raddb/certs
128 # These test certificates SHOULD NOT be used in a normal
129 # deployment. They are created only to make it easier
130 # to install the server, and to perform some simple
131 # tests with EAP-TLS, TTLS, or PEAP.
135 # http://www.dslreports.com/forum/remark,9286052~mode=flat
139 # These is used to simplify later configurations.
141 certdir = ${confdir}/certs
142 cadir = ${confdir}/certs
144 private_key_password = whatever
145 private_key_file = ${certdir}/server.pem
147 # If Private key & Certificate are located in
148 # the same file, then private_key_file &
149 # certificate_file must contain the same file
151 certificate_file = ${certdir}/server.pem
153 # Trusted Root CA list
155 # ALL of the CA's in this list will be trusted
156 # to issue client certificates for authentication.
158 # In general, you should use self-signed
159 # certificates for 802.1x (EAP) authentication.
160 # In that case, this CA file should contain
161 # *one* CA certificate.
162 CA_file = ${cadir}/ca.pem
165 # For DH cipher suites to work, you have to
166 # run OpenSSL to create the DH file first:
168 # openssl dhparam -out certs/dh 1024
170 dh_file = ${certdir}/dh
171 random_file = ${certdir}/random
174 # This can never exceed the size of a RADIUS
175 # packet (4096 bytes), and is preferably half
176 # that, to accomodate other attributes in
177 # RADIUS packet. On most APs the MAX packet
178 # length is configured between 1500 - 1600
179 # In these cases, fragment size should be
182 # fragment_size = 1024
184 # include_length is a flag which is
185 # by default set to yes If set to
186 # yes, Total Length of the message is
187 # included in EVERY packet we send.
188 # If set to no, Total Length of the
189 # message is included ONLY in the
190 # First packet of a fragment series.
192 # include_length = yes
194 # Check the Certificate Revocation List
196 # 1) Copy CA certificates and CRLs to same directory.
197 # 2) Execute 'c_rehash <CA certs&CRLs Directory>'.
198 # 'c_rehash' is OpenSSL's command.
199 # 3) uncomment the line below.
202 # CA_path = /path/to/directory/with/ca_certs/and/crls/
205 # If check_cert_issuer is set, the value will
206 # be checked against the DN of the issuer in
207 # the client certificate. If the values do not
208 # match, the cerficate verification will fail,
209 # rejecting the user.
211 # check_cert_issuer = "/C=GB/ST=Berkshire/L=Newbury/O=My Company Ltd"
214 # If check_cert_cn is set, the value will
215 # be xlat'ed and checked against the CN
216 # in the client certificate. If the values
217 # do not match, the certificate verification
218 # will fail rejecting the user.
220 # This check is done only if the previous
221 # "check_cert_issuer" is not set, or if
222 # the check succeeds.
224 # check_cert_cn = %{User-Name}
226 # Set this option to specify the allowed
227 # TLS cipher suites. The format is listed
228 # in "man 1 ciphers".
229 cipher_list = "DEFAULT"
233 # This configuration entry should be deleted
234 # once the server is running in a normal
235 # configuration. It is here ONLY to make
236 # initial deployments easier.
238 make_cert_command = "${certdir}/bootstrap"
241 # The TTLS module implements the EAP-TTLS protocol,
242 # which can be described as EAP inside of Diameter,
243 # inside of TLS, inside of EAP, inside of RADIUS...
245 # Surprisingly, it works quite well.
247 # The TTLS module needs the TLS module to be installed
248 # and configured, in order to use the TLS tunnel
249 # inside of the EAP packet. You will still need to
250 # configure the TLS module, even if you do not want
251 # to deploy EAP-TLS in your network. Users will not
252 # be able to request EAP-TLS, as it requires them to
253 # have a client certificate. EAP-TTLS does not
254 # require a client certificate.
256 # You can make TTLS require a client cert by setting
258 # EAP-TLS-Require-Client-Cert = Yes
260 # in the control items for a request.
263 # The tunneled EAP session needs a default
264 # EAP type which is separate from the one for
265 # the non-tunneled EAP module. Inside of the
266 # TTLS tunnel, we recommend using EAP-MD5.
267 # If the request does not contain an EAP
268 # conversation, then this configuration entry
270 default_eap_type = md5
272 # The tunneled authentication request does
273 # not usually contain useful attributes
274 # like 'Calling-Station-Id', etc. These
275 # attributes are outside of the tunnel,
276 # and normally unavailable to the tunneled
277 # authentication request.
279 # By setting this configuration entry to
280 # 'yes', any attribute which NOT in the
281 # tunneled authentication request, but
282 # which IS available outside of the tunnel,
283 # is copied to the tunneled request.
285 # allowed values: {no, yes}
286 copy_request_to_tunnel = no
288 # The reply attributes sent to the NAS are
289 # usually based on the name of the user
290 # 'outside' of the tunnel (usually
291 # 'anonymous'). If you want to send the
292 # reply attributes based on the user name
293 # inside of the tunnel, then set this
294 # configuration entry to 'yes', and the reply
295 # to the NAS will be taken from the reply to
296 # the tunneled request.
298 # allowed values: {no, yes}
299 use_tunneled_reply = no
302 # The inner tunneled request can be sent
303 # through a virtual server constructed
304 # specifically for this purpose.
306 # If this entry is commented out, the inner
307 # tunneled request will be sent through
308 # the virtual server that processed the
311 #virtual_server = "inner-tunnel"
314 ##################################################
316 # !!!!! WARNINGS for Windows compatibility !!!!!
318 ##################################################
320 # If you see the server send an Access-Challenge,
321 # and the client never sends another Access-Request,
326 # The server certificate has to have special OID's
327 # in it, or else the Microsoft clients will silently
328 # fail. See the "scripts/xpextensions" file for
329 # details, and the following page:
331 # http://support.microsoft.com/kb/814394/en-us
333 # For additional Windows XP SP2 issues, see:
335 # http://support.microsoft.com/kb/885453/en-us
337 # Note that we do not necessarily agree with their
338 # explanation... but the fix does appear to work.
340 ##################################################
343 # The tunneled EAP session needs a default EAP type
344 # which is separate from the one for the non-tunneled
345 # EAP module. Inside of the TLS/PEAP tunnel, we
346 # recommend using EAP-MS-CHAPv2.
348 # The PEAP module needs the TLS module to be installed
349 # and configured, in order to use the TLS tunnel
350 # inside of the EAP packet. You will still need to
351 # configure the TLS module, even if you do not want
352 # to deploy EAP-TLS in your network. Users will not
353 # be able to request EAP-TLS, as it requires them to
354 # have a client certificate. EAP-PEAP does not
355 # require a client certificate.
358 # You can make TTLS require a client cert by setting
360 # EAP-TLS-Require-Client-Cert = Yes
362 # in the control items for a request.
365 # The tunneled EAP session needs a default
366 # EAP type which is separate from the one for
367 # the non-tunneled EAP module. Inside of the
368 # PEAP tunnel, we recommend using MS-CHAPv2,
369 # as that is the default type supported by
371 default_eap_type = mschapv2
373 # the PEAP module also has these configuration
374 # items, which are the same as for TTLS.
375 copy_request_to_tunnel = no
376 use_tunneled_reply = no
378 # When the tunneled session is proxied, the
379 # home server may not understand EAP-MSCHAP-V2.
380 # Set this entry to "no" to proxy the tunneled
381 # EAP-MSCHAP-V2 as normal MSCHAPv2.
382 # proxy_tunneled_request_as_eap = yes
385 # The inner tunneled request can be sent
386 # through a virtual server constructed
387 # specifically for this purpose.
389 # If this entry is commented out, the inner
390 # tunneled request will be sent through
391 # the virtual server that processed the
394 #virtual_server = "inner-tunnel"
398 # This takes no configuration.
400 # Note that it is the EAP MS-CHAPv2 sub-module, not
401 # the main 'mschap' module.
403 # Note also that in order for this sub-module to work,
404 # the main 'mschap' module MUST ALSO be configured.
406 # This module is the *Microsoft* implementation of MS-CHAPv2
407 # in EAP. There is another (incompatible) implementation
408 # of MS-CHAPv2 in EAP by Cisco, which FreeRADIUS does not