2 # Whatever you do, do NOT set 'Auth-Type := EAP'. The server
3 # is smart enough to figure this out on its own. The most
4 # common side effect of setting 'Auth-Type := EAP' is that the
5 # users then cannot use ANY other authentication method.
10 # Invoke the default supported EAP type when
11 # EAP-Identity response is received.
13 # The incoming EAP messages DO NOT specify which EAP
14 # type they will be using, so it MUST be set here.
16 # For now, only one default EAP type may be used at a time.
18 # If the EAP-Type attribute is set by another module,
19 # then that EAP type takes precedence over the
20 # default type configured here.
22 default_eap_type = md5
24 # A list is maintained to correlate EAP-Response
25 # packets with EAP-Request packets. After a
26 # configurable length of time, entries in the list
27 # expire, and are deleted.
31 # There are many EAP types, but the server has support
32 # for only a limited subset. If the server receives
33 # a request for an EAP type it does not support, then
34 # it normally rejects the request. By setting this
35 # configuration to "yes", you can tell the server to
36 # instead keep processing the request. Another module
37 # MUST then be configured to proxy the request to
38 # another RADIUS server which supports that EAP type.
40 # If another module is NOT configured to handle the
41 # request, then the request will still end up being
43 ignore_unknown_eap_types = no
45 # Cisco AP1230B firmware 12.2(13)JA1 has a bug. When given
46 # a User-Name attribute in an Access-Accept, it copies one
47 # more byte than it should.
49 # We can work around it by configurably adding an extra
51 cisco_accounting_username_bug = no
56 # We do NOT recommend using EAP-MD5 authentication
57 # for wireless connections. It is insecure, and does
58 # not provide for dynamic WEP keys.
65 # We do not recommend using LEAP in new deployments. See:
66 # http://www.securiteam.com/tools/5TP012ACKE.html
68 # Cisco LEAP uses the MS-CHAP algorithm (but not
69 # the MS-CHAP attributes) to perform it's authentication.
71 # As a result, LEAP *requires* access to the plain-text
72 # User-Password, or the NT-Password attributes.
73 # 'System' authentication is impossible with LEAP.
80 # Currently, this is only permitted inside of EAP-TTLS,
81 # or EAP-PEAP. The module "challenges" the user with
82 # text, and the response from the user is taken to be
85 # Proxying the tunneled EAP-GTC session is a bad idea,
86 # the users password will go over the wire in plain-text,
90 # The default challenge, which many clients
92 #challenge = "Password: "
94 # The plain-text response which comes back
95 # is put into a User-Password attribute,
96 # and passed to another module for
97 # authentication. This allows the EAP-GTC
98 # response to be checked against plain-text,
99 # or crypt'd passwords.
101 # If you say "Local" instead of "PAP", then
102 # the module will look for a User-Password
103 # configured for the request, and do the
104 # authentication itself.
111 # To generate ctest certificates, run the script
113 # ../scripts/certs.sh
115 # The documents on http://www.freeradius.org/doc
116 # are old, but may be helpful.
120 # http://www.dslreports.com/forum/remark,9286052~mode=flat
123 # private_key_password = whatever
124 # private_key_file = ${raddbdir}/certs/cert-srv.pem
126 # If Private key & Certificate are located in
127 # the same file, then private_key_file &
128 # certificate_file must contain the same file
130 # certificate_file = ${raddbdir}/certs/cert-srv.pem
132 # Trusted Root CA list
133 # CA_file = ${raddbdir}/certs/demoCA/cacert.pem
135 # dh_file = ${raddbdir}/certs/dh
136 # random_file = ${raddbdir}/certs/random
139 # This can never exceed the size of a RADIUS
140 # packet (4096 bytes), and is preferably half
141 # that, to accomodate other attributes in
142 # RADIUS packet. On most APs the MAX packet
143 # length is configured between 1500 - 1600
144 # In these cases, fragment size should be
147 # fragment_size = 1024
149 # include_length is a flag which is
150 # by default set to yes If set to
151 # yes, Total Length of the message is
152 # included in EVERY packet we send.
153 # If set to no, Total Length of the
154 # message is included ONLY in the
155 # First packet of a fragment series.
157 # include_length = yes
159 # Check the Certificate Revocation List
161 # 1) Copy CA certificates and CRLs to same directory.
162 # 2) Execute 'c_rehash <CA certs&CRLs Directory>'.
163 # 'c_rehash' is OpenSSL's command.
164 # 3) Add 'CA_path=<CA certs&CRLs directory>'
165 # to radiusd.conf's tls section.
166 # 4) uncomment the line below.
171 # If check_cert_cn is set, the value will
172 # be xlat'ed and checked against the CN
173 # in the client certificate. If the values
174 # do not match, the certificate verification
175 # will fail rejecting the user.
177 # check_cert_cn = %{User-Name}
180 # The TTLS module implements the EAP-TTLS protocol,
181 # which can be described as EAP inside of Diameter,
182 # inside of TLS, inside of EAP, inside of RADIUS...
184 # Surprisingly, it works quite well.
186 # The TTLS module needs the TLS module to be installed
187 # and configured, in order to use the TLS tunnel
188 # inside of the EAP packet. You will still need to
189 # configure the TLS module, even if you do not want
190 # to deploy EAP-TLS in your network. Users will not
191 # be able to request EAP-TLS, as it requires them to
192 # have a client certificate. EAP-TTLS does not
193 # require a client certificate.
196 # The tunneled EAP session needs a default
197 # EAP type which is separate from the one for
198 # the non-tunneled EAP module. Inside of the
199 # TTLS tunnel, we recommend using EAP-MD5.
200 # If the request does not contain an EAP
201 # conversation, then this configuration entry
203 # default_eap_type = md5
205 # The tunneled authentication request does
206 # not usually contain useful attributes
207 # like 'Calling-Station-Id', etc. These
208 # attributes are outside of the tunnel,
209 # and normally unavailable to the tunneled
210 # authentication request.
212 # By setting this configuration entry to
213 # 'yes', any attribute which NOT in the
214 # tunneled authentication request, but
215 # which IS available outside of the tunnel,
216 # is copied to the tunneled request.
218 # allowed values: {no, yes}
219 # copy_request_to_tunnel = no
221 # The reply attributes sent to the NAS are
222 # usually based on the name of the user
223 # 'outside' of the tunnel (usually
224 # 'anonymous'). If you want to send the
225 # reply attributes based on the user name
226 # inside of the tunnel, then set this
227 # configuration entry to 'yes', and the reply
228 # to the NAS will be taken from the reply to
229 # the tunneled request.
231 # allowed values: {no, yes}
232 # use_tunneled_reply = no
237 # The tunneled EAP session needs a default EAP type
238 # which is separate from the one for the non-tunneled
239 # EAP module. Inside of the TLS/PEAP tunnel, we
240 # recommend using EAP-MS-CHAPv2.
242 # The PEAP module needs the TLS module to be installed
243 # and configured, in order to use the TLS tunnel
244 # inside of the EAP packet. You will still need to
245 # configure the TLS module, even if you do not want
246 # to deploy EAP-TLS in your network. Users will not
247 # be able to request EAP-TLS, as it requires them to
248 # have a client certificate. EAP-PEAP does not
249 # require a client certificate.
252 # The tunneled EAP session needs a default
253 # EAP type which is separate from the one for
254 # the non-tunneled EAP module. Inside of the
255 # PEAP tunnel, we recommend using MS-CHAPv2,
256 # as that is the default type supported by
258 # default_eap_type = mschapv2
262 # This takes no configuration.
264 # Note that it is the EAP MS-CHAPv2 sub-module, not
265 # the main 'mschap' module.
267 # Note also that in order for this sub-module to work,
268 # the main 'mschap' module MUST ALSO be configured.
270 # This module is the *Microsoft* implementation of MS-CHAPv2
271 # in EAP. There is another (incompatible) implementation
272 # of MS-CHAPv2 in EAP by Cisco, which FreeRADIUS does not