I don't know if I can do this ... I'm authorizing out of two databases, both dbs are in a single realm, and both dbs are in the same group. It's setup with AuthByPolicy of ContinueUntilAccept, the user could be in *either* db, therefore if it's rejected by the first db, and accepted by the second then an accept is sent to the NAS ... just the behavior I'm looking for .. If it's rejected by the first db, but accepted by the second, then an accept is sent to the NAS, any db accept sends an accept to the NAS .. Accounting is the problem. It looks like ContinueUntilAccept also means that the accounting records are only written to the first db and then stops (it's accepted!!), never to write accounting records to the second db. What I want is radiator to write accounting records to BOTH dbs .... So I tried ContinueAlways ........ If I set AuthByPolicy to ContinueAlways, I get the correct Accounting record behavior (it writes to both databases) BUT auth fails in this manner: First db accepts user ... so far so good, next database rejects user (user was only in first db, not second) and a reject is sent to the NAS ... NOT what I want! So .. is there a way to get a accept sent to the NAS if the user is in only one of the two databases AND get radiator to write accounting records to BOTH databases? Hummm ... hope this makes sense ... :-) ---- Thanx John R. Breeden Turquoise Tecjnologies, Inc Kailua-Kona, Hawaii === Archive at http://www.starport.net/~radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
