3.36.26. Asynchronous Previous topic Parent topic Child topic Next topic

Normally, AuthBy RADIUS completes 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, but be cautious when enabling the Asynchronous flag.
When you enable the Asynchronous flag, Handler now returns to AuthBy stack after a reply or timeout from the remote proxy. This allows <AuthBy RADIUS> and its subclasses to return evaluating AuthByPolicy when a reply is received from the remote proxy. Asynchronous is supported by <AuthBy RADIUS> and its subclasses.
For more information about how proxied requests are waited for by Radiator, see Section 3.36. <AuthBy RADIUS> and Section 3.36.25. 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>