There's probably a property on the object to allow you to add your
credentials.
If not, it's still pretty easy. First, figure out what protocol the secure
site is using for authentication-- is it BASIC, DIGEST, Negotiate, or
whatever. If it's basic, it's simple-- just add an Authorization header
with the base-64 encoded username:password string. If it's digest or
Negotiate, it gets trickier.

Signature
Thanks,
Eric Lawrence
Program Manager
Assistance and Worldwide Services
This posting is provided "AS IS" with no warranties, and confers no rights.
> This might work?
> https://username:password@www.domain.com
[quoted text clipped - 11 lines]
> >
> > Ollie
Chad Z. Hower aka Kudzu - 25 Feb 2004 18:51 GMT
"Eric Lawrence [MSFT]" <e_lawrence@hotmail.com> wrote in news:#5pIH88#DHA.808
@TK2MSFTNGP12.phx.gbl:
> If not, it's still pretty easy. First, figure out what protocol the secure
> site is using for authentication-- is it BASIC, DIGEST, Negotiate, or
> whatever. If it's basic, it's simple-- just add an Authorization header
> with the base-64 encoded username:password string. If it's digest or
> Negotiate, it gets trickier.
Indy supports all of these authentications and more. Its also free.
http://www.indyproject.org/
The only problem is that the .net version doesnt support SSL yet. BUT you
could bundle it with an SSL tunnel if your options are limited.
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"