Re: Passing windows credentials from server to server.

From: Andrea D'Onofrio [MSFT] (andreado_at_online.microsoft.com)
Date: 12/31/03

  • Next message: Andrea D'Onofrio [MSFT]: "Re: LogonUser API Help" 
    Date: Wed, 31 Dec 2003 09:31:49 +0100

    I've tested the scenario I suggested you on IIS 5.1 (both on ServerA and
    ServerB) and all works fine with Response.Redirect (then server side code).
    I don't know which servers there are in your scenario, but I think that, in
    this context, there are no differences with IIS 5.0 or IIS 6.0. Try to
    check:
    - ServerA -> Basic Authentication and ServerB -> Windows Integrated are the
    only options flagged
    - the Enabled Integrated Windows Authentication in the Advenced IE options
    is checked

    HtH,
    Andrea

    "Wade Wegner" <wwegner23@hotmail.com> wrote in message
    news:%23PbZGUxzDHA.1524@TK2MSFTNGP10.phx.gbl...
    > I have always thought that using the termi "windows authentication"
    referred
    > to the fact that you were authenticating to a windows account, and that it
    > qualified for both basic and NTLM. If I was incorrect, then I apologize.
    >
    > Now ...
    >
    > I have tried your suggestion, and I can get it to work under one context,
    > but not another. For isntance, when I authenticate the user on Server A,
    > and then have them click a button that redirects them to Server B, I get
    > prompted for login credentials. However, if I use a client-side vbScript
    to
    > redirect the user (window.location = "path.aspx"), then it works
    correctly.
    >
    > Am I doing something incorrectly, or will this not work for response
    > redirect?
    >
    > Thankis,
    >
    > Wade
    >
    > "Andrea D'Onofrio [MSFT]" <andreado@online.microsoft.com> wrote in message
    > news:uOu%230GvzDHA.1684@TK2MSFTNGP12.phx.gbl...
    > > Hi,
    > > > I would be very interested to hear your explanation, and know how to
    do
    > > > it -- especially if it's easily solved.
    > > ServerA -> Basic Authentication
    > > ServerB -> Windows Integrated
    > > You must turn on impersonation in ServerA web.config:
    > > <authentication mode="Windows" />
    > >
    > > <identity impersonate="true"></identity>
    > >
    > > If you have a code like Response.Redirect(http://serverB/default.aspx)
    in
    > a
    > > ServerA page, IIS (automatically) succesfully authenticate the user (the
    > > user must be a valid user for both serverA and ServerB) and you don't
    need
    > > to write any additional code.
    > >
    > > You will find more details about the issue in these articles:
    > > 283201 HOWTO: Use Delegation in Windows 2000 with COM+
    > > http://support.microsoft.com/?id=283201
    > >
    > > 287537 Using Basic Authentication to Generate Kerberos Tokens
    > > http://support.microsoft.com/?id=287537
    > >
    > > > FYI - below I did specify that Server B uses windows authentication.
    > > >
    > > FYI, extracted from your original post:
    > > ...access a page on Webserver B (which uses basic
    > > authentication), but I don't want them to have to login again ...
    > >
    > > > Thanks,
    > > > Wade
    > > HtH,
    > > Andrea
    > >
    > >
    > >
    > >
    >
    >

  • Next message: Andrea D'Onofrio [MSFT]: "Re: LogonUser API Help"
    • Quantcast