Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ASG 2020 + Smart Card Issues
#1
Question 
ASG Team -

I'm having issues with smart card logons using ASG 2020. I tried to upgrade to patch 7 and it still persists.

So here is the issue:

Try to RDP to a server using smart card as logon type. ASG Quick Connect. Enter server name. No credential. 

Pops up asks if I want to use smart card I say yes and enter my pin. Whoosh I'm in to Windows and life is good! Works as expected.


Go to RDP to next server...

Pop up asks if I want to use smart card, say yes and enter pin just like before. Whoosh we're in to Windows. The difference here is that instead of going to the desktop, I'm presented with a Windows logon screen wanting a user and password! This should not be as I auth'd with a smart card.

If I close the session and go back to my quick connect properties and look under Credentials there is an option for SSO. If I toggle that option [turn on if off, turn off if on] and try to connect again it works fine. Does not matter if it was on or off, just changing it to the other value fixes it.

However... the next server I try? Same problem again!   Sad



All of the servers I've tested work absolutely fine if I use Microsoft's own RDP client [mstsc] or their Remote Desktop Connection Manager which leads me to point at ASG as the issue since the native tools work fine. I've noticed it does not seem to matter what OS is on the end device I RDP to. Server 2016, 2019; Windows 10...

Any ideas?

Thanks!
Reply
#2
SSO has nothing to do with Smart Card!

Just open a connection - goto RDP-Resources category on the left and check the Smartcard option! It should be checked if you want to use it...
Regards/Gruss
Oliver
Reply
#3
(12-03-2021, 11:51 AM)DevOma Wrote: SSO has nothing to do with Smart Card!

Just open a connection - goto RDP-Resources category on the left and check the Smartcard option! If should be checked if you want to use it...

Yes I understand that but for some reason that workaround fixes the problem. 

I've isolated this to only happen when you use quick connect and it is like ASG's quick connect is not saving or using properties correctly.

If I make a normal static saved connection under 'Connections' it works fine.

PS: This is in database mode if that matters. I thought I saw something in release notes about settings in quick connect not saving properly but it was fixed; clearly not.
Reply
#4
Just following up. Any ideas?
Reply
#5
We will check again...
Regards/Gruss
Oliver
Reply
#6
Ya i saw this fix in the patch notes for Patch 7 for ASG 2020 which made me wonder down the road if maybe this is the problem since it only happens with QuickConnect.

Code:
"QuickConnect - "Full Connection Properties" will be saved correctly in database mode"



Cheers
Reply
#7
Hi DevOma, have you found anything on this?
Reply
#8
Tried to reproduce - but it works for me - and currently we are working on finalizing the next main release - we will check it again with version 2021 - should be ready in a few weeks...
Regards/Gruss
Oliver
Reply
#9
I'll keep an eye out for the new version and try it when that comes out!

Thanks
Reply




Users browsing this thread: 1 Guest(s)