hi Andreas
>> well, i don't know why you need 4-5 queries but supposing you need
>> them, why would you need less later on? where is the difference
>> whether you do the db query before or later, that's what i don't
>> catch. and the increase of the counter, what you want to do in case
>> of succ
Hi Artur,
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Artur
> Hecker
> Sent: Monday, January 27, 2003 12:28 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Action to perform when EAP/TLS has finished successfully
>
hi Andreas
> where does this help me ? If I understood you correctly here, the
> only improvemnt would apply to the athentication attempt, which would
> later on fail for sql-query reasons. Since the reject-action would be
> determined very early in the process, we'd avoid the 3-4
> Request/chal
Hi Artur,
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Artur
> Hecker
> Sent: Sunday, January 26, 2003 6:08 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Action to perform when EAP/TLS has finished successfully
>
&g
hi
> well, the reason is that I want to base the decision to grant or deny access based
>on the outcome of some database queries, which I believe is a costly operation. To do
>this, I can hook somewhere into the process and to my queries for every
>access-request which I receive, or in other w
ubject: Re: Action to perform when EAP/TLS has finished successfully
>
>
> hi
>
>
> i don't think i can really help you, but i want first to understand why
> you want to do that? i mean do you want to send a reject if your prior
> checks are wrong? or why are yo
hi
i don't think i can really help you, but i want first to understand why
you want to do that? i mean do you want to send a reject if your prior
checks are wrong? or why are you trying to do something before the last
accept message? what's the reason?
i kind of think, that what you want to do i
