RE: ASP.Net 2.0 windows IsInRole error
- From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng [MSFT])
- Date: Tue, 22 Jul 2008 02:21:24 GMT
Thanks for your followup Mike,
I'm glad that you've figured out the original issue and let us know the
progress.
Sure, welcome to post in the newsgroup for any new issuess you encounter.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: =?Utf-8?B?YmFrZQ==?= <mikeemail@xxxxxxxxxxxxx><WHBmo1J6IHA.1620@xxxxxxxxxxxxxxxxxxxxxx>
References: <7F58E31C-DF7A-4374-A1B2-0ED8A5760F8C@xxxxxxxxxxxxx>
Subject: RE: ASP.Net 2.0 windows IsInRole error
Date: Mon, 21 Jul 2008 14:59:01 -0700
Hi Steven,a
I have an update for you. I wrote a test app to remove any application
specific variables, and found that we were actually calling IsInRole with
non-existent group and without specifying the domain. Sorry about that,there
was some miscommunication between the person who wrote the code and me. Sothink
the group does not exist anywhere, and no domain was specified. I would
that in a perfect world (no bugs in framework, our network set upcorrectly,
etc.), it would not blow up, but it is easy enough for us to work around.is
However, we are still seeing strange behavior from the IsInRole call. It
acting differently on our XP Pro workstations (in one domain) than when itis
running on our 2003 Web Servers (in another domain).snippets,
I'll create a new posting to cover the scenarios, and include code
etc.method
Thank you,
Mike
"Steven Cheng [MSFT]" wrote:
Hi Mike,
From your description, when calling the "WindowPrincipal.IsInRole"
domainin an ASP.NET webservice , you got the following exceptiton, correct?
"The trust relationship between the primary domain and the trusted
thisfailed...."
Based on my research, there are some existing common issue related to
nameerror message. And most of them are caused by not supplying the domain
problemwhen call "IsInRole" function. However, as you said that you've already
supply the domain name in the account name parameter, I think the
thanhere is a bit different. Would you also post the code snippet in your
webmethod which call the "IsInRole" function?
Also, for the trusted domain part, have you verified that if the account
(you passed into "isInRole" function) is from the same domain(rather
another trusted domain) of the webserver, it will work correct?
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
.
- References:
- RE: ASP.Net 2.0 windows IsInRole error
- From: Steven Cheng [MSFT]
- RE: ASP.Net 2.0 windows IsInRole error
- From: bake
- RE: ASP.Net 2.0 windows IsInRole error
- Prev by Date: RE: ASP.Net 2.0 windows IsInRole error
- Next by Date: Kerberos Authentication - IE session re-requires authentication but it won't take.
- Previous by thread: RE: ASP.Net 2.0 windows IsInRole error
- Next by thread: Cannot solve SSL in IIS 6 with host headers
- Index(es):
Relevant Pages
|