When I encounter this, I just hit cancel or esc at the pin prompt and I am immediately presented with a name and password prompt. On Dec 6, 2007 1:47 PM, Rich Alexander <rich@xxxxxxxxxxxxxxxxxx> wrote: > Thanks, Greg. That's how we have it set up. The main page has two > links. One for CAC, one for explicit. Each is working perfectly. > > The problem is trying to use explicit credentials while there is a CAC in > the reader. > > I was just curious if anyone had had this before and had a solution. > > Our stance is that it is working as designed. The only people effected > are external and on a diferent domain. They log on to their local > workstation with CAC and use explicit to use our PS farm for one app. > > ----- Original Message ----- > *From:* Greg Reese <gareese@xxxxxxxxx> > *To:* thin@xxxxxxxxxxxxx > *Sent:* Thursday, December 06, 2007 2:16 PM > *Subject:* [THIN] Re: Another CAC problem > > I usually setup two separate WI sites. One for CAC users with passthrough > etc and one for explicit. Then I put a link for each of them on the other's > site just in case someone goes to the wrong one by mistake. > > On Dec 6, 2007 12:24 PM, Rich Alexander <rich@xxxxxxxxxxxxxxxxxx> wrote: > > > > > > > Hi, > > > > We use CAC only logon here. We have our WI running both Smart Card and > > Explicit logons. > > > > When logged on to the workstation with CAC and loggin into the WI with > > Explicit, we are unable to launch any apps properly. They just time out and > > then ask for credentials. Logging into the WI with CAC and then launching > > the apps works fine. In fact, pulling the CAC and then logging in > > explicitly works as well. > > > > If I save the ICA file and remove the Username/Domain/Password entries > > and then launch, it will properly prompt for credentials and then launch > > properly. > > > > Any ideas on a config change we could make to fix app launching with > > explicit login while a CAC is inserted? > > > > We are funneling all connections through a secure gateway over SSL. > > > > PS 4.0 > > > > Thanks! > > > > Rich > > > > > >