06-09-2019, 03:28 PM
Hi,
Since I applied last client update (ASGRD2019_Patch4_x64 -- 12.0.6420.1), the connection always prompts me for credentials.
Here is what I validated and behavior I noticed:
- Credentials saved in ASG are valid and assigned correctly to the machines;
- Windows and VNC are set to accept saved credentials;
- This used to work prior to me updating to patch4;
- If a machine is set by default to RDP (with assigned saved credentials and SSO ticked), if I click connect it will prompt for credentials;
- If I input those credentials, it will work;
- If I click "connect as" and choose those same saved credentials, the SSO works correctly;
- If a machine is set by default to VNC (with assigned saved credentials), if I click connect it will prompt me for credentials;
- If I input those credentials, it will work (note the username field is populated with my windows username instead of the saved one for the machine);
- If I click "connect as" and choose those same saved credentials, it will still prompt me for credentials;
- If I click "connect using protocol" and choose RDP, the SSO works correctly;
- This affects all ASG users (including some who still use 2018) so suspect a DB issue;
So overall seems saved credentials are broken after applying update 4.
We haven't changed anything on our side so I suspect the app has a bug. But again, I couldn't find this reported so I'm not sure.
If you need more info, please let me know.
Since I applied last client update (ASGRD2019_Patch4_x64 -- 12.0.6420.1), the connection always prompts me for credentials.
Here is what I validated and behavior I noticed:
- Credentials saved in ASG are valid and assigned correctly to the machines;
- Windows and VNC are set to accept saved credentials;
- This used to work prior to me updating to patch4;
- If a machine is set by default to RDP (with assigned saved credentials and SSO ticked), if I click connect it will prompt for credentials;
- If I input those credentials, it will work;
- If I click "connect as" and choose those same saved credentials, the SSO works correctly;
- If a machine is set by default to VNC (with assigned saved credentials), if I click connect it will prompt me for credentials;
- If I input those credentials, it will work (note the username field is populated with my windows username instead of the saved one for the machine);
- If I click "connect as" and choose those same saved credentials, it will still prompt me for credentials;
- If I click "connect using protocol" and choose RDP, the SSO works correctly;
- This affects all ASG users (including some who still use 2018) so suspect a DB issue;
So overall seems saved credentials are broken after applying update 4.
We haven't changed anything on our side so I suspect the app has a bug. But again, I couldn't find this reported so I'm not sure.
If you need more info, please let me know.