SecurityIdentifier not marked as serializable

[Dominick Baier [DevelopMentor]]

why don't you use the AD(AM) Membership provider that comes with ASP.NET??

 

[JB]

Hello all,

Some days ago I posted a question about a problem with a
SecurityIdentifier at:

http://groups.google.com/group/micr...6ed430f28d6/9f1c551da8359ac4#9f1c551da8359ac4

I hope someone can help me with it since I still have no clue how to
fix this,

TIA,
Jeroen

 

[Dominick Baier [DevelopMentor]]

ok - valid point

well he is right you cannot serialize SecurityIdentifier - don't know why
he wants to - would have to look at the code

maybe this helps:
http://www.oftedal.no/~erlend/?blogid=8

 

[JB]

Hi Dominick, thanks for answering. I do not use that one because it
does not support assigning roles to ADAM users, it only supports
assigning roles to domain users.

Do you perhaps know what's the cause of this error?

Jeroen

 

[JB]

Thanks, I know that posting, I first started writing my own custom
Membership provider using the code you linked to. But then I did not
get all of it to work properly (getting a list of all users in a
certain role did not work properly etc). Its code is posted at

http://groups.google.com/group/micr...+membership+provider&rnum=10#25fda10aea303196

After that I found the other provider which seemed to be written with a
early version of .NET 2 but by someone with good knowledge of ADAM and
Active Directory. So I decided to use that code and fix it up so it now
compiles for the current .NET 2 version. However, it looks like
Microsoft has sharpened the security policies a little and made the
SecurityIdentifier non-serializable in a later release.

Do you know how to make this work anyway? Or perhaps a valid
implementation for the methods that lack in my implementation?

Thanks,
Jeroen