The docs state that a <Realm DEFAULT>  will be handled before any
<Handler> clauses are taken.  This seems a bit odd as the Handler is more
fine tuned and sometimes a <Realm DEFAULT> is needed, so it overrides your
Handlers.  Example:

<Handler Service-Type=Framed-User>
        <AuthBy SQL>
        </AuthBy>
</Handler>
<Handler>
        <AuthBy FILE>
        </AuthBy>
</Handler>
<Realm DEFAULT>
        <AuthBy IPASS>
        </AuthBy>
</Realm>

Now in order to use Ipass, I need that <Realm DEFAULT> in there to catch
the roaming people.  How could I mesh these two so my local customers
still work?  What I'm finding is that local usernames are passed into
Ipass because they fall into the <Realm DEFAULT> clause.  However, I need
those Handlers in there to match certain types of customers, but they are
never consulted because the Realm clause wins.  Any better way of writing
this?  Maybe a <Handler> clause that looks for the @ symbol in the
User-Name attribute?

--------------------------------------------------------------------------
Aaron Holtz
ComNet Inc.
UNIX Systems Specialist
Email:  [EMAIL PROTECTED]
"It's not broken, it just lacks duct tape."
--------------------------------------------------------------------------



===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.

Reply via email to