Can anyone suggest the best place in WCF to catch SecurityExcepti ons arising
from failed authorization (declarative model) or CAS exceptions. I was hoping
that my IErrorHandler.H andleError implementation would do it but the original
exception has already been transformed to a FaultException by that point and
the original exception details are lost. These problems have been very
difficult to diagnose without a central error handling location.
I have also set
ServiceSecurity AuditBehavior newAudit = new
ServiceSecurity AuditBehavior() ;
newAudit.AuditL ogLocation = AuditLogLocatio n.Application;
newAudit.Messag eAuthentication AuditLevel = AuditLevel.Fail ure;
newAudit.Servic eAuthorizationA uditLevel = AuditLevel.Fail ure;
Description.Beh aviors.Remove<S erviceSecurityA uditBehavior>() ;
Description.Beh aviors.Add(newA udit);
Don't see any events in the Application log.
Thanks in advance
from failed authorization (declarative model) or CAS exceptions. I was hoping
that my IErrorHandler.H andleError implementation would do it but the original
exception has already been transformed to a FaultException by that point and
the original exception details are lost. These problems have been very
difficult to diagnose without a central error handling location.
I have also set
ServiceSecurity AuditBehavior newAudit = new
ServiceSecurity AuditBehavior() ;
newAudit.AuditL ogLocation = AuditLogLocatio n.Application;
newAudit.Messag eAuthentication AuditLevel = AuditLevel.Fail ure;
newAudit.Servic eAuthorizationA uditLevel = AuditLevel.Fail ure;
Description.Beh aviors.Remove<S erviceSecurityA uditBehavior>() ;
Description.Beh aviors.Add(newA udit);
Don't see any events in the Application log.
Thanks in advance
Comment