[THIN] Re: Web Interface, Passthrough Auth, Cannot reconnect

  • From: Jeff <hicksj3@xxxxxxxxx>
  • To: thin@xxxxxxxxxxxxx
  • Date: Wed, 1 Mar 2006 11:03:29 -0700

I ASSUMED that if my credentials are passed through and I double click the
icon, the WI would work the same way it works when I explicitly log in and
double click the icon (because I reconnect flawlessly when logged in
explicitly). When passing through, the farm knows who I am because it says I
already have an instance of the published desktop open, it just won't
reconnect me.

My objection to workspace control (which I have not found an answer for)
is a requirement that the PS server know the actual client name.



On 3/1/06, Joe Shonk <joe.shonk@xxxxxxxxx> wrote:
>
>  So how is WI going to know where to reconnect you to if workspace control
> is not enabled?Joe
>
> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
> Behalf Of *Jeff
> *Sent:* Wednesday, March 01, 2006 10:22 AM
> *To:* thin@xxxxxxxxxxxxx
> *Subject:* [THIN] Re: Web Interface, Passthrough Auth, Cannot reconnect
>
>
>
> I should have mentioned, I am NOT using Workspace Control.
>
> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
> Behalf Of *Jeff
> *Sent:* Wednesday, March 01, 2006 8:53 AM
> *To:* thin@xxxxxxxxxxxxx
> *Subject:* [THIN] Web Interface, Passthrough Auth, Cannot reconnect
>
>
>
> PS 4.0, Win2k3 SP1
>
> Client 9.150 Web Interface and Program Neighborhood only, Win2k Pro
>
>
>
> issue: Client that passes authentication to Web Interface cannot reconnect
> to disconnected published desktop session.
>
> Steps to reproduce:
>
> Open Web Interface with passed through authentication
>
> Open published desktop session
>
> Disconnect from published desktop session, confirm session is disconnected
>
> Open published desktop session
>
> Receive "Connection Error, You already have an instance of this
> application open..."
>
>
>
> Separately Web Interface, Passthrough Auth and reconnection to published
> apps work great. However, together I get this message.
>
> Logging in explicitly on the same client, to the same session, is
> successful
>
>
>
> Any hints appreciated.
>
> Jeff Hicks
>
> University of Colorado Hospital
>
>
>
>
>

Other related posts:

  1. Home
  2. thin
  3. Archive
  4. 03-2006