2 ######################################################################
4 # This is a virtual server that handles *only* inner tunnel
5 # requests for EAP-TTLS and PEAP types.
9 ######################################################################
14 # This next section is here to allow testing of the "inner-tunnel"
15 # authentication methods, independently from the "default" server.
16 # It is listening on "localhost", so that it can only be used from
19 # $ radtest USER PASSWORD 127.0.0.1:18120 0 testing123
21 # If it works, you have configured the inner tunnel correctly. To check
22 # if PEAP will work, use:
24 # $ radtest -t mschap USER PASSWORD 127.0.0.1:18120 0 testing123
26 # If that works, PEAP should work. If that command doesn't work, then
28 # FIX THE INNER TUNNEL CONFIGURATION SO THAT IT WORKS.
30 # Do NOT do any PEAP tests. It won't help. Instead, concentrate
31 # on fixing the inner tunnel configuration. DO NOTHING ELSE.
40 # Authorization. First preprocess (hints and huntgroups files),
41 # then realms, and finally look in the "users" file.
43 # The order of the realm modules will determine the order that
44 # we try to find a matching realm.
46 # Make *sure* that 'preprocess' comes before any realm if you
47 # need to setup hints for the remote radius server
50 # Take a User-Name, and perform some checks on it, for spaces and other
51 # invalid characters. If the User-Name appears invalid, reject the
54 # See policy.d/filter for the definition of the filter_username policy.
59 # Do checks on outer / inner User-Name, so that users
60 # can't spoof us by using incompatible identities
62 # filter_inner_identity
65 # The chap module will set 'Auth-Type := CHAP' if we are
66 # handling a CHAP request and Auth-Type has not already been set
70 # If the users are logging in with an MS-CHAP-Challenge
71 # attribute for authentication, the mschap module will find
72 # the MS-CHAP-Challenge attribute, and add 'Auth-Type := MS-CHAP'
73 # to the request, which will cause the server to then use
74 # the mschap module for authentication.
78 # Pull crypt'd passwords from /etc/passwd or /etc/shadow,
79 # using the system API's to get the password. If you want
80 # to read /etc/passwd or /etc/shadow directly, see the
81 # passwd module, above.
86 # Look for IPASS style 'realm/', and if not found, look for
87 # '@realm', and decide whether or not to proxy, based on
92 # If you are using multiple kinds of realms, you probably
93 # want to set "ignore_null = yes" for all of them.
94 # Otherwise, when the first style of realm doesn't match,
95 # the other styles won't be checked.
97 # Note that proxying the inner tunnel authentication means
98 # that the user MAY use one identity in the outer session
99 # (e.g. "anonymous", and a different one here
100 # (e.g. "user@example.com"). The inner session will then be
101 # proxied elsewhere for authentication. If you are not
102 # careful, this means that the user can cause you to forward
103 # the authentication to another RADIUS server, and have the
104 # accounting logs *not* sent to the other server. This makes
105 # it difficult to bill people for their network activity.
111 # The "suffix" module takes care of stripping the domain
112 # (e.g. "@example.com") from the User-Name attribute, and the
113 # next few lines ensure that the request is not proxied.
115 # If you want the inner tunnel request to be proxied, delete
116 # the next few lines.
119 &Proxy-To-Realm := LOCAL
123 # This module takes care of EAP-MSCHAPv2 authentication.
125 # It also sets the EAP-Type attribute in the request
126 # attribute list to the EAP type from the packet.
128 # The example below uses module failover to avoid querying all
129 # of the following modules if the EAP module returns "ok".
130 # Therefore, your LDAP and/or SQL servers will not be queried
131 # for the many packets that go back and forth to set up TTLS
132 # or PEAP. The load on those servers will therefore be reduced.
139 # Read the 'users' file
143 # Look in an SQL database. The schema of the database
144 # is meant to mirror the "users" file.
146 # See "Authorization Queries" in sql.conf
150 # If you are using /etc/smbpasswd, and are also doing
151 # mschap authentication, the un-comment this line, and
152 # enable the "smbpasswd" module.
156 # The ldap module reads passwords from the LDAP database.
160 # Enforce daily limits on time spent logged in.
167 # If no other module has claimed responsibility for
168 # authentication, then try to use PAP. This allows the
169 # other modules listed above to add a "known good" password
170 # to the request, and to do nothing else. The PAP module
171 # will then see that password, and use it to do PAP
174 # This module should be listed last, so that the other modules
175 # get a chance to set Auth-Type for themselves.
184 # This section lists which modules are available for authentication.
185 # Note that it does NOT mean 'try each module in order'. It means
186 # that a module from the 'authorize' section adds a configuration
187 # attribute 'Auth-Type := FOO'. That authentication type is then
188 # used to pick the appropriate module from the list below.
191 # In general, you SHOULD NOT set the Auth-Type attribute. The server
192 # will figure it out on its own, and will do the right thing. The
193 # most common side effect of erroneously setting the Auth-Type
194 # attribute is that one authentication method will work, but the
197 # The common reasons to set the Auth-Type attribute by hand
198 # is to either forcibly reject the user, or forcibly accept him.
202 # PAP authentication, when a back-end database listed
203 # in the 'authorize' section supplies a password. The
204 # password can be clear-text, or encrypted.
210 # Most people want CHAP authentication
211 # A back-end database listed in the 'authorize' section
212 # MUST supply a CLEAR TEXT password. Encrypted passwords
219 # MSCHAP authentication.
225 # For old names, too.
230 # Pluggable Authentication Modules.
233 # Uncomment it if you want to use ldap for authentication
235 # Note that this means "check plain-text password against
236 # the ldap database", which means that EAP won't work,
237 # as it does not supply a plain-text password.
239 # We do NOT recommend using this. LDAP servers are databases.
240 # They are NOT authentication servers. FreeRADIUS is an
241 # authentication server, and knows what to do with authentication.
242 # LDAP servers do not.
249 # Allow EAP authentication.
253 ######################################################################
255 # There are no accounting requests inside of EAP-TTLS or PEAP
258 ######################################################################
261 # Session database, used for checking Simultaneous-Use. Either the radutmp
262 # or rlm_sql module can handle this.
263 # The rlm_sql module is *much* faster
268 # See "Simultaneous Use Checking Queries" in sql.conf
273 # Post-Authentication
274 # Once we KNOW that the user has been authenticated, there are
275 # additional steps we can take.
277 # Note that the last packet of the inner-tunnel authentication
278 # MAY NOT BE the last packet of the outer session. So updating
279 # the outer reply MIGHT work, and sometimes MIGHT NOT. The
280 # exact functionality depends on both the inner and outer
281 # authentication methods.
283 # If you need to send a reply attribute in the outer session,
284 # the ONLY safe way is to set "use_tunneled_reply = yes", and
285 # then update the inner-tunnel reply.
287 # If you want privacy to remain, see the
288 # Chargeable-User-Identity attribute from RFC 4372.
289 # If you want to use it just uncomment the line below.
293 # If you want to have a log of authentication replies,
294 # un-comment the following line, and enable the
295 # 'detail reply_log' module.
299 # After authenticating the user, do another SQL query.
301 # See "Authentication Logging Queries" in sql.conf
305 # Instead of sending the query to the SQL server,
306 # write it into a log file.
311 # Un-comment the following if you have set
312 # 'edir_account_policy_check = yes' in the ldap module sub-section of
313 # the 'modules' section.
319 # Un-comment the following if you want to generate Moonshot (ABFAB) TargetedIds
320 # IMPORTANT: This requires the UUID package to be installed!
327 # Instead of "use_tunneled_reply", uncomment the
328 # next two "update" blocks.
331 # &outer.session-state: += &reply:
335 # These attributes are for the inner session only.
336 # They MUST NOT be sent in the outer reply.
338 # If you uncomment the previous block and leave
339 # this one commented out, WiFi WILL NOT WORK,
340 # because the client will get two MS-MPPE-keys
342 # update outer.session-state {
343 # MS-MPPE-Encryption-Policy !* ANY
344 # MS-MPPE-Encryption-Types !* ANY
345 # MS-MPPE-Send-Key !* ANY
346 # MS-MPPE-Recv-Key !* ANY
347 # Message-Authenticator !* ANY
353 # Access-Reject packets are sent through the REJECT sub-section of the
356 # Add the ldap module name (or instance) if you have set
357 # 'edir_account_policy_check = yes' in the ldap module configuration
359 Post-Auth-Type REJECT {
360 # log failed authentications in SQL, too.
362 attr_filter.access_reject
365 # Let the outer session know which module failed, and why.
367 update outer.session-state {
368 &Module-Failure-Message := &request:Module-Failure-Message
374 # When the server decides to proxy a request to a home server,
375 # the proxied request is first passed through the pre-proxy
376 # stage. This stage can re-write the request, or decide to
379 # Only a few modules currently have this method.
382 # Uncomment the following line if you want to change attributes
383 # as defined in the preproxy_users file.
386 # Uncomment the following line if you want to filter requests
387 # sent to remote servers based on the rules defined in the
388 # 'attrs.pre-proxy' file.
389 # attr_filter.pre-proxy
391 # If you want to have a log of packets proxied to a home
392 # server, un-comment the following line, and the
393 # 'detail pre_proxy_log' section, above.
398 # When the server receives a reply to a request it proxied
399 # to a home server, the request may be massaged here, in the
404 # If you want to have a log of replies from a home server,
405 # un-comment the following line, and the 'detail post_proxy_log'
409 # Uncomment the following line if you want to filter replies from
410 # remote proxies based on the rules defined in the 'attrs' file.
411 # attr_filter.post-proxy
414 # If you are proxying LEAP, you MUST configure the EAP
415 # module, and you MUST list it here, in the post-proxy
418 # You MUST also use the 'nostrip' option in the 'realm'
419 # configuration. Otherwise, the User-Name attribute
420 # in the proxied request will not match the user name
421 # hidden inside of the EAP packet, and the end server will
422 # reject the EAP request.
427 } # inner-tunnel server block