If I understand section 13.1.6 of the manual correctly you could add a check item of Auth-Type = Reject for the users in the DBFILE or if all of the users in that database are to be rejected, just put the check item for the DEFAULT user.
>===== Original Message From "Jon Snyder" <[EMAIL PROTECTED]> ===== >Anyone know of a simple way I might have overlooked to invert the sense of >an AuthBy? > >AcceptIfMissing is part of this, but what I'm after is more of >"RejectIfFound"--I want to reject users if they are in a DBFILE. I have >hacked this by putting a bogus User-Password into the dbm and using >AcceptIfMissing, but it would be nice if there were a way to have an AuthBy >do everything it was going to do, then have a keyword to swap ACCEPT and >REJECT when it was finished. > >_______________________________ >Jon Snyder >Computing & Networking Services >Portland State University > >=== >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. === 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.
