add new issue       

Issue ID:  736     Add config option to block passing principal through SL data portal      
Created by rocky on 2010-04-21 11:12 AM, 2770 days ago
Project:  CSLA .NET for Silverlight
Category:  enhancement
Priority:  high
Status:  closed
Feature area:Data Portal
Version:4.0.x
  Entering "issue#999" in comment creates link to id 999

show inline images      show change history

comment 2503 posted by sergeyb on 2010-04-28 8:41 PM, 2763 days ago 
Add config option to block passing principal through SL data portal.  Implement exact same way as .NET Portal - ApplicationContext.AuthenticationType="Windows" or "Csla"
comment 2463 posted by rocky on 2010-04-23 12:01 PM, 2768 days ago 
merged bug 362 into this bug:
Allow SL client to retrieve pre-existing ASP.NET principal object
comment 2431 posted by rocky on 2010-04-23 11:47 AM, 2768 days ago 
Ideally this would be a setting in ApplicationContext, so any proxy/host objects can honor the setting.
comment 2416 posted by rocky on 2010-04-21 11:12 AM, 2770 days ago 
It should be possible to tell the SL client data portal to not pass the principal to the server, and to tell the server not to expect to get a principal from the client. Much like the CslaAuthorization concept from the .NET data portal.
comment 1144 posted by rocky on 2009-03-05 8:48 AM, 3182 days ago 
Right now the data portal always resets HttpContext.Current.User to the client value, making it impossible for the SL client to ever pick up a pre-existing server-side principal to return it to the client.

http://forums.lhotka.net/forums/thread/31622.aspx