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
154 CA_file = ${cadir}/ca.pem
157 # For DH cipher suites to work, you have to
158 # run OpenSSL to create the DH file first:
160 # openssl dhparam -out certs/dh 1024
162 dh_file = ${certdir}/dh
163 random_file = ${certdir}/random
166 # This can never exceed the size of a RADIUS
167 # packet (4096 bytes), and is preferably half
168 # that, to accomodate other attributes in
169 # RADIUS packet. On most APs the MAX packet
170 # length is configured between 1500 - 1600
171 # In these cases, fragment size should be
174 # fragment_size = 1024
176 # include_length is a flag which is
177 # by default set to yes If set to
178 # yes, Total Length of the message is
179 # included in EVERY packet we send.
180 # If set to no, Total Length of the
181 # message is included ONLY in the
182 # First packet of a fragment series.
184 # include_length = yes
186 # Check the Certificate Revocation List
188 # 1) Copy CA certificates and CRLs to same directory.
189 # 2) Execute 'c_rehash <CA certs&CRLs Directory>'.
190 # 'c_rehash' is OpenSSL's command.
191 # 3) uncomment the line below.
194 # CA_path = /path/to/directory/with/ca_certs/and/crls/
197 # If check_cert_issuer is set, the value will
198 # be checked against the DN of the issuer in
199 # the client certificate. If the values do not
200 # match, the cerficate verification will fail,
201 # rejecting the user.
203 # check_cert_issuer = "/C=GB/ST=Berkshire/L=Newbury/O=My Company Ltd"
206 # If check_cert_cn is set, the value will
207 # be xlat'ed and checked against the CN
208 # in the client certificate. If the values
209 # do not match, the certificate verification
210 # will fail rejecting the user.
212 # This check is done only if the previous
213 # "check_cert_issuer" is not set, or if
214 # the check succeeds.
216 # check_cert_cn = %{User-Name}
218 # Set this option to specify the allowed
219 # TLS cipher suites. The format is listed
220 # in "man 1 ciphers".
221 cipher_list = "DEFAULT"
225 # This configuration entry should be deleted
226 # once the server is running in a normal
227 # configuration. It is here ONLY to make
228 # initial deployments easier.
230 make_cert_command = "${certdir}/bootstrap"
233 # The TTLS module implements the EAP-TTLS protocol,
234 # which can be described as EAP inside of Diameter,
235 # inside of TLS, inside of EAP, inside of RADIUS...
237 # Surprisingly, it works quite well.
239 # The TTLS module needs the TLS module to be installed
240 # and configured, in order to use the TLS tunnel
241 # inside of the EAP packet. You will still need to
242 # configure the TLS module, even if you do not want
243 # to deploy EAP-TLS in your network. Users will not
244 # be able to request EAP-TLS, as it requires them to
245 # have a client certificate. EAP-TTLS does not
246 # require a client certificate.
248 # You can make TTLS require a client cert by setting
250 # EAP-TLS-Require-Client-Cert = Yes
252 # in the control items for a request.
255 # The tunneled EAP session needs a default
256 # EAP type which is separate from the one for
257 # the non-tunneled EAP module. Inside of the
258 # TTLS tunnel, we recommend using EAP-MD5.
259 # If the request does not contain an EAP
260 # conversation, then this configuration entry
262 default_eap_type = md5
264 # The tunneled authentication request does
265 # not usually contain useful attributes
266 # like 'Calling-Station-Id', etc. These
267 # attributes are outside of the tunnel,
268 # and normally unavailable to the tunneled
269 # authentication request.
271 # By setting this configuration entry to
272 # 'yes', any attribute which NOT in the
273 # tunneled authentication request, but
274 # which IS available outside of the tunnel,
275 # is copied to the tunneled request.
277 # allowed values: {no, yes}
278 copy_request_to_tunnel = no
280 # The reply attributes sent to the NAS are
281 # usually based on the name of the user
282 # 'outside' of the tunnel (usually
283 # 'anonymous'). If you want to send the
284 # reply attributes based on the user name
285 # inside of the tunnel, then set this
286 # configuration entry to 'yes', and the reply
287 # to the NAS will be taken from the reply to
288 # the tunneled request.
290 # allowed values: {no, yes}
291 use_tunneled_reply = no
294 # The inner tunneled request can be sent
295 # through a virtual server constructed
296 # specifically for this purpose.
298 # If this entry is commented out, the inner
299 # tunneled request will be sent through
300 # the virtual server that processed the
303 #virtual_server = "inner-tunnel"
306 ##################################################
308 # !!!!! WARNINGS for Windows compatibility !!!!!
310 ##################################################
312 # If you see the server send an Access-Challenge,
313 # and the client never sends another Access-Request,
318 # The server certificate has to have special OID's
319 # in it, or else the Microsoft clients will silently
320 # fail. See the "scripts/xpextensions" file for
321 # details, and the following page:
323 # http://support.microsoft.com/kb/814394/en-us
325 # For additional Windows XP SP2 issues, see:
327 # http://support.microsoft.com/kb/885453/en-us
329 # Note that we do not necessarily agree with their
330 # explanation... but the fix does appear to work.
332 ##################################################
335 # The tunneled EAP session needs a default EAP type
336 # which is separate from the one for the non-tunneled
337 # EAP module. Inside of the TLS/PEAP tunnel, we
338 # recommend using EAP-MS-CHAPv2.
340 # The PEAP module needs the TLS module to be installed
341 # and configured, in order to use the TLS tunnel
342 # inside of the EAP packet. You will still need to
343 # configure the TLS module, even if you do not want
344 # to deploy EAP-TLS in your network. Users will not
345 # be able to request EAP-TLS, as it requires them to
346 # have a client certificate. EAP-PEAP does not
347 # require a client certificate.
350 # You can make TTLS require a client cert by setting
352 # EAP-TLS-Require-Client-Cert = Yes
354 # in the control items for a request.
357 # The tunneled EAP session needs a default
358 # EAP type which is separate from the one for
359 # the non-tunneled EAP module. Inside of the
360 # PEAP tunnel, we recommend using MS-CHAPv2,
361 # as that is the default type supported by
363 default_eap_type = mschapv2
365 # the PEAP module also has these configuration
366 # items, which are the same as for TTLS.
367 copy_request_to_tunnel = no
368 use_tunneled_reply = no
370 # When the tunneled session is proxied, the
371 # home server may not understand EAP-MSCHAP-V2.
372 # Set this entry to "no" to proxy the tunneled
373 # EAP-MSCHAP-V2 as normal MSCHAPv2.
374 # proxy_tunneled_request_as_eap = yes
377 # The inner tunneled request can be sent
378 # through a virtual server constructed
379 # specifically for this purpose.
381 # If this entry is commented out, the inner
382 # tunneled request will be sent through
383 # the virtual server that processed the
386 #virtual_server = "inner-tunnel"
390 # This takes no configuration.
392 # Note that it is the EAP MS-CHAPv2 sub-module, not
393 # the main 'mschap' module.
395 # Note also that in order for this sub-module to work,
396 # the main 'mschap' module MUST ALSO be configured.
398 # This module is the *Microsoft* implementation of MS-CHAPv2
399 # in EAP. There is another (incompatible) implementation
400 # of MS-CHAPv2 in EAP by Cisco, which FreeRADIUS does not