Hello James -
Yes this has changed in Radiator 3.1 - I suggest you upgrade. regards Hugh On Tue, 9 Jul 2002 13:21, James Wiegand wrote: > Just to clarify, because under section 6.30 RewriteUsername is not listed, > even though it is shown in section 6.45, is it legal to have a > RewriteUsername statement under a Hosts clause? This would be useful. > > Sorry to be pedantic, but the statement that anything which is legal in a > Hosts clause is not clear in the context of a RewriteUsername statement. > In 2.18 I seem to remember not being able to include a rewrite statement in > a Hosts clause. Is this changed for 3.1? > > Thanks for the help, > > Jim Wiegand, BSEE, MSE > Supervisor, Infrastructure Operations > Fiberlink Communications > 215 793 6554 > > > The information transmitted is intended only for the person or entity to > which it is addressed and may contain confidential and/or privileged > material. Any review, retransmission, dissemination or other use of, or > taking of any action in reliance upon, this information by persons or > entities other than the intended recipient is prohibited. If you received > this in error, please contact the sender and delete the material from any > computer. > > > > > Hugh Irvine > <[EMAIL PROTECTED] To: "James Wiegand" > m.au> <[EMAIL PROTECTED]>, > "'[EMAIL PROTECTED]'" > <[EMAIL PROTECTED]> 07/08/2002 cc: > 07:11 PM Subject: Re: (RADIATOR) > Selecting domain Please stripping in AuthBySQLRADIUS respond > to > hugh > > > > > > > > Hello James - > > In Radiator 3.1, you can use the AuthBy SQLRADIUS clause with > HostColumnDef's > to supply a RewriteUsername (or not). > > Note that you will need the patched version of AuthBy SQLRADIUS from the > Radiator 3.1 patches area. > > See section 6.45 in the Radiator 3.1 reference manual ("doc/ref.html"). > > regards > > Hugh > > On Tue, 9 Jul 2002 06:31, James Wiegand wrote: > > Hello, > > > > I am trying to come up with a config where we can store the bulk of our > > roaming configurations in an SQL table. There is one question that does > > not seem to be obvious from the configuration. Is it possible to have to > > strip the domain (or not) based on the (domain, host) key? > > > > Here's the scenario: > > > > [EMAIL PROTECTED] -> [EMAIL PROTECTED] sent to host1 > > -> [EMAIL PROTECTED] sent to host2 > > > > [EMAIL PROTECTED] -> user sent to host1 > > -> user sent to host2 > > > > [EMAIL PROTECTED] -> [EMAIL PROTECTED] sent to host1 > > -> user sent to host2 > > > > Any ideas? > > > > Jim Wiegand, BSEE, MSE > > Supervisor, Infrastructure Operations > > Fiberlink Communications > > 215 793 6554 > > > > > > The information transmitted is intended only for the person or entity to > > which it is addressed and may contain confidential and/or privileged > > material. Any review, retransmission, dissemination or other use of, or > > taking of any action in reliance upon, this information by persons or > > entities other than the intended recipient is prohibited. If you > > received > > > this in error, please contact the sender and delete the material from any > > computer. > > > > > > === > > Archive at http://www.open.com.au/archives/radiator/ > > Announcements on [EMAIL PROTECTED] > > To unsubscribe, email '[EMAIL PROTECTED]' with > > 'unsubscribe radiator' in the body of the message. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.