Calling a webservice from my ASP.NET application

[J-T]

I 'm calling a web service using this code:

MyService service = new MyService();
service.Credent ials = System.Net.Cred entialCache.Def aultCredentials ;

I was getting an "Access Denied" everytime, but it works when I use this
code :

MyService service = new MyService();
service.Credent ials = new
NetworkCredenti al("myLogin","m yPassword","myD omaine");

I have enabled impersonation by adding <identity impersonate="tr ue" /> to my
web config and we are using windows authentication. What else should I add in
order to get it up and workin?

Thanks

[Scott Allen]

Hi J-T :

Impersonation generally does not work in this scenario, because the
user's credentials will have to make 2 hops, which isn't allowed
without some special configuration:

http://odetocode.com/Blogs/scott/arc...2/24/1053.aspx

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Wed, 25 May 2005 17:38:05 -0700, "J-T" <J-*@microsft.com> wrote:

I 'm calling a web service using this code:

MyService service = new MyService();
service.Creden tials = System.Net.Cred entialCache.Def aultCredentials ;

I was getting an "Access Denied" everytime, but it works when I use this
code :

MyService service = new MyService();
service.Creden tials = new
NetworkCredent ial("myLogin"," myPassword","my Domaine");

I have enabled impersonation by adding <identity impersonate="tr ue" /> to my
web config and we are using windows authentication. What else should I add in
order to get it up and workin?

Thanks

[J-T]

Scott,I've seen all your articles (I sent my questions to you,but apparently
your comment part dosen't work;-).

The problem is that They have installed reporting services and our asp.net
application in the **same box** (which I know is not a good idea,but why I
don't know).Therefore that problem should not exist because as you mentioned
that's for the time you have reporting services and your app in two
different places.

I think I found the problem ,the person who has this problem is opening
another thread(than the asp.net thread) to call the webservice and the
reason he get the second logon page is that the token is not transfered from
the main thread to his newly-opened thread.

Can you guide me to something which shows the advantagesa dn disadvantages
of having RS and the main application in the same box?

Thanks alot Scott

"Scott Allen" <sc***@nospam.o detocode.com> wrote in message
news:ku******** *************** *********@4ax.c om...

Hi J-T :

Impersonation generally does not work in this scenario, because the
user's credentials will have to make 2 hops, which isn't allowed
without some special configuration:

http://odetocode.com/Blogs/scott/arc...2/24/1053.aspx

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Wed, 25 May 2005 17:38:05 -0700, "J-T" <J-*@microsft.com> wrote:

I 'm calling a web service using this code:

MyService service = new MyService();
service.Crede ntials = System.Net.Cred entialCache.Def aultCredentials ;

I was getting an "Access Denied" everytime, but it works when I use this
code :

MyService service = new MyService();
service.Crede ntials = new
NetworkCreden tial("myLogin", "myPassword","m yDomaine");

I have enabled impersonation by adding <identity impersonate="tr ue" /> to
my
web config and we are using windows authentication. What else should I add
in
order to get it up and workin?

Thanks

[Scott Allen]

Hey J-T:

On Thu, 26 May 2005 09:56:34 -0700, "J-T" <J-*@microsft.com> wrote:

Scott,I've seen all your articles (I sent my questions to you,but apparently
your comment part dosen't work;-).

Oh - is this in the OdeToCode.com/articles area?
The problem is that They have installed reporting services and our asp.net
application in the **same box** (which I know is not a good idea,but why I
don't know).Therefore that problem should not exist because as you mentioned
that's for the time you have reporting services and your app in two
different places.

Yes - having them on the same machine should make it easier....
I think I found the problem ,the person who has this problem is opening
another thread(than the asp.net thread) to call the webservice and the
reason he get the second logon page is that the token is not transfered from
the main thread to his newly-opened thread.

Ah - that would be the problem. Only the original thread of the
request gets the impersonation token. I've heard in 2.0 they actually
propogate the impersonation token but I have not verified it this ...
Can you guide me to something which shows the advantagesa dn disadvantages
of having RS and the main application in the same box?

I sincerely apologize that the comments did not get through.

Off hand I don't know of any official documentation on the advantages
/ disadvantages. My personal opinion would be:

Advantages:

Easier authentication scenarios (impersonation works)
Faster response
Disadvantages:

Performance (SSRS can be a resource hog under load - if your user base
expands you may need to move RS to another machine anyway)

Licensing (You have to pay for a SQL License too).

--
Scott
http://www.OdeToCode.com/blogs/scott/

--
Scott
http://www.OdeToCode.com/blogs/scott/

[J-T]

> Oh - is this in the OdeToCode.com/articles area?
Yes,couple days ago,I submitted a comment but never got appears(I'm an
every-day reader of yours;-))

I sincerely apologize that the comments did not get through. I think I've leanrt enough from your weblog and OdeToCode.com in a way that
you **do not** need to apologize for my comment not going through.Such a
wonderful weblog.I love it

Thanks for the vaulable information.

Reza
"Scott Allen" <sc***@nospam.o detocode.com> wrote in message
news:lc******** *************** *********@4ax.c om... Hey J-T:

On Thu, 26 May 2005 09:56:34 -0700, "J-T" <J-*@microsft.com> wrote:

Scott,I've seen all your articles (I sent my questions to you,but
apparently
your comment part dosen't work;-).

Oh - is this in the OdeToCode.com/articles area?

The problem is that They have installed reporting services and our asp.net
application in the **same box** (which I know is not a good idea,but why I
don't know).Therefore that problem should not exist because as you
mentioned
that's for the time you have reporting services and your app in two
different places.

Yes - having them on the same machine should make it easier....

I think I found the problem ,the person who has this problem is opening
another thread(than the asp.net thread) to call the webservice and the
reason he get the second logon page is that the token is not transfered
from
the main thread to his newly-opened thread.

Ah - that would be the problem. Only the original thread of the
request gets the impersonation token. I've heard in 2.0 they actually
propogate the impersonation token but I have not verified it this ...

Can you guide me to something which shows the advantagesa dn disadvantages
of having RS and the main application in the same box?

I sincerely apologize that the comments did not get through.

Off hand I don't know of any official documentation on the advantages
/ disadvantages. My personal opinion would be:

Advantages:

Easier authentication scenarios (impersonation works)
Faster response
Disadvantages:

Performance (SSRS can be a resource hog under load - if your user base
expands you may need to move RS to another machine anyway)

Licensing (You have to pay for a SQL License too).

--
Scott
http://www.OdeToCode.com/blogs/scott/

--
Scott
http://www.OdeToCode.com/blogs/scott/