James,

I would like to add that I've noted the same behavour as Rainer - related to
the failing of authentication if the SQL transaction fails. I can understand
the reasoning from a security standpoint in a highly secure environment.
You've indicated that if both text logging and sql logging are enabled, then
authentication will not fail upon loss of sql logging alone. Other MS
documents also support this statement. However, from what I can tell, a loss
of sql logging will cause a failure in authentication - regardless if text
logging is enabled or not. I'm just in the process of setting our IAS up
(still testing) and don't have any previous experience with it, so it may be
possible that I have something configured incorrectly. I found this thread
after trying to test the very feature (using both sql and text logging - the
n
'breaking it's sql logging capability). It appears that a successful
authentication is logged in the text file even with the sql log failure -
however the connection actually fails authentication. The IAS Server System
Log also indicates authentication failure in this scenario for me.

Like Rainer, I would also like to see the SQL Logging be configurable - with
a choice to allow authentication even if the logging failed. Additionally,
I'm not sure if there is a documentation error or I have a configuration
issue related to the above authentication failure even with the dual logging
configuation.

Thanks,
Brian Brocker


"Rainer Sinsch" wrote:

> Hi James,
>
> thanks for forwarding the feature request! I have written an email to your
> provided email-address (removed the no-spam) with all my detailed contact
> information.
>
> /Rainer
>
> "James McIllece [MS]" <jamesmci@online.microsoft.com> schrieb im Newsb
eitrag
>  news:Xns994C8CFD113F6jamesmcionlinemicro
s@207.46.248.16... 
>
>
>

[ Post a follow-up to this message ]