2 # This file represents a server that is implementing an identity
3 # provider for GSS-EAP (RFC 7055) using the trust router
4 # protocol for dynamic realm discovery. Any ABFAB identity
5 # provider is also an ABFAB relying party proxy.
7 # This file does not include a TLS listener; see abfab-tls for a simple
8 # example of a RADSEC listener for ABFAB.
20 # If you intend to use CUI and you require that the Operator-Name
21 # be set for CUI generation and you want to generate CUI also
22 # for your local clients then uncomment the operator-name
23 # below and set the operator-name for your clients in clients.conf
27 # If you want to generate CUI for some clients that do not
28 # send proper CUI requests, then uncomment the
29 # cui below and set "add_cui = yes" for these clients in clients.conf
47 # Allow EAP authentication.
52 # Once we KNOW that the user has been authenticated, there are
53 # additional steps we can take.
56 # For EAP-TTLS and PEAP, add the cached attributes to the reply.
57 # The "session-state" attributes are automatically cached when
58 # an Access-Challenge is sent, and automatically retrieved
59 # when an Access-Request is received.
61 # The session-state attributes are automatically deleted after
62 # an Access-Reject or Access-Accept is sent.
65 &reply: += &session-state:
68 # Create the CUI value and add the attribute to Access-Accept.
69 # Uncomment the line below if *returning* the CUI.
73 # If you want to have a log of authentication replies,
74 # un-comment the following line, and enable the
75 # 'detail reply_log' module.
78 # After authenticating the user, do another SQL query.
80 # See "Authentication Logging Queries" in sql.conf
84 # Un-comment the following if you want to modify the user's object
85 # in LDAP after a successful login.
89 # For Exec-Program and Exec-Program-Wait
91 # Remove reply message if the response contains an EAP-Message
92 remove_reply_message_if_eap
93 # Access-Reject packets are sent through the REJECT sub-section of the
96 # Add the ldap module name (or instance) if you have set
97 # 'edir_account_policy_check = yes' in the ldap module configuration
99 Post-Auth-Type REJECT {
100 # log failed authentications in SQL, too.
102 attr_filter.access_reject
104 # Insert EAP-Failure message if the request was
105 # rejected by policy instead of because of an
106 # authentication failure And already has an EAP message
107 # For non-ABFAB, we insert the failure all the time, but for ABFAB
108 # It's more desirable to preserve reply-message when we can
109 if (&reply:Eap-Message) {
113 # Remove reply message if the response contains an EAP-Message
114 remove_reply_message_if_eap
118 # When the server decides to proxy a request to a home server,
119 # the proxied request is first passed through the pre-proxy
120 # stage. This stage can re-write the request, or decide to
123 # Only a few modules currently have this method.
126 # Before proxing the request add an Operator-Name attribute identifying
127 # if the operator-name is found for this client.
128 # No need to uncomment this if you have already enabled this in
129 # the authorize section.
132 # The client requests the CUI by sending a CUI attribute
133 # containing one zero byte.
134 # Uncomment the line below if *requesting* the CUI.
137 # Uncomment the following line if you want to change attributes
138 # as defined in the preproxy_users file.
141 # Uncomment the following line if you want to filter requests
142 # sent to remote servers based on the rules defined in the
143 # 'attrs.pre-proxy' file.
144 # attr_filter.pre-proxy
146 # If you want to have a log of packets proxied to a home
147 # server, un-comment the following line, and the
148 # 'detail pre_proxy_log' section, above.
152 # When the server receives a reply to a request it proxied
153 # to a home server, the request may be massaged here, in the
158 # If you want to have a log of replies from a home server,
159 # un-comment the following line, and the 'detail post_proxy_log'
163 # Uncomment the following line if you want to filter replies from
164 # remote proxies based on the rules defined in the 'attrs' file.
165 # attr_filter.post-proxy
168 # If you are proxying LEAP, you MUST configure the EAP
169 # module, and you MUST list it here, in the post-proxy
172 # You MUST also use the 'nostrip' option in the 'realm'
173 # configuration. Otherwise, the User-Name attribute
174 # in the proxied request will not match the user name
175 # hidden inside of the EAP packet, and the end server will
176 # reject the EAP request.