Principal object on the Server

 

After alot of digging I have come up with the following conclusion.

 

Any entity that inherits from my AuditableEntity class performs security checks using the SaveSecurityCheck override. At that time I check to see if the current Principal objects has suffecient rights, which they do. Then I call the base classes AuditSelf method which then goes on to call another method to create the AuditValues. At that point I perform another security check to see if this person can create new records. If they can then it bypasses this and moves on. If not it marks this item as InActive and then it is flagged to be viewed and approved by an Administrator or any other person with permissions.

 

The problem I am having is that when I go to create the AuditValues the Principal object fails for the same security check it passed on before it entered the AuditSelf method.

 

What can be causing this? I can not recreate this on the development version. I found that this is only happening on the version running through the BOS.

 

 

 

 

 

 

The BOS is multi-threaded, with each request processed on a separate thread.  The BOS sets the Thread.CurrentPrincipal on each request thread to the principal representing the calling user, and this should be available throughout the lifetime of the thread.  Any other threads started by application code will not have the same CurrentPrincipal unless specifically set.

 

 

 

Since AuditArgs is created with an IPrincipal, which you know to be good at that point, you could try modifying the AuditArgs class to keep and expose the IPrincipal, and then check that in subsequent processing in AuditNewEntity, et al.