Web Services client and Basic Auth

[Old Man]

using c# in a windows application.

I am developing a webservice to run on our extranet SSL server. The
company policy is that this server log everybody in.

I am going to use the WSE security, but what is stoping me now is the first
basic auth login handshake.

The webservice works on my dev box, but when i use the test tool I wrote in
c# windows application it fails because it cant get to the webservice, it
is stopped at the Basic Auth.

I saw on the web where you can create a login object and attach it to the
webrequest object, webrequest is buried deep in the
System.Web.Serv ices.Protocols and not available to me.

What can i do - is the only option that I have at present is build the soap
packet myself and then use manual code to send it on to the webservice....
this is not a desirable option.

[Jared]

It's in VB but you shouldn't have any problems with it. MSDN has some good
reading on NetworkCredenti al and the like.

Dim l As New localhost.MyWeb Service
Dim cred As System.Net.ICre dentials 'Or networkcredenti als, whatever you
prefer
cred = New System.Net.Netw orkCredential(M e.txtUser.Text. Trim,
Me.txtPassword. Text.Trim)
l.Credentials = cred

dim SomValue as string = l.SomeService

"Old Man" <Ol*****@Nursin gHome.com> wrote in message
news:Xn******** *************** ***********@63. 223.5.246...

using c# in a windows application.

I am developing a webservice to run on our extranet SSL server. The
company policy is that this server log everybody in.

I am going to use the WSE security, but what is stoping me now is the
first
basic auth login handshake.

The webservice works on my dev box, but when i use the test tool I wrote
in
c# windows application it fails because it cant get to the webservice, it
is stopped at the Basic Auth.

I saw on the web where you can create a login object and attach it to the
webrequest object, webrequest is buried deep in the
System.Web.Serv ices.Protocols and not available to me.

What can i do - is the only option that I have at present is build the
soap
packet myself and then use manual code to send it on to the webservice....
this is not a desirable option.

[syd]

after a bit of looking i found this...
Pass Current Credentials to an ASP.NET Web Service
http://support.microsoft.com/?kbid=813834
"Jared" <VB***********@ email.com> wrote in
news:10******** *****@corp.supe rnews.com:

It's in VB but you shouldn't have any problems with it. MSDN has some
good reading on NetworkCredenti al and the like.

Dim l As New localhost.MyWeb Service
Dim cred As System.Net.ICre dentials 'Or networkcredenti als, whatever
you prefer
cred = New System.Net.Netw orkCredential(M e.txtUser.Text. Trim,
Me.txtPassword. Text.Trim)
l.Credentials = cred

dim SomValue as string = l.SomeService

"Old Man" <Ol*****@Nursin gHome.com> wrote in message
news:Xn******** *************** ***********@63. 223.5.246...

using c# in a windows application.

I am developing a webservice to run on our extranet SSL server. The
company policy is that this server log everybody in.

I am going to use the WSE security, but what is stoping me now is the
first
basic auth login handshake.

The webservice works on my dev box, but when i use the test tool I
wrote in
c# windows application it fails because it cant get to the
webservice, it is stopped at the Basic Auth.

I saw on the web where you can create a login object and attach it to
the webrequest object, webrequest is buried deep in the
System.Web.Serv ices.Protocols and not available to me.

What can i do - is the only option that I have at present is build
the soap
packet myself and then use manual code to send it on to the
webservice.... this is not a desirable option.

[Jared]

Syd,
I don't think that will work in this scenario, Old specifically stated
that he needed to use Basic Windows Authentication which passes your
credentials in base64 encoded clear text. Windows Integrated uses a hash,
which "cannot" be decrypted, it just verifies the signature. Since basic
can't verify the identity, it should not allow access.
Your method works great for Windows Integrated.
Jared

"syd" <sy************ *@klassifiedbbs .net> wrote in message
news:Xn******** *************** **********@63.2 23.5.246...

after a bit of looking i found this...
Pass Current Credentials to an ASP.NET Web Service
http://support.microsoft.com/?kbid=813834
"Jared" <VB***********@ email.com> wrote in
news:10******** *****@corp.supe rnews.com:

It's in VB but you shouldn't have any problems with it. MSDN has some
good reading on NetworkCredenti al and the like.

Dim l As New localhost.MyWeb Service
Dim cred As System.Net.ICre dentials 'Or networkcredenti als, whatever
you prefer
cred = New System.Net.Netw orkCredential(M e.txtUser.Text. Trim,
Me.txtPassword. Text.Trim)
l.Credentials = cred

dim SomValue as string = l.SomeService

"Old Man" <Ol*****@Nursin gHome.com> wrote in message
news:Xn******** *************** ***********@63. 223.5.246...

using c# in a windows application.

I am developing a webservice to run on our extranet SSL server. The
company policy is that this server log everybody in.

I am going to use the WSE security, but what is stoping me now is the
first
basic auth login handshake.

The webservice works on my dev box, but when i use the test tool I
wrote in
c# windows application it fails because it cant get to the
webservice, it is stopped at the Basic Auth.

I saw on the web where you can create a login object and attach it to
the webrequest object, webrequest is buried deep in the
System.Web.Serv ices.Protocols and not available to me.

What can i do - is the only option that I have at present is build
the soap
packet myself and then use manual code to send it on to the
webservice.... this is not a desirable option.