all groups > dotnet remoting > july 2006 >
You're in the

dotnet remoting

group:

"authorizedGroup" and Globalization


"authorizedGroup" and Globalization Günter Prossliner
7/20/2006 12:19:54 PM
dotnet remoting:
Hi everyone!

I want to create an IpcChannel without security, so than everyone can access
the channel. Even if I set the "IsSecured" Property of the IpcServerChannel
to false, I got "Access denied" Exceptions? Why does this happen? Is it not
possible to disable the security - restrictions at all? If no, why is there
an "IsSecured" Property, if it has no effect?

The solution that I have implemented, it to add the following Channel
Property:

channelProps["authorizedGroup"] = "Everyone";

This works fine on my (engish) computer. Some of our developers are using a
German Windows OS. I get the exception that the Windows Prinzipal cannot be
resolved. On a German Windows there is no "Everyone" group instead the Group
is named "Jeder".

What I do now, is to query the windows language, and so I decide to use
"Everyone" or "Jeder". In my case this works, because in our environment
Windows is installed eigher in German or in English.

But I wonder if there is any way to get the localized name of the "Everyone"
Group by code. What if the OS is installed in Greek or Chinse? It's very
anoying, that Windows does not accept the english names.

Any ideas?


br,
Guenter Prossliner

Re: "authorizedGroup" and Globalization Günter Prossliner
7/21/2006 12:00:00 AM
Hi everyone!

[quoted text, click to view]

Now I use the LookupAccountSid API Function for the translation of wellkown
SIDs (like Everyone) to localized names.


br
GP

AddThis Social Bookmark Button