Open sylum opened 7 years ago
Where are you attempting to serialize the ClaimsIdentity? Between web and app server, or out to a mobile client device?
Hi Rocky,
I'm attempting to serialize the ClaimsIdentity between web and app server. Both of them will be hosted on Azure (webApp container).
I don't know if ClaimsIdentity is marked as Serializable
- as in whether Microsoft allows it to serialize using BinaryFormatter or NDCS. If it is serializable using those technologies (and you aren't planning to ever use .NET Core) then there are some options in that regard.
Otherwise you'll need to do one of the following:
The first option basically bypasses any sort of distributed security provided by your network infrastructure. The second option leverages any sort of distributed security provided by your network infrastructure.
fwiw, the issue here is pretty much the same as with a WindowsIdentity (also not serializable). Either you get the underlying network to support impersonation and pass keys through the data portal so you can reauthenticate on each machine, or you pull the relevant data out of the identity into your identity and pass that around through the data portal.
Thank you very much for your good advices. You give me enough matter to pursue my investigations. I think i will dig up the solution 1.
Hi Folks,
I'm currently working on n tiers MCV5 + CSLA 4.6.1 application using the dataportal with MobileProxy. I'm facing somes diffuciltes with the authentication, cause the ClaimsIdentity needs to implement IMobileObject. Does anyone have already do this kind of implementation ?
thanks for your helps,
Cedric