(RADIATOR) Connection for all

[Steve Roderick]

You should be able to have a fall through handler that authenticates the user but returns a different IP address and possibly a filter attribute. So, if the first authentication (is account active) failed then it would fall through to the next one (special IP assignment).

Something like:

        AuthByPolicy ContinueUntilAccept

        # This will verify that the account is active and allow the user
        AuthBy StandardCustomerTesting

        # This will always allow the user to gain access (or better yet, anyone in the database)
        # but will assign an IP address from a special pool
        AuthBy StatusAccessOnly

If you configured your network to allow access to your account status site from both your normal IP pool and your special IP pool it should do what you want. Unfortunately, you will get lots of customers who aren't trying to get to the access info and will think that something is seriously wrong. Then they will call you anyway. A possible solution might be to put everyone behind a web proxy and then have the proxy redirect any request coming from the special pool to the account status site.

Just some thoughts.

Steve
  ----- Original Message ----- 
  From: Mohammed AbdusSami 
  To: 'Hugh Irvine' ; radiator at open.com.au 
  Sent: Tuesday, November 12, 2002 2:16 AM
  Subject: (RADIATOR) Connection for all


  Dear All,

   

  Right now radiator is configured in such a way that only Active customers will get the connection.  What I need is even if they are on hold I want them to get connected assign a separate IP pool so that they can know at least their account status immediately, which will help to activate it.

   

  Regards,

   

  AbdusSami

   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20021113/f2a6007c/attachment-0001.html>