Previous page Section 3.42.31. NoReplyReject Section 3.42.32. Asynchronous (632 / 1693)   Table of Contents Section 3.42.33. Synchronous Next page

3.42.32. Asynchronous Previous topic Parent topic Child topic Next topic

The default behaviour for <AuthBy RADIUS> is to return IGNORE as soon as the request has been forwarded to the remote RADIUS server. It does not wait for a reply before moving on to other AuthBy classes, or handling new requests. You can change this behaviour with the Asynchronous flag. This flag is recommended for all new configurations.
When you enable the Asynchronous flag, Handler continues to evaluate its AuthBy policy after a reply or timeout from the remote proxy. Other requests are processed while the reply is pending. Asynchronous is supported by <AuthBy RADIUS> and its subclasses.
For more information about how proxied requests are waited for by Radiator, see Section 3.42. <AuthBy RADIUS> and Section 3.42.33. Synchronous. 
# Auth to server1 and continue to AuthBy FILE if server 1 accepts.
# Process other requests while the reply from server 1 is pending.
<Handler>
      AuthByPolicy ContinueWhileAccept
      <AuthBy RADIUS>
            # Evaluate the policy when we get a reply or a timeout
            Asynchronous
            Host server1
            Secret xxxxxx
      </AuthBy>
      <AuthBy FILE>
            Filename %D/users
      </AuthBy>
</Handler>
Previous page Section 3.42.31. NoReplyReject Section 3.42.32. Asynchronous (632 / 1693)   Table of Contents Section 3.42.33. Synchronous Next page